Amazon DSP Events

Send conversion events to Amazon DSP via the Amazon Ads API for programmatic campaign measurement and audience optimisation across Amazon properties.

Why route Amazon DSP through Datafly Signal

• Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Amazon DSP optimises against are not filtered by the browser.
• Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Amazon DSP receives match keys rather than raw personal data.
• Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Amazon DSP attributes the event to the right session.
• Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Amazon DSP rate limit, and retries on 429 or transient failure rather than dropping the event.
• Token lifecycle is handled for you. Signal obtains and refreshes the OAuth credentials Amazon DSP requires, so nothing expires quietly in the middle of a campaign.
• 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.
• No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Complete these steps in the Amazon Advertising platform before configuring the integration in Signal.

Configuration

Signal Setup

Quick Setup

1. Navigate to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Amazon DSP Events or filter by Advertising.
4. Click Install, select a variant if available, and fill in the required fields.
5. Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

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 Events",
    "variant": "default",
    "config": {
      "advertiser_id": "ENTITY1234ABCD",
      "profile_id": "1234567890",
      "access_token": "Atza|IwEBIA..."
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The default Retail preset maps a minimal set of conversion events:

To customise or extend, edit the integration’s Field Mappings in the Management UI.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Amazon DSP API. No client-side scripts are loaded for this integration.

Testing

1. Install the integration with your Advertiser ID, Profile ID, and Access Token.
2. Trigger a test event (e.g. a purchase) on your site with the Datafly.js collector active.
3. Check the Live Events view in Signal to confirm the event was captured.
4. Verify the event appears in the Amazon DSP console under conversion reporting.
5. Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

Troubleshooting