Integrations / Advertising
Amazon Ads
Conversion tracking for Amazon Ads sponsored products and display campaigns.
Datafly Signal delivers first-party events to Amazon Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amazon Ads expects.
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 hashed before it leaves 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.
What ships in the blueprint
Mapped events
add_to_cartpagepurchaseview_itemVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Amazon Ads documentation.
Frequently asked questions
Does Datafly Signal integrate with Amazon Ads?
Yes. Datafly Signal delivers first-party events to Amazon Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amazon Ads expects. The integration is included in every deployment at no additional cost.
How is server-side Amazon Ads tracking different from the Amazon Ads tag?
The Amazon Ads tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Amazon Ads from your server, so delivery does not depend on browser conditions.
What personal data is sent to Amazon Ads?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Amazon Ads receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Amazon Ads?
The blueprint ships with mappings for add_to_cart, page, purchase, view_item. Any event in your schema can be mapped to Amazon Ads through pipeline configuration without a code change.
Do I need to keep the Amazon Ads tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Amazon Ads deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Amazon Ads server-side?
See how Datafly Signal delivers first-party events to Amazon Ads from infrastructure you control, with hashed identity and consent enforcement built in.