Spent a full week chasing a phantom bug. Numbers in our Amazon DSP went down. Bids looked fine. Tags looked fine. Servers looked fine. The bug? The cookie pop-up.
Here's what happened, and how to fix it without breaking anything else.
The thing nobody told us
Amazon changed how it reads cookies in 2026. There's a new signal called ACS — the Amazon Consent Signal. Every cookie tool has to send ACS in a very specific shape. Old tools don't. Even tools that say they support TCF v2. ACS is its own thing.
If your tool doesn't send ACS, Amazon turns down its tracking. Your DSP audiences shrink. Your sponsored ad numbers drop. None of it throws an error. That's the worst part.
How to fix it in four steps
Step one: check if your cookie tool is on Amazon's approved list. Most aren't.
Step two: hook the user's choice into the dataLayer the moment they click:
window.dataLayer.push({
event: 'consent_update',
ad_storage: 'granted',
analytics_storage: 'granted',
ad_user_data: 'granted',
ad_personalization: 'granted'
});
Let the certified tool turn that into the ACS shape Amazon wants. Don't write the mapping yourself — you'll break it.
Step three: open Tag Assistant. Fire a test event. Look for ACS in the outgoing Amazon pixel. If it's not there, your setup is broken.
Step four: when a user closes the pop-up without clicking, send 'denied' for ad_storage and ad_user_data. Don't leave it blank. Blank is the top reason Amazon flags an account.
Why bother
Cleaner ACS = bigger ad audiences = lower cost per sale. The math is simple. Seers walked through the whole thing in their breakdown of what 'Amazon-certified' really means. Teams already on server-side tagging get a head start because consent lives at the gateway, not in fragile client scripts.
Top comments (0)