If you ship Amazon Ads code in production, this one matters.
Amazon now reads user consent through a framework called the Amazon Consent Signal (ACS). Only Amazon-certified CMPs send the right values, in the right order, at the right time. If your tool is not certified, your campaign data is at risk.
What ACS Actually Does
ACS sits between your cookie banner and Amazon Ads systems. When a shopper picks "yes" or "no", the CMP turns that choice into a structured signal. Amazon then knows if it can use that data for ads measurement, audience modelling, or retargeting.
Three things matter for the engineer:
- The signal must fire before any Amazon ad tag runs.
- It must carry granular categories (marketing, analytics, personalisation).
- It must be re-checked when the shopper updates choices later.
How a Clean Setup Looks
A working pattern usually involves:
- CMP script loaded synchronously in
<head>so consent is known early. - Amazon Ads pixels and DSP tags gated behind a consent listener.
- ACS values pushed into the dataLayer for Google Tag Manager.
- A retry path for users who change their mind via a "Manage Cookies" link.
A certified CMP gives you tested templates so you do not have to build this from scratch. The full reasoning behind why Amazon went this route is laid out in the new standard for Amazon advertisers.
The Business Side
Cleaner ACS data means richer attribution, better lookalikes, and fewer "missing conversions" tickets from the marketing team. Engineers also stop firefighting privacy tickets, because server-side tagging handles routing safely.
If you ship to multiple regions, also map ACS to your existing privacy stack across global privacy regulations. One framework, less drift.
Less broken data. Stronger signals. Better campaigns.
Top comments (0)