Amazon Ads has switched on a first-party cookie inside the Amazon Ad Tag, the JavaScript snippet advertisers place on their own websites to report page views, sign-ups and purchases back to Amazon. It is on by default for North American sites, and it puts Amazon alongside Google in moving ad measurement onto the advertiser’s own domain as browsers and regulators squeeze third-party identifiers.
What Amazon changed
The Amazon Ads API release notes carry an entry dated November 16, 2026, which was already posted when we checked on November 15. It says that in North America the Amazon Ad Tag (AAT) now sets a first-party cookie named aatSession on the advertiser’s website. The cookie holds a session identifier that ties together the events a single visitor triggers on the site. Amazon gives the purpose plainly: the identifier lets Amazon Ads measure and attribute those events more reliably as third-party cookies are phased out.
The cookie expires 30 days after the visitor’s last page view, so every new page view pushes the expiry forward. Advertisers do not need to change their tag configuration. The note says no setup is required, and the session identifier section of the Amazon Ad Tag guide adds that AAT sends the identifier with each event it captures from the website.
Consent signals decide when it runs
According to the release note, AAT sets, reads and sends the identifier only when the visitor’s consent signals allow it, naming three: TCF, GPP and Amazon’s own Amazon Consent Signal (ACS). The guide repeats the list. It does not describe what the tag does on a site that passes none of those signals, which is a question each advertiser’s privacy team should put to Amazon directly.
The off switch is per page
Advertisers who do not want the cookie must add one command, amzn("disableAATSessionCookie", true);, to the tag’s base code before the first event fires. The guide says that when the line runs, AAT deletes any existing aatSession cookie on the domain, sets no new one and marks each event to show the advertiser turned the cookie off. So Amazon can tell which events came from sites that opted out.
The setting covers only the page it runs on. Amazon tells advertisers to place it everywhere AAT runs, for example in a shared site header or tag manager. Passing false does not switch the cookie back on for a page where it was already off; the line has to be removed. Events and hashed identity signals keep working either way.
The shift: measurement moves onto the advertiser’s domain
Amazon’s change follows a route Google opened in May 2025 with Google tag gateway for advertisers. Google’s Google Ads help announcement says the feature lets advertisers run Google tags, client-side or server-side, through their own website infrastructure such as a content delivery network, load balancer or web server. Google said advertisers who configured it saw an 11% uplift in signals.
“Our new Google tag gateway for advertisers makes it easy to upgrade your tags to serve from your site’s own server,” wrote Kamal Janardhan, Sr. Director, Product Management, Ads Measurement at Google, in a May 2025 post on the Google Ads & Commerce Blog.
The two platforms reach the same place by different paths. Google’s gateway needs the advertiser to configure routing through its own infrastructure. Amazon’s cookie arrives with the existing tag and stays unless the advertiser removes it page by page. Both put the measurement identifier under the advertiser’s domain name.
Browser makers have been redrawing those rules all year. We covered Safari 27.2 fixing a seven-day cap on cookies set by CNAME-hosted sites and Apple’s WebKit post explaining Safari’s identity resolution block. Industry bodies are pushing the same direction on the server side: the IAB Tech Lab finalized ECAPI guidelines for sending conversion events to clean rooms.
What it means for the marketing leader
The cookie sits on your domain, and that changes who answers for it. A visitor who opens your cookie settings will see aatSession listed under your site. Your consent banner, cookie policy and records of processing now need to describe a cookie that Amazon set without anyone on your team writing a line of code.
Attribution reports may move
Amazon says the identifier exists so it can measure and attribute site events more reliably. In our reading, that makes a step change in Amazon-reported conversions plausible once the cookie is live, because Amazon will be able to link events from one visitor that it previously saw as separate. Before you read any lift as campaign performance, mark the date the cookie appeared on your site in your reporting notes and compare Amazon’s numbers with your own analytics for the same window.
Consent tooling has to pass the right signals
The cookie depends on TCF, GPP or ACS signals reaching the tag. If your consent management platform sends none of them, ask Amazon in writing what the tag does on your pages. If you advertise on Amazon from outside North America, the guide lists the feature as North America only, so expect no change on those sites for now.
Decide on purpose
Some advertisers will want the cookie on, because better-linked sessions should feed Amazon’s attribution and bidding. Others will want it off until legal review is done. Both are defensible. The weak position is having no decision at all, with the cookie running because nobody checked. Amazon’s earlier moves to fold its DSP and ad console into one agent show how much of its buying now runs on the signals this tag sends back.
What to do this week
- Open your site in a North American session with consent granted and check for the aatSession cookie on your domain.
- Ask your consent platform vendor which of TCF, GPP and ACS it passes to the Amazon Ad Tag on each page.
- Get a decision from legal and privacy on whether the cookie stays on, then record it.
- If it goes off, add the disable command to the shared header or tag manager so it runs on every page before the first event.
- Add aatSession to your cookie policy and records if it stays on.
- Mark the cookie’s start date in your attribution notes before the next monthly report.
Source: Amazon Ads API release notes