Amazon DSP Events

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

Prerequisites

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

Create or access your Amazon Advertising account

Log in to Amazon Advertising. You need an Amazon Advertising account with advertiser-level access. If you don’t have one, register through the Amazon Advertising console.

Ensure you have Amazon DSP access

You need either managed-service or self-service access to Amazon DSP. Managed-service accounts are set up through an Amazon Ads account executive. Self-service accounts can be requested through the Amazon DSP console. Confirm you can access the DSP dashboard before proceeding.

Find your Advertiser ID and Profile ID in the DSP console

Navigate to the Amazon DSP console. Your Advertiser ID (entity ID) is found under Advertiser Settings. Your Profile ID is region-specific and can be found using the Amazon Ads API Profiles endpoint or in the DSP console URL. Each marketplace region (e.g. US, UK, EU) has a unique Profile ID.

Generate API credentials via the Amazon Advertising API portal

Go to the Login with Amazon developer console.
Create a new Security Profile if you don’t have one.
Register your application and note the Client ID and Client Secret.
Complete the OAuth flow to generate an Access Token with DSP permissions.
Ensure the token has the advertising::campaign_management scope.

⚠️

Amazon Ads API access tokens expire and must be refreshed. Signal handles token refresh automatically if you provide valid credentials, but initial token generation must be done manually through the OAuth flow.

Configuration

Field	Type	Required	Description
`advertiser_id`	string	Yes	Your Amazon DSP advertiser entity ID. Found in the Amazon DSP console under Advertiser Settings.
`profile_id`	string	Yes	Your Amazon Ads API profile ID. Each marketplace region has a unique profile ID.
`access_token`	secret	Yes	Amazon Ads API access token with DSP permissions. Generated via Login with Amazon OAuth flow.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Amazon DSP Events or filter by Advertising.
Click Install, select a variant if available, and fill in the required fields.
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

Signal Event	Amazon DSP Event	Description
`purchase`	`Purchase`	Completed transaction with revenue and order details
`add_to_cart`	`AddToCart`	Product added to shopping cart
`page_view`	`DetailPageView`	Product or content page view
`sign_up`	`Subscribe`	New user registration or subscription
Custom events	Custom conversion	Map any Signal event to an Amazon DSP conversion type via blueprint configuration

Event mappings are fully configurable through blueprints. The table above shows common default mappings — you can customise these to match your campaign goals.

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

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

⚠️

Amazon DSP conversion data may take up to 24 hours to appear in campaign reports due to Amazon’s attribution processing pipeline.

Troubleshooting

Issue	Resolution
`401 Unauthorized`	Your access token may have expired. Regenerate it through the Login with Amazon OAuth flow and update the integration configuration.
`403 Forbidden`	Verify the access token has the `advertising::campaign_management` scope and that your account has DSP API access enabled.
`404 Not Found`	Check that the Advertiser ID and Profile ID are correct and match the same region.
Events not appearing in Amazon DSP	Confirm the integration is enabled in Signal and check the Delivery Log for errors. Amazon may take up to 24 hours to process conversions.
`429 Rate Limit Exceeded`	Amazon Ads API has rate limits per profile. Signal will automatically retry with backoff.

Visit Amazon DSP Events documentation for full API documentation and credential setup instructions.

adMarketplace Amnet