Privacy Sandbox demos
Demos and colabs walk you through the Privacy Sandbox APIs.
Published on • Updated on
There are a number of demos available for the Privacy Sandbox APIs. Most of them will require you to be familiar with the APIs, so if you haven't read the docs, check out the links we've listed along with the demos.
Demos and colabs
Protected Audience API
Protected Audience API
Topics API
Topics API
Demo
The Topics API allows a browser to share information about a user's interests with third parties without the use of third-party cookies. It enables interest-based advertising (IBA) without tracking the sites a user visits. This demo shows an example of the API in action.
Colab
This colab makes it easy to load the TensorFlow Lite model used by Chrome to infer topics from hostnames.
Attribution Reporting
Attribution Reporting
Demo
The Attribution Reporting API enables advertisers and ad tech providers to measure conversions for ad clicks and views, ads in a third-party iframe, and ads in a first-party context. In this demo an advertiser uses an ad tech provider to run their ads on a publisher site.
Noiselab
Shared Storage
Shared Storage
CHIPS
CHIPS
First-party Sets
First-party Sets
First-Party Sets (FPS) is a way for a company to declare relationships among sites, so that browsers allow limited third-party cookie access for specific purposes. Chrome will use these declared relationships to decide when to allow or deny a site access to their cookies when in a third-party context.
Permissions Policy
Permissions Policy
User Agent Reduction
User Agent Reduction
User-Agent reduction minimizes the identifying information shared in the User-Agent string, which may be used for passive fingerprinting. Resource requests have a reduced User-Agent header now and the return values from certain Navigator interfaces are reduced. This demo lets you experiment with the new UA string values.
Private State Token API
Private State Token API
With the Private State Token API, a website can issue cryptographic tokens to a user it trusts, which can later be used elsewhere. The tokens are stored securely by the user's browser, and can then be redeemed in other contexts to confirm the user's authenticity. Check out the API in this demo.
Updated on • Improve article