twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Amazon's ad tag now sets a 30-day cookie on your website by default. Update your cookie list, then decide if you want it

If your site runs Amazon's ad tag, there's a new cookie on your domain called aatSession, and your privacy notice probably doesn't mention it. Amazon switched it on for North American sites without anyone having to install anything.

Editorial engraving of a developer at a kitchen table lifting a cookie from a jar beside his laptop while a colleague holds a printed list, ready to add to it.

Amazon Ads says its Amazon Ad Tag now sets a first-party cookie, aatSession, on advertiser websites in North America, on by default, lasting 30 days after a visitor's last page view and used only when consent signals allow. If your site runs the tag, add the cookie to your cookie list and consent settings, check what your site actually sets, then decide whether to keep it; switching it off takes one line on every page.

A cookie nobody on your team added

If your website runs the Amazon Ad Tag, the snippet that reports visits and purchases back to Amazon for your ad campaigns, your list of cookies may be out of date as of this week.

According to an Amazon Ads release note dated November 16, reported in detail by PPC Land, the tag "now sets a first-party cookie, aatSession" on advertiser websites in North America. It's on by default. Nobody has to install anything or change a setting. If you want it off, you have to add a line of code to every page.

A cookie you didn't add is still a cookie you have to explain. Your privacy notice, your cookie banner and your consent settings are all supposed to describe what your site stores in a visitor's browser. Amazon just changed that without a deploy on your side.

What the cookie does

From Amazon's note and its Ad Tag guide, as quoted by PPC Land: aatSession holds an identifier "that links the events a visitor triggers on your website, so Amazon Ads can measure and attribute those events more reliably as third-party cookies are phased out." It's set on your own domain, which makes it first-party. It expires 30 days after the visitor's last page view, so a visitor who comes back weekly keeps the same identifier for as long as they keep returning. TrackingDesk, which analyzed the change, points out that this makes it closer to a visitor ID than to what most analytics tools call a session.

Amazon says the tag sets, reads and sends the identifier "only when the visitor's consent signals allow it," naming the IAB's TCF and GPP frameworks and Amazon's own Consent Signal. It joins a cookie the tag already sets, amznAref, which stores a click token for 30 days when someone arrives from an Amazon ad.

Neither Amazon's note nor its guide answers some obvious questions, as PPC Land lists them: what happens when a visitor arrives with no consent signal at all, which countries "North America" covers, and how long the cookie really lasts in Safari. TrackingDesk adds two details. Amazon's consent guide labels its U.S. example "no consent signal required," and Safari's tracking prevention caps cookies written by JavaScript at seven days without a visit, so the 30 days won't hold there.

Sequence of work

How Amazon's tag got here

  1. Oct 2024

    Amazon Consent Signal introduced for advertisers outside the IAB framework.

  2. Dec 1, 2025

    Country code required on personal data; consent signal required for UK and EEA.

  3. Jun 30, 2026

    Unconsented UK and EEA data stops being processed.

  4. Nov 14-16, 2026

    Release note: aatSession cookie on North American sites, on by default.

Dates from Amazon Ads release notes as reported by PPC Land (source: ppc.land), 2024-2026.
A cookie you didn't add is still a cookie you have to explain.

Three documents it touches

The first is your cookie inventory and privacy notice. If they list cookies by name, add aatSession, and check amznAref is there too. Describe what it does in plain words: an Amazon advertising identifier that links a visitor's activity on your site for up to 30 days after their last visit.

The second is your consent tool. Most consent platforms scan the site and sort cookies into categories, but scans run on a schedule, and a new cookie can sit in "unclassified" for a while. Put both Amazon cookies in the advertising or marketing category, so they follow the visitor's choice. Then check what your banner sends to Amazon's tag when a U.S. visitor never clicks anything, since that's the case Amazon's documentation leaves open.

The third is your reporting. If your team compares Amazon-attributed conversions before and after this month, some of the change may come from how Amazon groups events now, not from your campaigns. Write that down next to the November numbers. If a lot of your customers use iPhones, expect the Safari difference to show up too.

If you run consent differently by region, check each version of the banner, not just the one you see from the office. A visitor in California, one in another state and one in Canada may each get a different default, and the Amazon tag sees whatever signal that version sends.

Keep it, or switch it off

This is a real choice, and there's no single right answer. Keeping the cookie probably helps Amazon connect ad clicks and site visits to purchases, which matters if Amazon ads are a big part of how you're found. Turning it off means one fewer identifier on your domain and a simpler privacy notice, at some cost to measurement that Amazon hasn't quantified.

If you decide to turn it off, the documented way is one command, amzn("disableAATSessionCookie", true);, placed in the tag's base code before the first event fires. The guide says the setting applies only to the page it runs on, so put it in a shared header or your tag manager, not a single template. Running it deletes any existing aatSession cookie, and passing false later won't bring it back on that page; removing the line does. If you use Amazon's Google Tag Manager template, version 4.1 adds a checkbox for this, unchecked by default, according to the merged change on Amazon's GitHub. Turning the cookie off doesn't stop the tag: events and hashed identity signals keep working, and Amazon marks events from sites that disabled it.

Whoever decides, write it down. The decision belongs to the people who run Amazon advertising and whoever owns privacy, together, not to whoever happens to be editing the tag manager that week. Record what you chose, why, and the date, and set a reminder to look again when Amazon answers the open questions about consent and Safari. If you change your mind later, you'll want to know what the numbers looked like on either side of the switch.

How the work moves

Keep it or switch it off, then check

  1. List

    Add aatSession (and amznAref, if missing) to the cookie inventory and notice.

  2. Classify

    Put both in the advertising category of your consent tool.

  3. Decide

    Does the measurement gain justify another identifier on your domain?

  4. Implement

    If off: the disable line before the first event on every page, or the GTM v4.1 checkbox.

  5. Verify

    Visit with consent accepted, then declined, and read what the browser stored.

Decision framework for your own site; not legal advice and not an Amazon procedure.

Check what your site actually sets

Documentation tells you what should happen. Your browser tells you what does. Open your site in a private window, accept cookies, browse a product and add it to the cart, then look at the stored cookies in the browser's developer tools. Do it again declining everything. Write down what appears each time.

TrackingDesk reported that the copy of Amazon's script it downloaded, last modified October 12, didn't yet contain aatSession. A recheck on November 18 found a newer build, last modified November 16, that does: it names the aatSession cookie and the disableAATSessionCookie command, and it writes the cookie from JavaScript in the browser, which is the path Safari caps at seven days without a visit. That still leaves the consent-default and country questions open, so check what your own site sets, and check again after any tag manager change.

Keeping a site's tags, consent setup and privacy pages in step with each other is ongoing work, and it's part of what we do on web applications we build and run. Talk to us.

Related work: Sutton|Place

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎