Increasing the Privacy Sandbox Relevance and Measurement origin trial to 5%

This week, no sooner than October 26, we'll begin increasing the Privacy Sandbox Relevance and Measurement origin trial population towards 5% of Chrome Stable users.

This week, no sooner than October 26, we will begin increasing the Privacy Sandbox Relevance and Measurement origin trial population towards 5% of Chrome Stable users. We always take an incremental approach to increasing limits and actively monitor for issues in Chrome origin trials–you can expect to see traffic levels increase over a period of a few days. Pre-stable channels, Canary and Beta will continue as is with a 50/50 split for origin trial eligibility.

We brought the trial to Chrome Stable in August to enable functional testing in a real, production environment—and the results helped us improve API stability, developer documentation, and support. We are increasing the scale of this testing to 5% to continue functional testing through 2022 and prepare for utility testing in 2023.

Through all of this, your feedback is critical. This feedback can come in the form of discussion on the proposals, reporting implementation issues, and—most importantly as we open up this wider scale—sharing the results of your testing with the rest of the ecosystem.

Control your participation in the origin trial

Learn how you can participate in the Privacy Sandbox Relevance and Measurement origin trial on our dedicated origin trial documentation.

The mechanics of the origin trial remain the same: you obtain origin trial tokens for the contexts where you want to experiment with the APIs. With the expanded testing population, you should ensure that you are actively monitoring and controlling the level of traffic where you choose to enable the trial.

A good approach here is to:

  1. Include the origin trial tokens by default in all contexts where you wish to experiment.
  2. Use feature detection to check for active APIs.
  3. If the APIs are active (and therefore, the browser is eligible for this experiment), choose whether or not to use them based on your own experiment criteria. For example, if you already have A/B testing infrastructure to experiment on a percentage of traffic, sampling, or some other attribute, then at this point you can decide which features you will actively use.

You can prevent participation in the origin trial entirely for any browser instance by not including the token in the response. For instance, if you have met your own quota for an experiment or need to address an issue during the trial, then not including the token ensures no experimental functionality will be available or active in the page.

Renew your token

Origin trial tokens expire six weeks from their issue date (or at the end of the trial if that's sooner).

It's critical that you renew and deploy your new tokens within that window for uninterrupted use of the origin trial features.

Renewing tokens only takes a few minutes, and you can deploy multiple tokens for the same trial within the same page. You can deploy a renewed token before your existing token expires, so there's no break in service for users.

Origin trial APIs and features

Increasing the testing population means finding the balance between getting early features for you to test while maintaining a stable experience for Chrome users. While we are increasing the overall population for the origin trial to 5% of Chrome Stable users, the individual API features within the trial will each progress through early channels for stability testing before we graduate them into the Beta or Stable origin trial.

Some features may only graduate to later channels if they are being used—this means early testing on Canary and Beta, either via the origin trial or with the feature flag, is critical for us to progress those features to Stable. In your testing, you should continue to actively use feature detection per API and expect to see variation in that functionality over time and over different Chrome versions.

As individual features progress, you'll be notified on the developer mailing lists for the relevant APIs (Attribution Reporting, FLEDGE, Topics, and Shared Storage). We'll continue to update the developer documentation with a summary of active functionality.

Attribution Reporting, Topics, FLEDGE, and Fenced Frames are all currently available in Chrome Stable and will be part of the increased traffic. We will start increasing traffic for Attribution Reporting and Topics from this week, no sooner than October 26. FLEDGE and Fenced Frames will increase from November 9th.

API Origin trial status
Attribution Reporting Available in Stable, increasing to 5% after October 26th.
Topics Available in Stable, increasing to 5% after October 26th.
FLEDGE Available in Stable, increasing to 5% from November 9th.
Fenced Frames Available in Stable, increasing to 5% from November 9th.
Shared Storage Only available in M105+ Canary, Dev, and Beta for now.

This is an important milestone in our overall progress to launching these APIs for general availability and phasing out third-party cookies. If you were waiting for a more complete set of functionality for your own testing—then now is the time to get involved!

Future Testing

As we conclude functional testing in 2022 to ensure all the APIs work as expected, we expect developers to invest in utility testing. In the coming months, we will publish more detailed utility testing guidance to help prepare developers to get the best results possible for specific advertiser types and their use cases.

As always, we want to hear your feedback and make the path to participation as easy as possible. You can reach out to us via our feedback form, @ChromiumDev on Twitter, our developer support repo on GitHub, or any of the other channels we have open for feedback.