Temporary third-party cookie access using heuristics based exceptions.

During the third-party cookie deprecation testing period, it is important for sites and services to prepare for third-party cookie restrictions, including moving to more private alternatives. Subject to addressing any remaining competition concerns of the UK's Competition and Markets Authority, Chrome will ramp up third-party cookie restrictions to 100% of users from early 2025.

To help developers with the transition, throughout this period Chrome also uses heuristics that grant temporary access to third-party cookies, for predefined flows, in order to mitigate breakage. In specific scenarios the access is granted automatically without incremental work from developers, but this is a temporary measure, with the expectation that the heuristics will be removed completely in the future and developers are expected to migrate to long term solutions.

Caution: Heuristics based exceptions only grant temporary access in limited scenarios and shouldn't be relied upon for current or new web development. Chrome will monitor their use over the course of the third-party deprecation process and they will be removed in a future Chrome version, when there is a large reduction in breakage from the exception scenarios handled by the heuristics over a sustained period of time. Developers should migrate to long term solutions instead. An important first step is to audit third party cookie usage and test for breakage.

Heuristics based exception scenarios

The scenarios that heuristics intend to identify are primarily authentication where a top-level site either opens a pop-up window or redirects to a third-party site for an operation and then returns to the top-level site, making use of a cookie either on that return journey or in the embedded context.

The following examples describe scenarios in which the browser would automatically grant third-party cookie access based on certain confidence signals. These confidence signals are largely pattern-based and rely on user interaction requirements.

Scenario A - Third party cookie access after pop-up interaction

• The user navigates to Site A
• The user loads a resource on Site B in a pop-up window with opener access, possibly following a set of HTTP redirects*.
• The resource on Site B receives a user interaction after being loaded.

For 30 days after this flow, Site B is allowed third-party cookie access when embedded on Site A.

Note: If there is a set of HTTP redirects in the pop-up window, user interaction in the pop-up will be required after the redirects, to ensure the user is interacting with the third party that will be granted third-party cookie access.

Scenario B - Third party cookie access after interaction across redirects

• User begins on Site A, and is then redirected to Site B.
• Site B receives a user interaction.
• Site B then redirects back to Site A (possibly through other origins).

For 15 minutes after this flow, Site B is allowed third-party cookie access when embedded on Site A.

Note: The temporary access is limited to 30 days in scenario A, which permits scenarios with access that persists across users sessions (e.g persistent authentication token). The grant for scenario B persists for 15 minutes, it is short-term access that should only last for the current user session. This behavior matches the temporary compatibility measures that are also shipping in the Firefox and Safari browsers.

The cookie access grant applies only to the pair of first-party site and third-party site. For example, if a scenario is met with first-party-site a.com and third-party site b.com, then any page on b.com is allowed to access cookies when loaded as a resource or iframe on any page on a.com. This grant does not apply to other third-party sites under a.com, b.com as a third-party resource of another top-level domain, or b.com when indirectly embedded on a.com with other cross-site (i.e. not a.com or b.com) iframes in the intermediate ancestor chain . Additionally, cookie access shouldn't be granted to resources of b.com embedded by other iframes which are cross-site to b.com.

For more detailed information about the heuristics you can read the corresponding explainer.

The heuristics-based exceptions demo lets you test third-party cookie access with and without heuristics exceptions.

Note: Heuristics based exceptions are a temporary measure, if your website has a sign-in flow that relies on third-party cookies check the impact of the third-party cookie phaseout on your sign-in workflows, a guide to migrate to the privacy preserving alternatives for your sign in flows.