On this page
Privacy Sandbox
Privacy Sandbox
Google's Privacy Sandbox was a 2019 initiative to replace third-party cookies in Chrome with privacy-preserving browser APIs for advertising, attribution, and fraud prevention. By October 2025 most of its advertising APIs had been retired due to low adoption; a small set of non-advertising features were retained and remain active in Chrome.
Background
Google announced Privacy Sandbox in 2019 and committed in January 2020 to phase out third-party cookies in Chrome within two years. The deprecation was delayed four times — June 2021, July 2022, April 2024, and July 2024 — before being reversed entirely (Hidekazu Konishi blog, 2026-10-02).
On April 22, 2025, Google formally abandoned the planned standalone user-choice prompt for third-party cookies, leaving them on by default in Chrome with no deprecation date (Didomi, 2025-04-29; Privacy Sandbox Feedback Report Q1-2025, 2025-04-30).
The three advertising APIs
The core Privacy Sandbox advertising stack (Privacy Sandbox status page, 2026-08-14):
| API | Purpose | Status (as-of 2026-10-24) |
|---|---|---|
| Topics API | Browser infers weekly interest topics from browsing history for targeting | Retired — removed from Chrome |
| Protected Audience API (PAAPI / FLEDGE) | On-device remarketing auctions; advertiser lists stay in the browser | Retired — removed from Chrome |
| Attribution Reporting API | Conversion measurement without cross-site user-level data | Retired — removed from Chrome |
October 2025 retirement announcement
On October 17, 2025, Google VP Anthony Chavez announced the retirement of most Privacy Sandbox technologies, citing "low levels of adoption" by the ad industry (Privacy Sandbox blog, 2025-10-17).
Full list of retired APIs: Topics (Chrome + Android), Protected Audience (Chrome + Android), Attribution Reporting (Chrome + Android), Private Aggregation API, Shared Storage, IP Protection, On-Device Personalization, Protected App Signals, Related Website Sets (including requestStorageAccessFor and Related Website Partition), SelectURL, SDK Runtime.
On the same day, the UK Competition and Markets Authority released Google from its legally binding Privacy Sandbox commitments — made in 2022 in response to CMA competition concerns — concluding that Google's decision not to deprecate third-party cookies "significantly mitigates" the original concerns. All 15 consultation responses were opposed; the CMA released Google regardless (AdExchanger, 2025-10-17).
Chrome removal timeline (as-of 2026-10-24)
| Chrome version | Approx. date | What changed |
|---|---|---|
| v144 | January 2026 | Deprecations began: Private Aggregation, Shared Storage, Protected Audience |
| v152 | August 25, 2026 | Private Aggregation API removed |
| — | September 30, 2026 | Shared Storage disabled across all channels |
| v153 | September 8, 2026 | Planned removal: Protected Audience, Related Website Sets, Shared Storage, requestStorageAccessFor, Attribution Reporting |
| — | After October 15, 2026 | Topics API 100% removal rollout |
| — | October 26, 2026 | Protected Audience 100% staged removal begins |
| v156 | ~October 20, 2026 stable | Fenced Frames becomes a stub |
Source: Hidekazu Konishi blog (verified 2026-10-02); Privacy Sandbox status page (2026-08-14). All dates volatile (as-of 2026-10-02).
What was retained
Google retained nine features after the retirement (Privacy Sandbox blog, 2025-10-17; Privacy Sandbox status page, 2026-08-14):
- CHIPS (Cookies Having Independent Partitioned State) — partitions third-party cookies by top-level site; prevents cross-site tracking while allowing embedded-widget and CDN-auth use cases; default since Chrome 114; broadly adopted by other browsers (as-of 2026-08-14)
- FedCM — browser-based federated sign-in; broad adoption including other browsers
- Private State Tokens — fraud prevention attestation tokens
- Bounce Tracking Mitigations
- Storage and Network State Partitioning
- Storage Access API (including Storage Access Header)
- User-Agent Client Hints
- User-Agent Reduction
frame-ancestorsdirective
Fenced Frames initially appeared on the "retain" list but was subsequently reclassified to "deprecate and remove," illustrating that classifications can shift after announcement. (Hidekazu Konishi blog, 2026-10-02)
Ecommerce and advertising impact
Remarketing performance gap (as-of 2024-Q1): Google's own live experiment (January–March 2024) comparing Privacy Sandbox APIs vs. third-party cookies found: overall spend recovery was 89% in Google Display Ads and 86% in DV360, but remarketing-only campaigns recovered only 55% and 49% respectively. Google described these as "directional estimates at a fixed point in time." (Google Ads Help, 2024)
No direct replacement product: There is no replacement technology or cookie prompt from Google for the retired advertising APIs. Third-party cookies remain default-on in Chrome, so cookie-based targeting continues to work in Chrome for now (Usercentrics, 2026-02-12).
Cross-browser fragmentation persists: Safari and Firefox continue to block third-party cookies by default regardless of Chrome's reversal; advertisers cannot rely on third-party cookies working universally (Usercentrics, 2026-02-12).
Pre-retirement adoption weakness: As of Q2 2025, buy-side firms were already scaling back Protected Audience API integrations due to operational cost, weak advertiser demand, and low exchange inventory (Privacy Sandbox Feedback Report Q2-2025, 2025-07-30).
Structural programmatic shift (as-of 2025-10-21): Open-exchange programmatic display spending projected to fall from 74.5% share (2013) to 6.7% (2027), while programmatic direct rises from 24% to 76%, reflecting a structural shift toward first-party data and private deals (Axios citing eMarketer, 2025-10-21).
What practitioners are doing
Sources describing advertiser and ecommerce marketing actions in 2026 (Stackmatix, 2026-09-03; Secure Privacy, 2026-08-04):
- Audit cookie dependencies by ad spend impact
- Set up Server-Side Tagging for conversion capture
- Build consented First-Party Data assets
- Shift to modelled / aggregate measurement (Media Mix Modelling, incrementality testing)
- Use geo holdouts or incrementality tests as measurement ground truth
- Reset leadership expectations around lower attribution precision
"Cookies staying is good for advertisers" vs "cookieless investment remains urgent": Secure Privacy and Stackmatix frame third-party cookie survival positively (short-term continuity). Didomi and Usercentrics stress that Safari/Firefox blocking means the threat landscape is unchanged and first-party data investment is still urgent. Secure Privacy, 2026-08-04 VS Didomi, 2025-04-29
"Nothing replaced it" vs "W3C Attribution is the path forward": Usercentrics (2026-02-12) states no replacement technology or prompt exists. AdExchanger (2025-10-17) reports Google VP Chavez citing the W3C Private Advertising Technology Community Group's Attribution proposal as a directional successor. Not strictly contradictory — no working product exists now — but framing diverges. Usercentrics VS AdExchanger, 2025-10-17
Consent and compliance (unchanged)
GDPR / ePrivacy Directive Article 5(3) and CCPA/CPRA consent obligations are unchanged by the Privacy Sandbox retirement; non-essential cookies still require prior user consent regardless of Chrome's cookie policy (Secure Privacy, 2026-08-04).
Google Consent Mode v2 is unrelated to Privacy Sandbox and remains mandatory for EEA and UK traffic on Google Ads, GA4, and DV360; required since March 2024 (Secure Privacy, 2026-08-04).
Industry standards alternatives to the retired APIs
ADMaP (Attribution Data Matching Protocol) v1.0 — IAB Tech Lab standard (February 2025) using Data Clean Rooms and Privacy Enhancing Technologies (PSI, TEEs) to enable advertiser-publisher conversion matching without user-level data exposure. Directly addresses the attribution use case vacated by the retired Attribution Reporting API (IAB Tech Lab, 2025-02-25).
IAB Tech Lab Trusted Server — open-source server-side ad infrastructure (PoC v0.0.2, March 2025; Developer Day September 2026) that moves bidding, identity, and audience functions from the browser into publisher-controlled edge servers, positioning Server-Side Tagging as the post-cookie execution layer for publishers (IAB Tech Lab, 2025-03-01 / Sept 2026).
Key terms
| Term | Meaning |
|---|---|
| CHIPS | Cookies Having Independent Partitioned State — third-party cookies partitioned per top-level site; retained |
| FedCM | Federated Credential Management — browser-based federated sign-in; retained |
| PAAPI | Protected Audience API — on-device remarketing auction (formerly FLEDGE); retired |
| Topics API | Browser-inferred interest topics for ad targeting; retired |
| Attribution Reporting | Cookieless conversion measurement; retired |
| CMA | UK Competition and Markets Authority |
| ADMaP | Attribution Data Matching Protocol — IAB Tech Lab Data Clean Rooms-based attribution standard |
| MMM | Media Mix Modelling — statistical post-cookie measurement alternative |
| Private State Tokens | Fraud prevention attestation tokens; retained |
| W3C PATCG | W3C Private Advertising Technology Community Group — proposed future attribution standard path |