Intent to Extend Experiment: Cookie Deprecation Label

367 views
Skip to first unread message

John Delaney

unread,
Sep 30, 2024, 10:12:19 AMSep 30
to blink-dev

Contact emails

john...@chromium.org, wande...@chromium.org, lin...@chromium.org


Explainer

https://github.com/privacysandbox/tpcd-labeling/blob/main/cookie_deprecation_labeling_explainer.md

https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing


Summary

As noted on the I2D&R for Third Party Cookies:

We recently announced a new path focused on elevating user choice, instead of third-party cookie deprecation. We will continue to support and invest in the Privacy Sandbox technologies. While we can't predict what exact user preferences will be, it’s important for businesses and developers to prepare for a likely increase in Chrome browsers without support for third-party cookies, and to continue investing in privacy-enhancing technologies.


The cookie deprecation labels are useful for developers to evaluate and optimize deployments of the Privacy Sandbox APIs prior to any changes in the number of browsers which support third-party cookies, so we are asking to extend the current set of labels for three more milestones.


Link to “Intent to Experiment” blink-dev discussion

https://groups.google.com/a/chromium.org/g/blink-dev/c/3escBQGtIpM/m/ntcytva5BgAJ

https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/v3PiIzm1M-Y

 

Goals for experimentation

Continued deployment and evaluation of Privacy Sandbox Ads APIs.


Experimental timeline

This feature was previously approved to run up until Chrome 129.


We would like to extend this for Chrome 130 through 132. 


Any risks when the experiment finishes?

Minimal, the cookie deprecation labels are only available for a subset of users and must be requested. 


Reason this experiment is being extended

We have received feedback that these labels are useful for ad tech companies to evaluate and optimize the APIs in preparation for changes to third party cookie availability.


Ongoing technical constraints

None


Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?

No, not supported on webview.


Link to entry on the feature dashboard

https://chromestatus.com/feature/5189079788683264



Mike Taylor

unread,
Sep 30, 2024, 6:03:50 PMSep 30
to John Delaney, blink-dev

Hey John,

Can you confirm these labels will only be sent to the 1% "Mode B" population, until the new user choice approach is shipped? Or is something else planned?

thx,
Mike

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/694264ea-eb98-41a8-a798-62d28f7715c5n%40chromium.org.

John Delaney

unread,
Oct 1, 2024, 11:50:10 AMOct 1
to Mike Taylor, blink-dev
Hey Mike,

We also plan to continue sending labels for the "label_only" groups as well, overall this <8.5% of browsers (these labels are also subject to a number of eligibility requirements). 

Currently we plan to continue extending this until the new approach is shipped, but we will provide any updates on future I2EEs.

Mike Taylor

unread,
Oct 4, 2024, 4:10:23 PMOct 4
to John Delaney, blink-dev

OK - thanks John. LGTM to extend until 132 inclusive.

Reply all
Reply to author
Forward
0 new messages