To curb tracking, Google says anti-fingerprinting tech is coming in Chrome and devs must explicitly opt-in for cookies that are meant to be used across sites
Google today announced a major new initiative around its Chrome browser that will, in the long run, introduce significant changes …
Context & Ripple Effects
This May 2019 announcement is the seed of an arc that ran for years: months later, Google's Chrome team turned the same ideas into an open anti-fingerprinting standard proposal, and by late 2023 they hardened into a dated plan to kill third-party cookies outright via a 1% user test and a Q3 phase-out.
What makes the opt-in requirement significant is that it flips the default: cross-site cookies stop working unless developers affirmatively declare them, while anti-fingerprinting closes the workaround trackers would otherwise use once cookies disappear.
First-order effects
- Developers whose cookies are meant to work across sites must now explicitly opt in or those cookies stop functioning in Chrome.
- Ad-tech firms relying on passive cross-site tracking lose both their cookie path and, as anti-fingerprinting lands, their fallback technique in the world's largest browser.
Second-order effects
- Advertisers and marketers are pushed toward whatever replacement Google proposes, giving the company that sells the most ads control over the standards its rivals must adopt — the dynamic the later Privacy Sandbox rollout formalized when Google began testing Tracking Protection on ~1% of users (scheduled for January 4, 2024).
Third-order effects
- Browser makers become de facto regulators of web tracking: defaults set by Chrome, not legislation, determine what cross-site identification is possible at all.
- If the pattern holds, web advertising restructures around opt-in signals and platform-supplied APIs rather than open third-party identifiers, concentrating measurement power with the companies that operate the browsers and the biggest ad networks.
The trend: Browsers are dismantling ambient web tracking piece by piece — first cookies made opt-in, then fingerprinting blocked — replacing it with platform-controlled privacy APIs on Google's timeline.