Stay organized with collections Save and categorize content based on your preferences.
Note: See updated guidance for the Relevance and measurement unified origin trial.The Privacy Sandbox includes a selection of proposals to enable advertising use cases without the need for cross-site tracking. Origin trials provide the opportunity for developers to evaluate and provide feedback on new web technologies through real-world testing. In previous origin trials sites have been able to test against individual APIs. For the Topics, FLEDGE and Attribution Reporting APIs we are providing a single origin trial that allows sites to run unified experiments across the APIs making up an initial version of the end-to-end ad lifecycle. The APIs are available for testing in Chrome 101 Beta and above. The Chrome 101 Beta release also sees updates to the user controls as we continue to iterate on configuration options.
As a developer you will be able to sign up for this single origin trial that will allow you to test across the Topics, FLEDGE, and Attribution Reporting APIs. This guide takes you through the configuration steps to access the APIs, explains how to validate your configuration, and provides further resources for testing against the APIs.
What's in the origin trial?The aim of this origin trial is to allow for meaningful testing across the ad lifecycle over multiple sites. To cover this journey, the origin trial includes:
document.browsingTopics().While this setup allows for unified testing across all these APIs, you can pick and choose which aspects to implement—as much or as little as fits your needs.
How do developers sign up for the origin trial?Register for the Privacy Sandbox Relevance and Measurement trial. With the following HTML tags, provide a trial token on every page that you would like to run API code:
<meta> tag in the top-level page's <head> section: <meta http-equiv="origin-trial" content="TOKEN_GOES_HERE">Origin-Trial: TOKEN_GOES_HERESome functionality available in the origin trial is intended for use in cross-site contexts, as in when you are providing a service as a third-party on the top-level site. If you need to enable your origin trial for these additional contexts, ensure that you select the option for "Third-party matching". To enable the origin trial from third-party JavaScript, inject the <meta> tag into the top-level page (i.e. the first-party page, not your own content) from your script. For example:
const otMeta = document.createElement('meta');
otMeta.setAttribute('http-equiv', 'origin-trial');
otMeta.setAttribute('content', 'TOKEN_GOES_HERE');
document.querySelector('head').appendChild(otMeta);
Learn more in the guide to getting started with Chrome's origin trials.
Caution: An iframe accessing a trial feature (such as FLEDGE'sjoinAdInterestGroup()) must provide a token that matches its origin. How do developers test locally?
The individual developer documentation for Topics, FLEDGE, and Attribution Reporting provide specific guidance on local developer testing for each API. The APIs are not on by default and must be enabled with flags for testing.
To enable APIs for testing, you must:
chrome://flags/#privacy-sandbox-ads-apis flag.
--enable-features=BrowsingTopics,InterestGroupStorage,AllowURNsInIframes,PrivacySandboxAdsAPIs. * Individual APIs may have more additional flags for more fine-grained configuration, check the individual guides for details.chrome://settings/adPrivacy.chrome://settings/cookies.Troubleshooting Chrome's origin trials provides a detailed checklist to validate your configuration of the origin trial.
DevTools shows the status for an origin trial in the Applications tab under Frames.
While the origin trial will only show as active to eligible users as detailed below, you can also use the developer flags to test against your own production site.
What users are eligible for the origin trial?By design, origin trials are intended to only run on a small portion of overall Chrome traffic and as such you should always assume that even when you have enabled the origin trial on your site, the user may not have the API active. The active experiment group in the origin trial will start with a low proportion of users and likely ramp up as the trial progresses. Be aware that the percentage of Chrome users in the experiment may not match the percentage of enabled users on your site.
However, to allow for unified testing across sites, that set of eligible users should remain mostly consistent. For example, if a user is eligible for the origin trial when they view an ad on a participating publisher site, that same user should still be eligible when they convert on a participating advertiser site.
For a user to be eligible, they must:
chrome://settings/adPrivacy.chrome://settings/cookies.As with any web platform feature, you should detect support for the feature before using it.
TopicsCheck for the browsingTopics() function in the document and the Permissions Policy](https://developer.chrome.com/articles/permissions-policy/#featurepolicyallowsfeaturefeature) for "browsing-topics".
if ('browsingTopics' in document && document.featurePolicy.allowsFeature('browsing-topics')) {
// Topics enabled
}
If you want to join an ad interest group, check for the joinAdInterestGroup function in navigator and the Permissions Policy for "join-ad-interest-group".
if ('joinAdInterestGroup' in navigator && document.featurePolicy.allowsFeature('join-ad-interest-group')) {
// FLEDGE interest group enabled
}
If you want to run an auction, check for the runAdAuctionfunction in navigator, and the permissions policy for "run-ad-auction".
if ('runAdAuction' in navigator && document.featurePolicy.allowsFeature('run-ad-auction')) {
// FLEDGE auction enabled
}
Check for the attributionReporting object in the window and the Permissions Policy for "attribution-reporting".
if (document.featurePolicy.allowsFeature('attribution-reporting')) {
// Attribution Reporting API enabled
}
The feedback overview page details the various routes for giving feedback on different aspects of the Privacy Sandbox. There are specific sections for Topics, FLEDGE, and Attribution Reporting which provide the individual links for each API.
We also provide regular updates on the Progress in the Privacy Sandbox series which provides a summary of important news.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2022-03-31 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2022-03-31 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3