- What changed
- Amazon Ad Tag (AAT) sets a first-party aatSession cookie holding a session identifier that is sent with every event it captures; expires 30 days after the last page view
- When
- Release note dated November 16, 2026, visible November 14 (PPC Land); Google Tag Manager template v4.1 with an opt-out checkbox merged November 5, 2026
- Who it affects
- Brands and agencies running Amazon Ad Tag on websites for Amazon DSP, Amazon Marketing Cloud or off-Amazon conversion tracking; North America only, per Amazon's guide
- What to do
- Add aatSession to your cookie list and consent tool, decide keep or opt out, and mark the start date in reports so conversion changes are not misread
Key takeaways
- Amazon Ad Tag now sets a 30-day first-party aatSession cookie on North American advertiser sites by default, per a release note dated November 16, 2026.
- Opting out takes one command on every page or a checkbox in Amazon's GTM template v4.1; events keep flowing either way.
- Update your cookie list, test consent declines, annotate reports, and check the Safari gap after 30 days.
How aatSession works
- 1Visit
Shopper lands on your site with AAT
- 2Consent
Set only if TCF, GPP or ACS allow
- 3Cookie
aatSession written on your domain
- 4Events
Session ID sent with each event
- 5Expiry
30 days after the last page view
What Amazon switched on
According to the release note, as quoted by PPC Land, the tag "now sets a first-party cookie, aatSession" so Amazon Ads can measure and attribute site events more reliably as third-party cookies are phased out. Amazon's Ad Tag guide describes it as North America only, created and read automatically with no setup, sent with each event the tag captures, and expiring 30 days after the visitor's last page view, so every new visit pushes the expiry forward.
Amazon says the tag sets, reads and sends the identifier only when the visitor's consent signals allow it, naming TCF, GPP and the Amazon Consent Signal. What neither the note nor the guide says, PPC Land points out, is what happens when a visitor arrives with no consent signal at all, which is common on US sites without a consent banner. It is the second first-party cookie the tag writes: amznAref already stores the click token from an Amazon ad for 30 days.
How to turn it off, and the catch
The off switch is a command placed in the tag's base code before the first event: amzn("disableAATSessionCookie", true). When it runs, the tag deletes any existing aatSession cookie, stops setting a new one and marks each event to show the cookie was turned off, so Amazon can see which sites opted out. Events and hashed identity signals keep flowing. The setting applies to the current page only, so it has to run site-wide, and passing false does not switch the cookie back on; you have to remove the line.
For Google Tag Manager users, Amazon's own template on GitHub reached version 4.1 on November 5, 2026 with a "Disable first-party aatSession cookie" checkbox. The checkbox is unchecked by default. The same template already refuses to fire when Google consent mode marks ad_storage or ad_user_data as denied, but if no consent mode is configured in the container, it fires as usual.
Amazon Ad Tag measurement changes
Amazon Consent Signal introduced
Consent signal deadline for UK and EEA data
Events API generally available
GTM template v4.1 adds opt-out box
aatSession release note appears
Date on the release note
Our team and SpiderOS adapt bids and campaigns to new Amazon Ads features the week they launch.
So what: three ways this touches your numbers and your risk
Measurement: Amazon will group a browser's site events into sessions it can tie together for up to 30 days. Teams comparing Amazon reported conversions before and after mid-November may see shifts caused by how events are grouped, not by campaign changes. Note the date in your Amazon Marketing Cloud and DSP reports.
Safari: Apple's WebKit documentation says Intelligent Tracking Prevention deletes cookies created in JavaScript after 7 days without user interaction with the site. Amazon does not say how aatSession is written. If it is written by the script, a Safari shopper who returns after 8 days may start a fresh session, so the 30-day window will not hold for part of your traffic.
Compliance: a new cookie name on your domain means your privacy notice and consent tool's cookie list no longer match what the site sets until you add it. That is a paperwork fix, but it is the kind regulators and plaintiffs' firms look for.
Illustrative example: a brand's site records 1,000 purchases a month from Amazon DSP traffic. If 40% of shoppers use Safari and a quarter of those buy after a gap of more than 7 days, about 100 purchases a month could fall outside the 30-day session link. That is 10% of conversions where the session view is weaker than Amazon's 30-day description suggests. Use your own browser mix and time to purchase from your analytics.
What brands should do this week
Six steps, each with an owner, a place and a metric that shows it worked.
- Developer: open your site in a Chrome window, accept cookies, and check the browser's storage panel for aatSession and amznAref on your domain. Metric: you know whether the cookie is already being set on your pages.
- Privacy or legal owner: add aatSession, its 30-day duration and its purpose to the cookie list in your privacy notice and consent tool. Metric: the published cookie list matches what the storage panel shows.
- Developer: test a visit with consent declined in your banner and confirm aatSession is not set. Metric: no aatSession cookie after a decline; if one appears, raise it with Amazon Ads support before deciding to keep it.
- Marketing lead: decide keep or opt out. Keep it if you rely on Amazon DSP or AMC for off-Amazon conversions; opt out if your policy blocks new ad cookies. Metric: a written decision, and if opting out, the command in the shared site header or the GTM checkbox ticked on every AAT tag.
- Ads manager: add an annotation for November 14 to 16, 2026 in Amazon Ads reporting and your own dashboard. Metric: week over week conversion changes after that date are reviewed against the annotation before bids change.
- Analyst: after 30 days, compare Amazon reported site conversions with your own order data by browser. Metric: the gap for Safari versus Chrome, which tells you how much the 7-day limit affects you.
| Keep it | Opt out | |
|---|---|---|
| Session link for DSP and AMC | ||
| Events still sent to Amazon | ||
| Needs cookie list update | ||
| Code on every page |
Opt-out is page level; passing false does not turn it back on.
When this does not apply
Brands that sell only on Amazon and have no Amazon Ad Tag on an outside website are not affected; the cookie lives on the advertiser's own domain. Sites outside North America are not covered, according to Amazon's guide, and UK and EEA traffic already needs a valid consent signal for Amazon to process data. If you send site events only through the server-side Conversions or Events API, the browser cookie is not part of that path, though Amazon's documentation does not say how aatSession behaves with server-side tagging. Sponsored Products and Sponsored Brands reporting inside Amazon does not depend on this tag; for those, see our Amazon attribution guide for how off-Amazon traffic is measured.
Where PPC Spider helps
PPC Spider runs Amazon PPC management and DSP for brands, and SpiderOS flags measurement changes like this one so a shift in reported conversions is not mistaken for a campaign problem. Our DSP agency for Amazon sellers team can check your tag setup, and a free Amazon audit will show where your ad spend and conversions really come from. More platform changes are in Amazon advertising news.
Sources
- PPC Land: Amazon Ad Tag adds a 30-day first-party cookie to advertiser websites, November 14, 2026, on the Amazon Ads API release note dated November 16, 2026 (https://ppc.land/amazon-ad-tag-adds-a-30-day-first-party-cookie-to-advertiser-websites/)
- GitHub, amzn: v4.1: Add aatSession cookie opt-out to the GTM template, pull request 29, merged November 5, 2026 (https://github.com/amzn/ads-pao-amznjs-gtm-template/pull/29)
- GitHub, amzn: Amazon Ads GTM template README, consent mode and first-party session cookie sections (https://github.com/amzn/ads-pao-amznjs-gtm-template)
- WebKit: Tracking Prevention in WebKit, 7-day cap on script-writeable storage (https://webkit.org/tracking-prevention/)
We run these playbooks on client accounts every day. Start with a free audit.
Get a free audit