Amazon Ads

Datafly Signal delivers conversion events to Amazon Ads server-to-server, supporting sponsored products, display, and DSP campaign attribution and optimisation.

Why route Amazon Ads 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 Ads optimises against are not filtered by the browser.
Email is hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Amazon Ads 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 Ads attributes the event to the right session.
Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Amazon Ads 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 Ads requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination. Amazon Ads 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

Before configuring Amazon Ads in Signal, you need:

An Amazon Advertising account with API access
A registered application in the Amazon Advertising developer portal
An OAuth client ID, client secret, and a long-lived refresh token
Your Profile ID (advertiser/account profile)

Get your Amazon Ads credentials

Sign in to the Amazon Advertising developer portal and register an application.
Once approved, copy the Client ID (looks like amzn1.application-oa2-client...) and Client Secret.
Run the OAuth Login with Amazon authorisation flow to issue a refresh token with the advertising::campaign_management scope. See Amazon’s Authorisation guide for the exact steps.
In the Amazon Advertising console, open your account and copy the Profile ID from the URL or via the API profiles endpoint.

Configure the integration in Signal

In the Management UI, go to Integrations → Add Integration.
Select Amazon Ads from the catalogue.
Give the integration a name (for your reference).
Fill in the required fields:

Field	Required	Description
`client_id`	Yes	Amazon Ads API client ID.
`client_secret`	Yes	Amazon Ads API client secret.
`refresh_token`	Yes	Long-lived OAuth refresh token.
`profile_id`	Yes	Amazon Ads profile ID.

Choose which pipeline(s) this integration should run on.
Select consent categories (defaults to marketing).
Click Save.

Event mapping

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

Signal event	Amazon Ads event
`page`	`page_view`
`Product Viewed`	`view_content`
`Product Added`	`add_to_cart`
`Order Completed`	`purchase`

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

Identity

Signal sends the following identity signals to Amazon Ads, subject to consent and availability:

Capability	Notes
Hashed email	SHA-256 (lowercase, trimmed)
Client IP	Forwarded from the original request
User-Agent	Forwarded from the original request
Amazon AAX ID	Where available from the Amazon ad-system sync

This integration is gated on the marketing canonical consent category. Events without marketing consent are not delivered.

Verify it’s working

In the Management UI, go to Pipelines → your pipeline → Live Events.
Trigger a test event on your site.
The event appears in the live feed; click to see the exact payload sent to Amazon Ads.
Cross-check in the Amazon Advertising console under your conversion reports (note Amazon may take several hours to reflect API uploads).

Troubleshooting

Events aren’t appearing in Amazon Ads.

Confirm the integration is enabled on the pipeline.
Confirm marketing consent is granted.
Inspect the delivery response — 401/403 usually indicates the refresh token has been revoked; reissue via the OAuth flow.

Profile ID mismatch errors. Confirm the profile ID matches the account in the same region as the credentials.