Dotdigital

Datafly Signal delivers events to Dotdigital server-to-server, writing each event as a transactional (insight) data record attached to a contact. Dotdigital programs, automations and segments can then react to the first-party activity Signal captures, without a client-side Dotdigital tracking script.

Prerequisites

Before configuring Dotdigital in Signal you need a Dotdigital account, an API user, and a transactional-data collection name.

Configuration

Configure in Signal

1. Go to Integrations > Add Integration > Dotdigital.
2. Select the Default preset.
3. Enter your region, api_user_email, api_user_password, and collection_name.
4. Select consent categories (typically marketing).
5. Click Save.

API Endpoint

POST https://{region}-api.dotdigital.com/v2/contacts/transactional-data/{collection_name}

Authentication is HTTP Basic Auth: the API user email is the username and its password is the password. Signal Base64-encodes the credentials into the Authorization: Basic header. A successful write returns 201 Created.

Identity Signals

Dotdigital attaches each transactional-data record to a contact by email address. Signal sends the email from the identified contact’s traits as the contactIdentifier, so a user must be identified before their events can attach to a known contact.

Call datafly.identify() when a user logs in, registers, or submits a form so that Signal has an email to attach events to:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  firstName: "Jane",
  lastName: "Doe"
});

Event Mapping

The Default preset maps these Signal events to Dotdigital transactional data. The Signal event name is stored at json.eventName and event properties are stored under json.

Events not in the preset are dropped (defaults.action: drop). To customise, edit the integration’s Field Mappings in the Management UI.

Example: Order Completed

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "GBP",
  products: [
    { product_id: "SKU-A", product_name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", product_name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

Dotdigital payload sent by Signal:

{
  "key": "evt_abc123def456",
  "contactIdentifier": "jane.doe@example.com",
  "json": {
    "eventName": "order_completed",
    "anonymousId": "a1b2c3d4e5f6",
    "userId": "user-123",
    "timestamp": "2026-06-06T12:00:00Z",
    "orderId": "ORD-001",
    "revenue": 129.99,
    "currency": "GBP",
    "products": [
      { "product_id": "SKU-A", "product_name": "Widget", "price": 49.99, "quantity": 2 },
      { "product_id": "SKU-B", "product_name": "Gadget", "price": 30.01, "quantity": 1 }
    ]
  }
}

Testing

1. Identify a test contact and trigger an event from your site (or use Signal’s event debugger).
2. In Dotdigital, open the test contact’s record and check the Insight data section for the new record in your collection.
3. Alternatively, fetch the record via the API:

GET https://{region}-api.dotdigital.com/v2/contacts/transactional-data/{collection_name}/{key}

A 201 Created from the write endpoint and the record appearing against the contact confirm end-to-end delivery.

Troubleshooting