Chrome is moving towards a new experience that lets people make an informed choice with respect to third-party cookies.
You need to prepare your site for users who choose to browse without third-party cookies.
Take action to ensure your sites are prepared
We've broken the process down into these key steps, to ensure you're prepared for your site to run without third-party cookies:
- Audit your third-party cookie usage.
- Test for breakage.
- Migrate to privacy preserving solutions:
- For cross-site cookies which store data on a per site basis, like an embed, consider
Partitionedwith CHIPS. - For cross-site cookies that would otherwise be restricted by browser settings, consider prompting users with request for storage access permissions with Storage Access API.
- For cross-site cookies across a small group of meaningfully linked sites, consider Related Website Sets.
The Privacy Sandbox provides a range of purpose-built APIs for specific use cases without a need for third-party cookies:
- Federated Credential Management (FedCM) enables federated identity services allowing users to sign in to sites and services.
- Private State Tokens enable anti-fraud and anti-spam by exchanging limited, non-identifying information across sites.
- Topics enables interest-based advertising and content personalization.
- Protected Audience enables remarketing and custom audiences.
- Attribution Reporting enables measurement of ad impressions and conversions.
If you still have third-party cookie use cases that are not covered by these options, you should report the issue to us and consider if there are alternative implementations that don't depend on features that can enable cross-site tracking.
Preserve critical user experiences
Cross-site cookies have been a critical part of the web for over a quarter of a century. This makes any change, especially a breaking change, a complex process that requires a coordinated and incremental approach. While the additional cookie attributes and new privacy-focused APIs account for the majority of use cases, there are specific scenarios where we want to ensure we don't break the experience for people using those sites.
Explore these temporary options, such as third-party deprecation trial and enterprise controls, while you continue making the necessary changes to migrate away from unrestricted third-party cookies.
Read more about the options offered in Preserving critical user experiences.
Report issues with third-party cookies and get help
We want to ensure we capture the various scenarios where sites break without third-party cookies to ensure that we have provided guidance, tooling, and browser features to allow sites to migrate away from their third-party cookie dependencies. If your site or a service you depend on is breaking with third-party cookies disabled, you can submit it to our breakage tracker at goo.gle/report-3pc-broken.
If you have questions about third-party cookies, you can raise a new issue using the "third-party-cookies" tag in our developer support repository.