![]() Alternatively, to prevent breakage, you can set the CookiesAllowedForUrls policy to allowlist your enterprise applications to continue receiving third-party cookies.įor enterprise end users that are pulled into this experiment group and that are not covered by either enterprise admin policy, they can use the User Bypass control (the “eye icon” in the omnibox) to temporarily re-enable third-party cookies for 90 days on a given site when necessary. Admins can set the BlockThirdPart圜ookies policy to false to re-enable third-party cookies for all sites but this will prevent users from changing the corresponding setting in Chrome. We plan to provide more tooling (such as the Legacy Tech Report) to help identify third-party cookies use cases. This will give enterprises time to make the changes required to not rely on this policy or third-party cookies. Most enterprise users should be excluded from this experiment group automatically however, we recommend that admins proactively use the BlockThirdPart圜ookies and CookiesAllowedForUrls policies to re-enable third-party cookies and opt out their managed browsers ahead of the experiment. As bounce-tracking protections are also a part of 3PCD, the users in this group with third-party cookies blocked will have bounce tracking mitigations take effect, so that their state is cleared for sites that get classified as a bounce tracker. The facilitated testing period allows sites to meaningfully preview what it's like to operate in a world without third-party cookies. In Chrome 120 and beyond (Jan 2024), Chrome will globally disable third-party cookies for 1% of Chrome traffic as part of our Chrome-facilitated testing in collaboration with the CMA.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |