Chrome kept them, and a lot of advice never got the message

Third party cookies card showing 2025, the year Google retired most of Privacy Sandbox and kept them
Contents 7 sections

A great deal of marketing advice written between 2021 and 2025 opens by telling you that third party cookies are going away. They are not, at least not in Chrome, and Google said so plainly in October 2025.

That matters less for what it changes and more for what it reveals. A whole layer of confident content is built on a deadline that was cancelled, and almost none of it has been rewritten.

This is for you if you have been told to prepare for a cookieless future and want to know what is actually true.

What Google actually announced

On 17 October 2025 Google retired most Privacy Sandbox technologies, including Topics, Protected Audience and the Attribution Reporting API.

The wording on Chrome itself is worth quoting exactly, because paraphrases have already started drifting: “Chrome will maintain our current approach to offering users third party cookie choice in Chrome.”

The reason given was low adoption. The industry was invited to move to the replacements and largely did not.

So the position today is that third party cookies continue in Chrome, users retain a choice about them, and the elaborate replacement scheme built to succeed them has mostly been shut down.

Why the replacements for third party cookies did not take

Because they cost money to use, and that was measurable.

Testing by the UK competition authority, reported by PPC Land, found publisher revenue fell roughly 30% using Privacy Sandbox instead of third party cookies. Individual advertisers testing it saw spend fall by 42%, 60% and 67%. Click-through rates dropped between 12% and 67%. Google’s own demand-side platform testing showed a 14% drop.

Attribute that as competition authority testing reported by PPC Land, rather than as a figure you traced to the source yourself, because that is what it is.

Those numbers explain the outcome without needing a conspiracy. Nobody adopts a replacement that costs them a third of their revenue, and a standard nobody adopts eventually gets withdrawn.

What third party cookies never controlled anyway

The deadline was wrong. The direction was not, and confusing those two is the mistake this article exists to prevent.

Safari and Firefox have blocked third party cookies by default for years. That was true before this announcement and is still true after it. Depending on your market, that is a substantial share of your audience already invisible to cookie-based measurement.

Consent requirements are independent of browser policy. Where a visitor declines, you lose the data regardless of what Chrome permits.

Apple’s App Tracking Transparency did its damage in 2021 and none of it was reversed. Research by Aridor, Che, Hollenbeck, Kaiser and McCarthy measured a 36.6% relative reduction in click-through rates on conversion-optimised Meta campaigns after that change, with a 95% confidence interval of 18.2% to 54.5%, across 1,221 firms.

So partial visibility is your normal operating condition. It always was. Chrome’s decision changes the slope, not the destination.

How to spot third party cookies advice that never got updated

There is a quick test, and it is worth applying because this content is still ranking.

If an article opens with a phrase like “with the deprecation of third party cookies” as a coming event, it was written against the old timetable and has not been revised. That does not automatically make everything in it wrong, and it does mean the urgency it is selling you is stale.

Be especially careful with anything selling a product on that premise. A large number of measurement tools were positioned entirely as the answer to a deadline that no longer exists, and the marketing has not caught up with the announcement.

Date-stamped claims are your friend here. “As of October 2025” tells you when somebody last checked. “Currently” tells you nothing at all.

What I would actually do differently

Very little, and that is the honest answer rather than a disappointing one.

Everything worth doing for measurement was worth doing for reasons other than the Chrome timetable. Capturing your own customer data, connecting your CRM back to the ad platforms, running server side where you already have the access. None of that was a response to a deadline.

What I would stop doing is rebuilding measurement architecture in a hurry. If a plan’s justification was “cookies are going away next year”, that plan needs a new justification before it gets any more budget.

And I would treat the whole episode as a reminder about how this industry works. A confidently announced deadline moved four times and then got cancelled, while the content built on it kept ranking.

What this says about buying advice on third party cookies

There is a lesson here that outlasts the cookie question itself.

An entire consulting and tooling market grew up around a date. The date slipped, slipped again, and then vanished. Very little of the material sold against it has been withdrawn or corrected, because there is no mechanism that forces a correction.

So the practical skill is not knowing the current state of third party cookies. It is knowing how to check. Two habits cover most of it.

Look for the date the claim was made, in the sentence rather than in a byline. A claim that says “as of October 2025” can be assessed. A claim that says “currently” cannot, and “currently” is doing an enormous amount of quiet work across this topic.

Then look for who benefits from you believing it. Not as cynicism, just as context. A company selling a replacement for something has an interest in that thing ending, and that interest does not make them wrong. It does mean their timeline deserves a second source.

Both habits take seconds. Between them they would have saved a lot of people a lot of rebuilding.

What to change this week

Three things.

Check whether any measurement project in your plan is justified by the deprecation of third party cookies. If it is, rewrite the justification or drop the project.

Then find out what share of your own traffic is Safari and Firefox. That is your existing blind spot, and it is usually larger than people expect.

Then keep the first party work going, because none of the reasons for it depended on Chrome.

What conversion numbers actually measure covers what you can and cannot see, the four ways the number goes wrong covers the failure modes, and platform reported conversions explains why two systems disagree even when both are working. For how benchmark claims get repeated long past their sell-by date, most cost per lead benchmarks are recycled is the same problem in a different topic. The case studies show what the measurement looks like once it is honest, and you can book a teardown if you want yours checked.

Frequently asked questions

Are third party cookies going away?

Not in Chrome. On 17 October 2025 Google retired most Privacy Sandbox technologies and said it would maintain its current approach to offering users third party cookie choice. The reason given was low adoption. Safari and Firefox blocked them years ago and that has not changed.

So was the whole cookieless panic wrong?

The deadline was wrong. The direction was not. A large share of your traffic already blocks these cookies through Safari and Firefox, and consent requirements bite whatever browser somebody uses. Chrome changed its timetable, not the underlying trend.

What was Privacy Sandbox meant to replace third party cookies with?

A set of technologies Google built so advertisers could target and measure without them, including Topics, Protected Audience and the Attribution Reporting API. Most were retired in October 2025, after the industry largely declined to adopt any of them.

How did the replacements for third party cookies perform?

Badly, which is much of why they were dropped. Competition authority testing reported publisher revenue falling roughly 30% under Privacy Sandbox. Individual advertisers testing it saw their spend fall by considerably larger margins than that.

Does this mean I can stop worrying about first party data?

No, and this is the trap. The reasons to build first party data never depended on Chrome's timetable. Consent rules, Apple's tracking changes and ad blockers all reduce what you can see today, whatever Chrome decides to do.

How do I tell if an article about third party cookies is out of date?

Check whether it announces their deprecation as a future event. A large amount of content published between 2021 and 2025 rests on a premise that turned out not to happen. Most of it has never been revised, and much of it still ranks.

Which browsers still block third party cookies?

Safari and Firefox both block them by default and have done for years. Between them that is a substantial share of most audiences, particularly on mobile in markets where iPhone use runs high. Partial loss is your normal condition.

What should I actually do about it?

Nothing dramatic. Keep building first party data, keep your server side connections where you already have them, and stop rebuilding measurement around a deadline that got cancelled. The work that was worth doing before is still worth doing now.

Want a second pair of eyes on your account?

Book a free teardown

Book a free teardown

Send me your worst-performing campaign.

I will tell you what is wrong on the first call. No obligation, no hard sell, and I will say honestly if I am not the right fit.

Book a free 20-minute account teardown

Replies within one business day, Lahore time.