Chrome's 1% third-party cookie restriction and a readiness checklist
Chrome will restrict third-party cookies for 1% of users from January 4. It will not move your numbers much, but it is a cheap prompt to find out which of your tags depend on them.
On December 14, Google said that starting January 4 Chrome will begin testing a feature called Tracking Protection, which restricts website access to third-party cookies by default, for 1% of Chrome users globally. Google also said it plans to phase out third-party cookies for everyone in the second half of 2024, subject to addressing remaining competition concerns raised by the UK's Competition and Markets Authority. The test will not noticeably change your results in January. Its value is as a deadline you can plan around.
What was actually announced
Participants are chosen at random and are notified when they open Chrome on desktop or Android. If a site appears broken, and Chrome detects problems such as repeated page refreshes, users can temporarily re-enable third-party cookies for that site using an icon in the address bar. Google said developers can use the test to check their readiness for a web without third-party cookies.
The wider date is conditional. Earlier in the year, Google's timeline put full-scale removal at the third quarter of 2024, and The Register later corrected its report to say removal would begin from then, dependent on the CMA's concerns. Treat any date beyond January as provisional.
Size the exposure with simple arithmetic
Before you worry, work out how much it could matter. Suppose Chrome accounts for 60 percent of your web traffic. One percent of Chrome users is then about 0.6 percent of your visitors. If a quarter of your conversions depend on third-party cookies, the affected share of conversions in the test is a fraction of a percent. These numbers are hypothetical; substitute your own browser mix from your analytics.
The test is small, but it is not zero, and it is the only chance you have to see real behavior before the wider change. The point is not the 1%; it is that you now have a calendar.
A readiness checklist
- List every third-party cookie your site sets or relies on. Use your browser's developer tools on key pages, including the checkout or sign-up flow. Group them by purpose: advertising, analytics, login, payments, embedded content.
- Test your site with third-party cookies blocked. Chrome's cookie settings let you block them. Walk through your main funnel and note what breaks, especially anything in an embedded frame such as payments, chat, video or single sign-on.
- Check your ad platform tags. Confirm that your Google Ads and Meta setups also send first-party and server-side signals, because those do not rely on a cross-site cookie. Look at which events are sent only from the browser.
- Review conversion tracking across domains. If a purchase happens on a different domain from the one hosting your ads, test that path with cookies blocked. Cross-domain setups are the most likely to fail quietly.
- Audit your consent and data collection. First-party data is only useful if it was collected with the right permission. Make sure your consent setup is working before leaning on it harder.
- Set up a comparison. Before January 4, record Chrome conversion rates by channel, so you can see whether anything shifts in the weeks after.
What not to do
Do not rebuild your measurement around the Privacy Sandbox proposals on the strength of this announcement. They are still being evaluated by the CMA, and the date is conditional. A first-party and server-side foundation is a safer investment, because it also helps in other browsers and in apps, where Chrome's decision has no effect.
Do not, either, treat January as a fire drill. If your site breaks for a tiny share of users, you will hear about it from customer support or from conversion data for that segment. Make sure whoever reads that data knows what to look for.
Where this leaves mobile app advertisers
This announcement concerns Chrome. If your campaigns drive installs via app store links, they do not depend on web cookies directly. But if you run web-to-app funnels, retargeting based on web visits or measurement that joins web sessions with installs, then your web pieces are exposed. Check the web steps of those funnels first.
The takeaway: use January 4 as the date by which you have a cookie inventory, a blocked-cookie test of your main funnel and a baseline for Chrome conversion rates.