Chrome did not get rid of third-party cookies. According to Usercentrics, Google announced in July 2024 that it would not deprecate them, and it then retired the remaining Privacy Sandbox APIs in October 2025, including Attribution Reporting, Topics and Protected Audience.
One caution before going further: Google's own Privacy Sandbox announcement page and Chrome's cookie help page were not checked for this article. Treat the dates below as one vendor's summary, and confirm them against Google before you make a business decision on them.
What is a third-party cookie, in plain terms?
Say you look at a pair of running shoes on a shop's website. Later you open a news site and see an ad for those same shoes. That is the kind of thing third-party cookies make possible: a small file set by a company other than the site you are on, which can recognise your browser as you move between different sites.
The cookie the shoe shop sets for your basket is a first-party cookie. The one an ad network sets on both the shop and the news site is third-party. The long argument over Chrome was always about the second kind.
So what was Privacy Sandbox supposed to do?
Privacy Sandbox was Google's set of browser features meant to stand in for third-party cookies once Chrome stopped supporting them. The three names you will see most often are the ones Usercentrics lists as retired:
- Topics: the browser itself would hand advertisers broad interest categories instead of letting them track individual visits.
- Protected Audience: a way to run retargeting, like the shoe ad above, inside the browser rather than through a cross-site cookie.
- Attribution Reporting: a way to tell an advertiser that an ad led to a purchase without tying it to a cross-site identity.
The plan only made sense if cookies were going away.
Check Chrome's default cookie setting on Google's help page
The Usercentrics page says Google did not deprecate third-party cookies in Chrome. Chrome's own help page on cookie controls was not read for this article, so it does not spell out what your copy of Chrome does out of the box. Check Google's help page for the current default and the options available to you.
If your code uses Topics, Protected Audience or Attribution Reporting
If you maintain code or ad setups built on any of these, treat the retirement described above as a strong signal to check Google's developer documentation before assuming they still work.
Why is there so much confusion about this?
Because the story reversed. For years the headline was that Chrome would kill third-party cookies, and plenty of guides, vendor pages and agency decks were written on that assumption. If an article tells you cookies are about to disappear from Chrome, look at when it was written.
What you should do differently now
If you just browse with Chrome: do not assume Chrome is blocking cross-site tracking for you. This article does not give menu steps, because Chrome's cookie help page was not checked for it. Look up Google's Chrome help page on cookies for the current menu names and options.
If you run a website: do not plan around a cookieless Chrome that, on this account, is not coming.
If you build or buy ad tech: stop planning work on Topics, Protected Audience or Attribution Reporting until you have confirmed their status in Google's own documentation. A vendor summary is a starting point, not a source to ship code against.