I believe that was the end of the experiment.
thanks,
Mike
On 1/29/26 11:57 a.m., Garrett Johnson wrote:
Was this extended beyond Chrome 141, or was that the end of the
experimental labels?
Thanks.
Sincerely,
Garrett Johnson
Associate Professor
Questrom School of Business
Boston University
https://garjoh.com
On Tuesday, 22 July 2025 at 11:33:02 UTC-4 Nan Lin wrote:
Contact emails
[email protected], [email protected]
Explainer
https://github.com/privacysandbox/tpcd-labeling/blob/main/cookie_deprecation_labeling_explainer.md
<https://github.com/privacysandbox/tpcd-labeling/blob/main/cookie_deprecation_labeling_explainer.md>
https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing
<https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing>
Summary
The cookie deprecation labels are useful for developers to
evaluate and optimize deployments of the Privacy Sandbox APIs, and
we want to avoid disruption while we engage with the industry to
gather feedback on an updated roadmap for these technologies.
Therefore we are asking to extend the current set of labels
<https://developers.google.com/privacy-sandbox/relevance/setup/web/chrome-facilitated-testing>for
three more milestones.
Link to “Intent to Experiment” blink-dev discussion
https://groups.google.com/a/chromium.org/g/blink-dev/c/NJrU4AQ5m_I/m/l-SaSj9MEQAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/NJrU4AQ5m_I/m/l-SaSj9MEQAJ>
Goals for experimentation
Continued deployment and evaluation of Privacy Sandbox Ads APIs.
Experimental timeline
This feature was previously approved to run up until Chrome 138.
We would like to extend this for Chrome 139 through 141, inclusive.
Any risks when the experiment finishes?
Minimal, the cookie deprecation labels are only available for a
subset of users and must be requested. Embedded services that will
need to detect third-party cookie availability in Chrome
<https://privacysandbox.google.com/cookies/prepare/detect>after
the experiment ends can utilize Storage Access Headers
<https://github.com/privacycg/storage-access-headers>instead of
relying on these labels.
As new clients are ineligible for the experiment, the percentage
of clients that receive the labels will decay over time, and
eventually the experiment will effectively expire naturally.
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, and we want to avoid
disruption while we engage with the industry to gather feedback on
an updated roadmap for these technologies.
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
<https://chromestatus.com/feature/5189079788683264>
--
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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e0d0b7c3-21bb-457e-a461-31e26caa19d9n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e0d0b7c3-21bb-457e-a461-31e26caa19d9n%40chromium.org?utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/596a3842-2396-4333-90c5-7b118b2fdf8a%40chromium.org.
