Chrome's Third-Party Cookie Blocking Reshapes Login and Ad Measurement

06 October 2026

The long-planned deprecation of third-party cookies in Chrome is intensifying, with Google recently expanding its restriction tests to 1% of users. This browser-level privacy shift is upending core adtech infrastructure and resetting the tech stacks for many embedded login flows.

Google has introduced several third-party cookie blocking controls for users and enterprise teams. Disabling third-party cookies via Chrome’s main settings or the chrome://settings/cookies path blocks these cookies across all sites by default. Developers working with enterprise groups can use the Chrome setting paths alone or with policies like BlockThirdPartyCookies and CookiesAllowedForUrls.

Google’s documentation highlights the scope of this change. Since 2024, the web platform team has noted the broad effects of third-party cookie changes, including impacts on authentication, fraud detection, ad delivery, and embedded services. With the latest restrictions, Chrome can now block third-party cookies in all contexts, even where previous exceptions would permit them. Google's testing tool suggests flags like --test-third-party-cookie-phaseout and chrome://flags/#test-third-party-cookie-phaseout for simulating the changes.

Reports of issues have increased since Chrome began restricting third-party cookies by default during testing last year under CMA oversight. With many developers reporting significant functionality breaks, the full impact of the deprecation remains uncertain for the industry, even as enterprise administrators gain extensive control over the feature's behavior.

---