Magento
DataDome Magento with Fastly CDN integration detects and protects against bot activity.
This module is dedicated for use with Magento utilizing Fastly CDN.
DataDome works as a preflight to detect bots. A fingerprint is sent and DataDome detects in real-time if the traffic is legitimate or not.
This module leverages Fastly integration into Magento.
Prerequisites
Before integrating DataDome bot protection in Magento, you need to:
- Ask Fastly Support to enable DataDome support for your Fastly service as described here
- Use Fastly integration version 1.2.127 or higher in Magento
- Have DataDome server-side key available in your DataDome dashboard
- Have access to Magento StoreFront Admin Portal
- Have already set up Fastly as Caching system for your Magento website
How to install and configure
1. Enable Fastly Edge Modules
- Connect to your Magento StoreFront Admin Portal
- Go to Stores > Configuration > Advanced > System > Full Page Cache > Advanced Configuration
- Find Enable Fastly Edge Modules and select Yes then press the Save Config button at the top-right.
After enabling, the Fastly Edge Module sub-menu should appear as seen below:
Click on Manage and then Refresh. Select DataDome Bot Detection integration in the list and click on Save.
2. Configure DataDome integration
-
Click on the wheel icon
-
Paste your server-side key inside the Field API Key and click on Upload. The server-side key is found in the DataDome dashboard.
You need to contact Fastly Support to enable advanced features (Pragmas) before enabling this change.
- You are now protected by DataDome Bot & Fraud Protection
## Settings
Setting | Description | Required | Default |
---|---|---|---|
API Key | Your DataDome License key | Yes | |
Exclusion regex | The regex that will be applied to req.url.path | Yes | (?i)\.(avi|flv|mka|mkv|mov|mp4|mpeg|mpg|mp3|flac|ogg|ogm|opus|wav|webm|webp|bmp|gif|ico|jpeg|jpg|png|svg|svgz|swf|eot|otf|ttf|woff|woff2|css|less|js)$ |
Connection timeout | How long to wait for a timeout (in milliseconds) | Yes | 150 |
First byte timeout | How long to wait for the first byte (in milliseconds) | Yes | 50 |
Between bytes timeout | How long to wait between bytes (in milliseconds) | Yes | 50 |
restore_referrer | Restore original referrer when a challenge is passed. | No | false |
graphql_support | Enable GraphQL extraction of operation name on POST request. | No | false |
Updated about 1 month ago