Google plans to disable third-party cookies for 1% of Chrome users and migrate them to Privacy Sandbox in Q1 2024 and then do so for all Chrome users in H2 2024
Frederic Lardinois / TechCrunch :
Context & Ripple Effects
Google’s cookie-removal plan traces back to its 2020 commitment to end third-party-cookie support, but the timetable was later pushed to H2 2024 to allow more Privacy Sandbox testing. This 1% rollout turns that extended testing period into a defined production trial.
The move also fits the subsequent plan to make Privacy Sandbox APIs available to developers, making Chrome’s migration schedule consequential for the ad-tech ecosystem built around browser-level identifiers.
First-order effects
- Chrome users in the 1% Q1 2024 cohort would lose third-party-cookie access, while sites and ad-tech providers would have to operate through Privacy Sandbox mechanisms for those users.
- Google gains live compatibility and performance feedback before attempting the planned broader Chrome phase-out in H2 2024.
Second-order effects
- Advertisers, publishers, and measurement vendors would need to test targeting, attribution, and fraud workflows against the 1% cohort rather than rely solely on cookie-based implementations.
- A successful test raises the cost of delaying Privacy Sandbox integration for vendors whose products depend on Chrome traffic; failures would strengthen the case for further timing or implementation changes.
Third-order effects
- If Chrome completes the transition, browser owners become more central in setting the technical rules for advertising identity and measurement, shifting power away from interoperable third-party identifiers.
- The pattern points to privacy changes arriving through controlled browser experiments and API migrations rather than a single clean cutoff, with rollout timing remaining contingent on ecosystem readiness.
The trend: This is one data point in the shift from open third-party tracking toward browser-governed privacy and advertising infrastructure.