Navigating M&A, Privacy Sandbox & Alternatives As The Cookie Crumbles

Timeline showing Google's reversal of third-party cookie deprecation and the shutdown of most Privacy Sandbox APIs
Six years of industry preparation, built around a deprecation that never happened.

This piece was written for a Privacy Sandbox era that was supposed to arrive. It didn’t. Google kept third-party cookies and shut down most of the project meant to replace them. Here’s what that actually means for how adtech should be thinking about identity now.

For six years, the digital advertising industry planned around a specific assumption: Chrome would deprecate third-party cookies, and Privacy Sandbox APIs would be the replacement. Neither happened as planned. If your identity strategy still has a line item for “prepare for cookie deprecation,” it’s worth revisiting.

What actually happened to Privacy Sandbox

On 22 April 2025, Google confirmed it would not deprecate third-party cookies in Chrome, and would not introduce the standalone “choice prompt” it had floated as a fallback either. Third-party cookies stayed on by default, managed through Chrome’s existing privacy settings rather than any new consent mechanism. Then, on 17 October 2025, Google retired ten of the remaining Privacy Sandbox APIs, including Topics, Protected Audience (the rebuilt FLEDGE), and Attribution Reporting, the core pieces that were meant to actually replace cross-site tracking functionality. Only a handful of narrower components, CHIPS, FedCM and Private State Tokens, survived.

Why the reversal happened

Google never gave a single official reason, but the public record points to a few converging pressures: the UK Competition and Markets Authority’s ongoing scrutiny of whether Privacy Sandbox itself entrenched Google’s advertising position rather than reducing it, industry testing that reportedly found meaningfully weaker attribution accuracy in Privacy Sandbox tools compared to cookie-based measurement, and six years of limited voluntary adoption even where APIs were already available. Whatever the internal weighting of those factors, the practical effect was the same: a six-year, industry-wide infrastructure project ended without delivering the replacement it was built to be.

It’s worth being fair to the scale of what was attempted here. Privacy Sandbox wasn’t a minor product, it was Google’s proposed answer to one of the hardest open problems in digital advertising: how to preserve useful measurement and targeting without individual-level tracking. That it didn’t work as intended isn’t evidence the problem was easy or that Google didn’t try seriously to solve it. It’s evidence that the problem is genuinely harder than a single browser vendor, however dominant, could solve unilaterally while also satisfying regulators, publishers and advertisers all at once.

What survived, and what didn’t

StatusWhat it means practically
Third-party cookies: stay on by default in ChromeNo forced migration off cookie-based measurement for Chrome traffic
Topics, Protected Audience, Attribution Reporting: retiredThe core cookieless targeting and measurement APIs are gone, not paused
CHIPS, FedCM, Private State Tokens: still activeNarrower, specific-use utilities remain, not a general cookie replacement
Safari, Firefox, Brave: still block third-party cookiesRoughly 30% of browser traffic was never affected by this reversal at all

Where the capital went instead: identity M&A, not a shared standard

Privacy Sandbox was, at its core, an attempt to solve identity and measurement through a shared industry standard rather than through any single company’s proprietary infrastructure. That attempt failed. What replaced it wasn’t another standard, it was acquisition. Adtech and martech M&A ran hot through 2025, roughly 465 deals, up 13% on the prior year, and buyer focus concentrated specifically on incrementality measurement, identity resolution and AI-driven performance, the exact capability set Privacy Sandbox was meant to deliver as shared infrastructure. The clearest single example: The Trade Desk’s acquisition of Sincera, a supply chain transparency data company, a direct bet on buying the transparency and identity capability that a six-year standards effort couldn’t deliver by consensus. The fuller picture of 2025’s deal activity is covered in the State of the Market hub.

The practical read for anyone building an identity roadmap now: the industry’s answer to “how do we solve measurement without a universal standard” turned out to be “buy the company that already solved a piece of it.” That’s a genuinely different planning assumption than waiting for Privacy Sandbox, or its successor, to arrive. Whether to build identity infrastructure in-house, partner for it, or acquire a piece of it outright is now a live strategic question in its own right, covered from the investment-decision side in Our Guide To Making Wise Marketing Technology Investments and from the platform-dependency side in CDP Considerations.

Related Reading
Free Tools

Need to put a number on your next media decision?

Model the impact of a media or marketing decision on your own numbers, browse the full library of strategic calculators and decision tools, and get definitions straight on the industry terms that come up along the way, three free resources, ready whenever you need them.

Try the calculators → Explore strategic decision tools → Browse the glossary →

What this means for adtech’s identity strategy now

The mistake would be reading this reversal as “nothing changes, cookies are back.” Chrome keeping cookies doesn’t undo years of Safari and Firefox blocking them, doesn’t touch Apple’s own privacy-preserving frameworks covered in What Is Apple’s Private Click Measurement, and doesn’t change GDPR or ePrivacy consent obligations, which apply to cookies regardless of what Chrome’s default setting is. What it does change is the urgency and shape of migration: the specific Privacy Sandbox APIs many teams had begun integrating against are gone, and any roadmap built around them needs a genuine rework, not a pause.

The more durable lesson: identity strategy built around a single browser vendor’s roadmap, however dominant that vendor is, carries real platform risk. First-party data infrastructure and modelled measurement, the direction covered across Multi-Touch Attribution and CDP Considerations, turned out to be the more durable bet regardless of which way Chrome’s policy ultimately went.

The teams best positioned right now are the ones who treated Privacy Sandbox preparation as one input into a broader first-party strategy rather than the whole strategy. If your roadmap had a single point of failure named “Privacy Sandbox,” this reversal is the forcing function to fix that structurally, not just to update the specific line items that are now obsolete.

Free Playbook

The Customer Data Strategy engagement model covers building identity and measurement infrastructure that doesn’t depend on any single platform’s roadmap holding steady.

Get the Executive Playbooks
Common Questions

Adtech and Privacy Sandbox: FAQ

Are third-party cookies safe to rely on again?

In Chrome, they remain available by default, but Safari, Firefox and Brave still block them, representing a meaningful share of traffic that was never affected by Chrome’s policy either way. Relying solely on cookie-based measurement still leaves a real, permanent gap.

Should we abandon work already done to prepare for Privacy Sandbox?

The specific API integrations, yes, since the underlying APIs are retired. The broader first-party data and consent infrastructure built alongside that preparation generally remains useful regardless, since it doesn’t depend on the specific Privacy Sandbox tools that were shut down.

Could Google reverse this again and revive cookie deprecation?

Nothing rules it out, but reintroducing deprecation would mean rebuilding replacement infrastructure largely from scratch given how much of Privacy Sandbox was retired, which makes a near-term reversal of the reversal unlikely even if not impossible.