Google has started testing the phasing out of third-party cookies on Chrome, affecting about 1% of its users or approximately 30 million people. Learn how to check if you are part of the initial test.
Third-party cookies, which track users' browsing habits across different websites for targeted advertising, are slowly being replaced by Google's Privacy Sandbox APIs. This new method aims to allow personalized ads based on users' interests without compromising their privacy.
Firefox and Safari have already eliminated default access to these cookies, with Google expecting to follow suit by adopting a more secure method. The tech giant is aiming for interoperability across different browsers while maintaining high privacy and security standards.
The shift away from third-party cookies marks a significant change in online advertising, requiring advertisers to adapt to new privacy-preserving technologies. Google is actively working with web developers to create solutions that protect user privacy while ensuring the web remains dynamic and accessible.
Based on the test results and whether it causes significant issues with the displaying of websites, Google will begin to gradually phase out third-party cookies for the rest of its users starting in the third quarter of 2024.
How to identify if you're in the one percent bracket
Google Chrome users who are added to the third-party cookie deprecation tests will not be notified. However, Google has shared information in a support document on how to check if you are part of the test.
You can use one of the following four methods to check if you are part of the 'Third-party cookies restricted by default' test:
1. Look for the "Eye" Icon in the Address Bar
When you visit a website that tries to access third-party cookies, Chrome will display an "eye" icon in the address bar.
This icon indicates that the site is attempting to use third-party cookies and that Chrome is restricting this access as part of its new Tracking Protection feature.
2. Tracking Protection Dialog
By clicking on the "eye" icon, you'll open a dialog that provides more information about Tracking Protection.
This feature limits cross-site tracking by blocking third-party cookies by default. If you wish, you can temporarily allow third-party cookies for the site you're currently on by toggling the permission in this dialog, which will be granted for 90 days.
3. Chrome DevTools Alerts
For users not included in the 1% or those who haven’t manually blocked third-party cookies via Chrome settings, Chrome DevTools will display warnings about potential cross-site cookie issues.
However, for those within the 1% testing group, DevTools will show errors indicating that reading and setting third-party cookies have been blocked.
4. Settings Changes
Users in the 1% group will find that their Chrome settings have been updated to include a new chrome://settings/trackingProtection page, replacing the previous chrome://settings/cookies panel.
This new Tracking Protection settings panel signifies that your browser is part of the group with restricted third-party cookie access.
These indicators will help you understand whether your Chrome browser is part of Google's initial testing phase for phasing out third-party cookies.
If you are not part of the test but want to join it manually, you can enable tracking protection by going to chrome://flags in the address bar and turning on an experimental flag titled "Test Third Party Cookie Phaseout." When prompted, relaunch the browser for the setting to go into effect.
Comments
d0x360 - 4 months ago
I am and of course I get into something I don't care about because I use Adguard on android and pc and it handles 3rd party cookies for me and has for the last 13 years... Sigh
h_b_s - 4 months ago
I will never understand why people complain because a feature that used to be part of very widely used plug ins is now standard on the program (but actually never required a plug in). Especially in this case, where 3rd party cookies never should have even been allowed in the first place.
It's been an *option* to disallow 3rd party cookies in pretty much ALL browsers since the beginning. Just that Google is using its monopoly position to now enforce what shouldn't have been allowed anyway. It's a *rare* case where leveraging monopoly position is a good thing for end users, yet you get nonsensical complaints like the above.
U_Swimf - 4 months ago
This is bull.. The only third party whose stuff is ever gonna be blocked with be the user who is using the browser and their wishes.
To the guy who said it's been an option since the begining, i challenge anyone to actually count cookies on each site they visit by checking 3 times each visit to any given website.
Once with All cookies disabled, count the total blocked. Then, reload the page after changing to block only third party, count how many are blocked and how many allowed. Lastly, enable all cookies or whatever other options you may have, then count.. You'll find the numbers don't usually equal what they should.. E.g. If i block ALL cookies (back when that was a "preference" and an "option") one might see 50 cookies blocked, but then have different total numbers when counting for any other circumstance. Clear cache if you want or try removing/deleting them to start with a clean pallete each time but good luck with that..
Know what Chrome has been doing in my browser? Saving my preferences and settings as a third Party Cookie. If i disable third party cookies or rather ALL cookies, i lose any prefernces and presumably preferences i have set. Theme, probably permissions, and it used to be logins and SSO but that specific one recently changed for me too. Now i am forced to stay logged in always without an option other than using a "Guest" profile, which is unmanagable from my "Admin" roll. Might as well not bother then.