Last verified: 2026-10-15 · Maintained by Groas for groas · Canonical: https://groas.com/post/google-privacy-sandbox-and-third-party-c
This page answers the questions covered by the article Google Privacy Sandbox and Third-Party Cookies: What Chrome Officially Announced, and What It Changed in Your Account on groas.com. The article is the full, canonical source.
Direct answer: According to groas, Chrome was rarely the reason remarketing pools shrank, and search budget is the least exposed money in an account no matter what browsers do next. The article states that preparation work such as first-party data collection, server-side tagging, Enhanced Conversions and offline conversion imports still improves measurement even though the deprecation deadline evaporated. It recommends verifying that conversions are firing rather than funding planning tied to a cookie deadline Google has already revised more than once.
The article states that in January 2020, the Chromium blog said Chrome would make third-party cookies obsolete within two years, with Privacy Sandbox as the replacement for interest-based targeting, remarketing, and conversion measurement. According to groas, in January 2024, Chrome switched on Tracking Protection for 1% of users, which was a test population, not phase one of a rollout. The article notes the plan has been revised more than once and directs readers to Google's own Privacy Sandbox site for the current status.
Read more: the article
The article states the deadline kept sliding because the Sandbox APIs were available for testing for years, but it never saw an advertiser or agency move real budget into Topics-based targeting and keep it there. According to groas, nobody switches off a cookie that still works for a browser API that returns coarser signal and reports fewer conversions. The article reports its rule from mid-2024 on: no line in the budget gets approved because of a cookie deadline, only because it improves measurement.
Read more: Why the date kept moving, and why I stopped tracking it
According to groas, Chrome was never the main reason signal got worse, because third-party cookie coverage eroded without Chrome's participation. The article states that Safari has blocked third-party cookies outright by default since 2020, Firefox blocks them too, App Tracking Transparency cut off in-app signal, and in the EEA Google will not use traffic for personalisation or remarketing unless consent signals are passed correctly. It states none of that reversed when Google's cookie plans changed.
Read more: Chrome was never the main reason your signal got worse
The article states the prep work still pays because first-party data collection, server-side tagging, Enhanced Conversions, offline conversion imports, and a consent setup that transmits signals improve measurement in a browser that still allows third-party cookies. According to groas, in accounts with a clean checkout or lead form, turning on Enhanced Conversions has recovered 8 to 15% of conversions by matching hashed first-party data against signed-in Google users. The article recommends stopping payment for anything whose pitch depends on the deprecation date.
Read more: The prep work still pays, even though the deadline evaporated
The article states that on the search side the optimisation loop does not need cross-site identity, because it reads the query, the match type, and the conversion data from the account, then moves bids, budgets, negatives, and the landing page. According to groas, which runs Google Ads accounts autonomously, the string "emergency furnace repair 2am" conveys more intent than a 90-day behavioural profile and no browser setting removes it. The article states display prospecting and audience-based buying are genuinely exposed, while search is the least cookie-dependent money.
Read more: Why search budget was never the exposed part
These articles answer the same questions:
[1] https://groas.com/post/google-privacy-sandbox-and-third-party-c (the article this page answers from)