Amazon DSP

Import server-side conversions against Amazon DSP conversion definitions (conversion import, Conversions API v1). For new set-ups Amazon recommends the Events API: see the Amazon Ads integration.

Why route Amazon DSP through Datafly Signal

• Conversions survive ad blockers and tracking prevention. Signal sends the event from your own infrastructure, so the conversions Amazon DSP optimises against are not filtered by the browser.
• Identifiers are hashed before they leave your infrastructure. Signal normalises and applies SHA-256 inside your own deployment, so Amazon DSP receives match keys, not raw personal data.
• One consent decision governs every destination. Amazon DSP is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
• Presets for Retail and Insurance. The mapping starts from a working configuration for your vertical, and every field can be changed afterwards.

Prerequisites

1. An Amazon Ads API application (Login with Amazon). Copy its Client ID and Client Secret, and keep a refresh token for a user with the event_manager_edit permission on the DSP advertiser.
2. Copy the DSP Advertiser ID (not the entity ID) and pick the API host for its region.
3. Create the conversion definitions (source SERVER_TO_SERVER) in Amazon DSP and copy their IDs: one default, and optionally one per event type.

Configuration

Configure in Signal

1. In the Management UI, go to Integrations > Integration Library and select Amazon DSP.
2. Choose a preset, fill in the fields above and choose the pipelines and consent categories (advertising destinations default to marketing).
3. Click Install Integration.

Or with the Management API:

curl -X POST http://localhost:8084/v1/admin/integration-catalog/amazon_dsp/install \
  -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" \
  -d '{"name": "Amazon DSP", "variant": "default", "config": {"advertiser_id": "1234567890123", "client_id": "amzn1.application-oa2-client.abc123...", "client_secret": "...", "refresh_token": "Atzr|...", "api_host": "advertising-api.amazon.com", "configuration_id": "1234567890123"}, "delivery_mode": "server_side"}'

API endpoint

POST https://{{api_host}}/accounts/{{advertiser_id}}/dsp/conversionDefinitions/eventData

Authentication: Login with Amazon Bearer token (refreshed from the refresh token), Amazon-Advertising-API-ClientId and Amazon-Ads-AccountId headers. Allow egress to your region's Amazon Ads API host from the network your delivery workers run on.

Presets and event mapping

Every preset sends only the fields it maps (the strict output contract is on). Events not listed are not sent.

Retail (ecommerce)

Retail events imported against Amazon DSP conversion definitions: page and product views, search, add to cart, checkout and purchases with value, currency and the order ID as clientDedupeId.

Default (default)

Amazon DSP conversion import core events (page views, search, add to cart, checkout, leads, sign-ups and purchases), each sent to the conversion definition configured for its type, with hashed email, phone and name match keys and the country code.

Insurance (insurance)

Insurance funnel: quote requests and leads, applications and policy purchases, each against its own conversion definition, with premium value and the policy number as clientDedupeId.

Identity and hashing

Email, phone and names come from datafly.identify() traits (a legacy properties.email / properties.phone is read when no trait is set). Raw personal data is never sent.

The conversion import needs at least one match key per event, so an event with no email, phone, name or device advertising ID (an anonymous visitor) is not sent.

Deduplication and consent

clientDedupeId carries the Signal event ID, or the order ID on purchases; Amazon keeps the first record per ID across the Ad Tag, this API and MMPs. countryCode is required.

Example: purchase (Default preset)

datafly.identify('crm-user-7', { email: 'jane.doe@example.com', phone: '07700 900123', first_name: 'Jane', last_name: 'Doe' });
datafly.track('purchase', {
  transaction_id: 'T_1001', value: 139.99, currency: 'GBP',
  items: [
    { item_id: 'SKU_1', item_name: 'Helmet', item_category: 'Motorbike', item_brand: 'Shoei', price: 120.00, quantity: 2 },
    { item_id: 'SKU_2', item_name: 'Gloves', price: 19.99, quantity: 1 }
  ]
});

Request Signal sends (rendered from the preset):

{
  "eventData": [
    {
      "clientDedupeId": "T_1001",
      "conversionDefinitionId": "CD-PURCH",
      "countryCode": "GB",
      "currencyCode": "GBP",
      "matchKeys": [
        {
          "type": "EMAIL",
          "values": [
            "86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d"
          ]
        },
        {
          "type": "PHONE",
          "values": [
            "033134b911b137918338415ee3d20a064b24773d36a3b02e8b99fdd3fcd6b4cd"
          ]
        },
        {
          "type": "FIRST_NAME",
          "values": [
            "81f8f6dde88365f3928796ec7aa53f72820b06db8664f5fe76a7eb13e24546a2"
          ]
        },
        {
          "type": "LAST_NAME",
          "values": [
            "799ef92a11af918e3fb741df42934f3b568ed2d93ac1df74f1b8d41a27932a6f"
          ]
        }
      ],
      "name": "purchase",
      "timestamp": "2025-09-22T00:13:20.123Z",
      "value": 139.99
    }
  ],
  "source": "SERVER_TO_SERVER"
}

Known limitations

• unitsSold is not set (Amazon defaults it to 1) (#1389).

Troubleshooting