Intent to Extend Experiment: Cookie Deprecation Label
John Delaney
We would like to extend the Cookie Deprecation Label experimental feature being used for Chrome Facilitated Testing. This feature previously received approval to run through the end of M125 (ending roughly June 10, 2024). The Facilitated Testing period, however, is scheduled to run through June 30, 2024.
Therefore, we would like to extend Cookie Deprecation Labels for another milestone through M126.
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
To prepare for the third-party cookie deprecation, it is important to understand the full impact of Chrome’s planned transition from third-party cookies to the Privacy Sandbox Ads APIs.
This experiment exposes a temporary set of APIs which provide access to browser-determined treatment and control groups to support opt-in server side testing of the third-party cookie deprecation.
We are exploring ways to address ecosystem feedback that we should continue supporting labels after 30 June. We expect to provide more information soon.
Link to “Intent to Experiment” blink-dev discussion
https://groups.google.com/a/chromium.org/g/blink-dev/c/3escBQGtIpM/m/ntcytva5BgAJ
Goals for experimentation
The goal of this experiment is to allow adtechs to evaluate the impact of third party cookie phase out through opt-in server side testing. We expect partners to run experiments downstream from the browser provided treatment and control groups.
Experimental timeline
Previously the feature was approved until M125. We'd like to extend the experiment by one milestone to M126 so that we can continue to support the Chrome Facilitated Testing period until June 30, 2024. Any experimentation after June 30 will be covered by another Intent.
Any risks when the experiment finishes?
Minimal. The feature is designed in a way that websites must feature detect for the web API. This feature is also only available for a subset of users.
Reason this experiment is being extended
This feature is necessary to support the ongoing Chrome Facilitated Testing effort. The Facilitated Testing period is scheduled to complete on June 30, 2024 which is slightly beyond our previous approval for the feature. Therefore we are requesting to extend the experimental feature access to M126.
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
LGTM to extend one more milestone (M126).
--
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/cc8339ee-9996-43cf-b3ec-451f01f9e64cn%40chromium.org.
John Delaney
Mike Taylor
I will claim that it doesn't, since it's just for 1 more milestone.
(if other API OWNERS disagree, now is a great time to chime in!)
Daniel Bratell
I agree. One lgtm is enough for this, but thanks to John for raising it.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5fdea5ce-fabf-48b2-9c33-2e629999d392%40chromium.org.