Installation with Wrangler

Prerequisites

• DATADOME_SERVER_SIDE_KEY available in your DataDome dashboard,
• DATADOME_CLIENT_SIDE_KEY available in your DataDome dashboard,
• up-to-date Wrangler,
• a Worker project. If you don’t have one, you can easily create one in one command line.

Protect your traffic

1. Download the latest version of our Cloudflare Worker script.
2. Copy the file datadome.tsinto your Wrangler project.
3. Create a Cloudflare Worker secret named DATADOME_SERVER_SIDE_KEY:

wrangler secret put DATADOME_SERVER_SIDE_KEY

A prompt appears. Enter the value of your DataDome server-side key you can find in your DataDome Dashboard.

4. Create a Cloudflare Worker secret named DATADOME_CLIENT_SIDE_KEY:

wrangler secret put DATADOME_CLIENT_SIDE_KEY

A prompt appears. Enter the value of your DataDome client-side key you can find in your DataDome Dashboard.

5. Update your wrangler.toml file:

• Change the value of main with the path to the datadome.ts file,
• Add the route key to configure the domains and routes you want to set the DataDome Worker on.

name = "datadome-worker"
main = "src/datadome.ts"
route = { pattern = "example.org/*", zone_name = "example.org" }

6. Deploy your Worker (you will be asked to authenticate with Cloudflare if you are not logged in already):

wrangler deploy

Congrats! You can now see your traffic in your DataDome dashboard.

Configuration

The configuration is done inside the script, using constants.

 /\.(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|map)$/i

Update with Wrangler

1. Download the latest version of our Cloudflare Worker script.
2. Retrieve the specific values that you may have set to configure your DataDome Worker that are not the default value.
3. Paste the content of the datadome.ts file into the file used as the main source for the script of your Worker project.
4. Configure the settings with the values from step 2.
5. Deploy with Wrangler:

wrangler deploy

Uninstallation with Wrangler

To delete the DataDome Worker, run from your Worker project:

wrangler delete

Logging

DataDome custom logging

1. Inside your wrangler.toml file add:

   [observability.logs]
   enabled = true

2. Deploy with

   wrangler deploy

3. By default, DataDome logs errors only (such as errors in the configuration). If you want to have detailed logs for debugging, you can modify the DataDome Worker script and set DATADOME_ENABLE_DEBUGGINGto true.

DataDome logs format

The DataDome custom logs have the following format:

{
  "step": "string",
  "result": "string", 
  "reason": "string",
  "details": {
    "key": "value"
  },
  "company": "DataDome",
  "line": 123
}

Logpush

You can use Logpush to send logs to a destination supported by Logpush (Datadog, Splunk, S3 Bucket…).

❗️

Cloudflare plan

Logpush is available to customers on Cloudflare’s Enterprise plan.

Update the Worker’s script

1. Fill the DATADOME_LOGPUSH_CONFIGURATION value with the name of the values you want, as an Array of Strings.
   The possible values are available in the Enriched headers page.

Eg:

DATADOME_LOGPUSH_CONFIGURATION = "["X-DataDome-botname", "X-DataDome-isbot", "x-datadomeresponse"]"

Enable Logpush

2. Inside your wrangler.toml file add:

logpush = true

3. Deploy with wrangler.

// Sample code for custom fields  
// Editing directly the datadome.js file  
var DATADOME_CUSTOM_FIELD_STRING_1 = function (request) {  
    if (request.headers['x-user-tier'] && request.headers['x-user-tier'][0] && request.headers['x-user-tier'][0].value) {  
        return request.headers['x-user-tier'][0].value;  
    } else {  
        return 'standard';  
    }  
};

// Sample code for custom fields  
// when calling activateDataDome
 const dataDomeHandler = activateDataDome(myHandler, {
   serverSideKey: env.DATADOME_SERVER_SIDE_KEY,
   clientSideKey: env.DATADOME_CLIENT_SIDE_KEY,
   customFieldString1: function (request) {
     if (request.headers['x-user-tier'] && request.headers['x-user-tier'][0] 
				&& request.headers['x-user-tier'][0].value) {  
       return request.headers['x-user-tier'][0].value;  
     } else {  
       return 'standard';  
     }
   }, 
   // ...other options
 });