Amazon announced that its advertising tag will create a 30-day first-party cookie on advertiser websites. The change, effective immediately, lets Amazon capture a session identifier for every page view or purchase. Marketers must now ensure consent signals like TCF, GPP or ACS are in place, or data from the UK and EEA will be blocked.
What happened
- Amazon Ad Tag (AAT) now creates and reads a session identifier that lives for 30 days on the advertiser’s domain.
- The identifier is attached to every event the tag records, such as page views or purchases, and is sent back to Amazon.
- No extra code or tag configuration is required; the mechanism works out of the box, as the guide states advertisers do not need to add code or change settings.
- The identifier is only set, read, and transmitted when a visitor’s consent signal permits it. Accepted signals include TCF, GPP and ACS.
- Amazon’s guide prints an off-switch inside an example of the tag’s base code for easy disabling.
- The rollout follows a series of consent-related updates dating back to October 2024, culminating in a hard deadline of June 30, 2026 for UK and EEA consent signals.
Why it matters
- Advertisers gain a richer, cross-site view of conversions because the cookie bridges the gap between Amazon’s authenticated graph and visits to an advertiser’s own site.
- Amazon reported third-quarter 2026 advertising revenue of $19.64 billion, up 11%, underscoring the scale of its ad ecosystem and the impact of measurement changes.
- Failure to provide a valid consent signal will cause data from UK and EEA users to be dropped, mirroring Google’s recent Consent Mode V2 enforcement that cut one advertiser’s conversions by 90% overnight.
- The session identifier will appear only on visits with consent, creating a split in reporting that could skew ROAS and attribution if not accounted for.
What this means for marketers
- Ensure your consent management platform can pass TCF, GPP or ACS signals together with the required country code to Amazon’s tag.
- Audit your reporting pipelines; the new cookie will affect both Amazon Marketing Cloud analyses and any downstream dashboards that rely on AAT, the Conversions API or the Events API.
- Consider supplementing Amazon data with first-party analytics to fill gaps when consent is missing, especially for EU traffic.
- ADFLU’s verified lead generation service can help filter out low-quality leads that may arise from incomplete consent data, keeping your pipeline clean.
"Please do not send multiple signals. If multiple are provided, Amazon Ads will use TCF and ignore ACS," Amazon release notes
The bottom line
Amazon’s 30-day first-party cookie gives advertisers deeper insight into cross-site conversions, but it also forces stricter consent compliance. Marketers must integrate a consent management platform, adjust attribution models for consent-driven data gaps, and monitor performance closely to avoid unexpected drops in reported ROAS.
Sources
- 1.ppc.land
