Privacy Sandbox

Naming, expiry, and other considerations when transitioning to partitioned cookies.

Here's where to start, including setup and a quick overview.

• Web
• Mobile
• Attribution Reporting API
• Guide

Get started with Private advertising Get started on building your ads solution with the Privacy Sandbox, and enabling your critical advertising use cases without relying on cross-site tracking. Learn, build, and provide feedback on the Privacy

Topics API Improve ad relevance without compromising user privacy. Get started on building your ad solution with the Topics API, a mechanism designed to allow for interest-based advertising. With Topics, the specific sites a user has visited are not

• Topics API
• Landing page

Privacy-focused APIs and updates for cookies, advertising, identity, personalization, and fraud prevention.

• Product

Third-party cookies Understand cookie usage on your site. Learn how to transition to alternatives. Prepare for Chrome changes Learn more about changes to Chrome's treatment of third-party cookies and understand what actions you need to take to

Publishers typically diversify their ad demand sources to optimize for revenue and invoke multiple companies (for example, publisher ad servers, supply-side platforms, and demand-side platforms) to determine the best ad for a given ad slot on the

To help developers start experimenting with the Protected App Signals API, this document describes all the APIs within the API surface, details how to set up a test environment, and provides examples of the configuration and scripts. First release of

• Mobile
• Protected App Signals API
• Guide

Private Aggregation To provide critical features that the web relies on, the Private Aggregation API has been built for aggregating and reporting on cross-site data in a privacy-preserving manner. With Private Aggregation, generate aggregate data

• Private Aggregation API
• Landing page

Updated the list of upcoming changes and known issues Introduced lite flexible event-level configuration, as a bridge to the full flexible event-level configuration Starting in September 2023, registerWebSource, registerWebTrigger, registerAppSource

• Mobile
• Attribution Reporting API
• Landing page

"Simple demos to help you understand HTTP cookies."

Leading ecommerce CMS provider Tray provides insights into how they implemented partitioned cookies (CHIPS) and the Storage Access API across their services.

In this section, you can find different resources such as demos, videos, training material, and information on events related to Privacy Sandbox. Learn about the different Private advertising APIs to build your advertising use cases. Glossary Learn

"Understand HTTP cookies."

As you read through the Privacy Sandbox on Android documentation, use the Developer Preview or Beta button to select the program version that you're working with, as instructions may vary. The Attribution Reporting API is designed to provide improved

• Mobile
• Attribution Reporting API
• Guide

Measure when an ad click or view leads to a conversion, such as a purchase on an advertiser site.

• Web
• Attribution Reporting API
• Landing page

How to measure when an ad click or view leads to a purchase or other events

• Attribution Reporting API
• Pathway

"Understand HTTP cookie attributes."

"The web uses the HTTP protocol to transfer resources and set cookies. How does that work?"

"A third-party cookie is from a site that's different from the site you're visiting. What does that mean in practice?"

"Cookies may be blocked by browser design, user settings, developer flags, or enterprise policy."

Want to ensure a smooth payment experience for every user, whether or not third-party cookies are available? Learn how to identify and address third-party cookie dependencies, and transition to alternative APIs to support payment flows even where cookies are restricted.

• Web
• Guide

Understand how to test common workflows that may rely on third-party cookies and decide on which privacy-preserving alternatives to migrate to. person Identity guide Find recommended solutions for sign-in scenarios likely to be affected by

Introducing a new FedCM UI for displaying filtered out accounts in Chrome 133.

• Web
• Federated Credential Management API

Quarterly report for 2024 Q4 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

To access the Privacy Sandbox relevance and measurement APIs on Chrome and Android, developers need to enroll with the Privacy Sandbox. This includes Attribution Reporting, Protected Audience, Topics, Private Aggregation, and Shared

• Web
• Mobile
• Landing page

Get ready for third-party cookie changes. Learn how to test your sign-in workflows and make the necessary changes to prepare.

• Web
• Guide

Summary reports are a powerful tool for examining your data from Attribution Reporting and Private Aggregation. This pathway will take you through the key concepts and tooling needed to enable you to build effective reports.

• Attribution Reporting API
• Private Aggregation API
• Pathway

Federated Credential Management API Enable a streamlined, one-tap browser-mediated identity federation flow and an intuitive UI with the FedCM API. Support more users, even those who say 'no' to third-party cookies. Understand how FedCM can improve

• Federated Credential Management API
• Landing page

Where and how to provide feedback for Privacy Sandbox proposals throughout the development process.

A web platform API that allows users to login to websites with their federated accounts in a manner compatible with improvements to browser privacy.

• Web
• Federated Credential Management API
• Landing page

Explore FedCM (Federated Credential Management) and its role in privacy-first federated identity. Learn how to implement FedCM on the Relying Party side.

• Web
• Federated Credential Management API

Chrome 133 introduces support for Storage Access HTTP headers

• Web
• Storage Access API
• Blog

Explore FedCM (Federated Credential Management) and its role in privacy-first federated identity. This guide covers implementing FedCM as an identity provider, including key concepts and practical examples.

• Web
• Federated Credential Management API

Cookie basics Guides, demos and tools to help you understand how cookies work. What are cookies? Understand HTTP cookies: how they're set by a web server, then stored and sent by a web browser. Third-party cookies A third-party cookie is from a site

• Landing page

Deploy and manage Aggregation Service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

In the past, third-party cookies have been used to store and convey information about a user's state, such as their sign-in status, information about the device they are using, or whether they are known and trusted. For example, whether the user has

"Chrome tools to help you understand cookie usage on your site."

Overview of how users can manage and customize the Federated Credential Management API.

• Web
• Federated Credential Management API

For sites that need time to adjust to third-party partitioning of storage, service workers, and communication APIs, the deprecation trial has been extended once more to allow them to temporarily keep their third-party storage, service workers, and communication APIs unpartitioned.

Follow the instructions on this page to set up the Privacy Sandbox on Android SDK in Android Studio. First, it is recommended to Install and use the latest Canary build of Android Studio. Then, within Android Studio, install the SDK and relevant

• Mobile
• Guide

This guide explains how to enable your physical Android device or emulator to perform end-to-end testing for beta features of the Privacy Sandbox on Android. Follow these instructions to opt-in your Google Account to receive beta updates of Google

• Mobile
• Guide

Chrome introduces Shared Storage updates including support for cross-origin worklet scripts and updates to the Select URL API with Shared Storage in Chrome 132 with the support of saved queries.

• Web
• Shared Storage API

There are two methods for configuring your device for testing the Protected Audience API - by using a CLI tool that Privacy Sandbox provides on GitHub, or by running a series of ADB commands. You can pull the CLI Python scripts from this GitHub

• Mobile
• Protected Audience API
• Guide

For advertisers and DSPs who are interested in buying ad space and measuring the performance of ads. Create and manage an audience and start an auction with the Protected Audience API. looks_one Set up your developer environment Enable Privacy

• Web
• Mobile
• Landing page

When you create a custom audience, you can specify some or all of the custom audience metadata. This information can be passed directly when creating a CustomAudience object. The CustomAudience.Builder also supports a dailyUpdateUri field which can

• Mobile
• Protected Audience API
• Guide

A custom audience represents a group of users with common intentions or interests as decided by an advertiser app. An app or SDK may use a custom audience to indicate a particular audience, such as someone who has left items in a shopping cart. The

• Mobile
• Protected Audience API
• Guide

An API to convey a limited amount of information from one browsing context to another (for example, across sites) to help combat fraud, without passive tracking.

Deploy and manage this service to produce summary reports for the Attribution Reporting API or Private Aggregation.

• Mobile

Bidding and Auction (B&A) Services is a set of services for ad buyers and sellers that runs in a Trusted Execution Environment (TEE) to facilitate a Protected Audience (PA) auction. This developer's guide explains how a seller can integrate with

• Web
• Protected Audience API
• Guide

Bidding and Auction (B&A) Services is a set of services for ad buyers and sellers that runs in a Trusted Execution Environment (TEE) to facilitate a Protected Audience (PA) auction. This Developer's Guide explains how a buyer can integrate with a

• Web
• Protected Audience API
• Guide

Learn the auction architecture of Bidding and Auction Services Bidding and Auction (B&A) Services provides a set of services for ad buyers and sellers that runs in a Trusted Execution Environment (TEE) to facilitate a Protected Audience (PA)

• Web
• Protected Audience API
• Guide

Chrome 132 introduces multiple FedCM updates including the Mode API for better user control and the Continuation API for flexible multi-step sign-in flows.

• Web
• Federated Credential Management API

Set up your developer environment to implement an identity solution with FedCM, a new API for privacy-preserving federated authentication.

• Web
• Federated Credential Management API

Allow unlimited, cross-site storage write access with privacy-preserving read access.

• Web
• Shared Storage API
• Landing page

Select a URL based on data collected in Shared Storage, and render the content in a fenced frame.

• Web
• Shared Storage API
• Guide

Android WebView will take the next step in reducing the information available in the User-Agent string, to improve privacy for users. With this change, websites and services that rely on the User-Agent string for certain information may need to take action. This post gives some background on what's happening, why WebView is making this change, and what you can do to prepare.

SDK Runtime Enhance user privacy, app security, and SDK integrity with a new Android 14 environment that allows third-party SDKs to run in isolation from the app process, providing stronger safeguards for user data. Architecture Learn how the SDK

• Mobile
• SDK Runtime API
• Landing page

The Android platform uses the concept of app sandboxing to maintain robust execution and security boundaries for app code, along process boundaries. It's a common practice for apps to include third-party code, often in the form of SDKs such as ads

• Mobile
• SDK Runtime API
• Landing page

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

As described in the Attribution Reporting API design proposal, the API enables attribution of the following trigger paths on a single Android-powered device: Web here is defined as web content shown in an app. Web content can be shown in the context

• Web
• Mobile
• Attribution Reporting API
• Guide

Learn how to create an audience to target your ads

• Shared Storage API
• Pathway

Learn how to create an audience to target your ads

• Protected Audience API
• Pathway

Learn the essentials for event-level conversion measurement with the Attribution Reporting API.

• Attribution Reporting API
• Pathway

Learn how to sell ad spaces with a Protected Audience auction

• Protected Audience API
• Pathway

Answers to frequently asked questions about obligations, consent, and user controls.

Mediation is a common way for sell-side ad platforms to offer yield management. In a mediation workflow, the mediation SDK ('mediator') invokes multiple ad networks ('mediatee' or 'mediatees') to obtain the best ad for a given slot. In some cases,

• Mobile
• SDK Runtime API
• Guide

Key concepts of the Private Aggregation API

• Web
• Private Aggregation API
• Guide

Measure ad conversions aggregated across users, without revealing individual data. Formerly known as aggregate reports.

• Mobile
• Web
• Attribution Reporting API
• Guide

The following steps describe how to get started with Aggregation Service deployment. To get started with Aggregation Service deployment: Complete the Privacy Sandbox Developer Enrollment process. Select one of the following API endpoints for use with

• Mobile

Test your sites with third-party cookies disabled.

• Web
• Guide

Find overviews, walkthroughs, and conceptual discussions in these Privacy Sandbox videos.

From Chrome 132, developers can participate in a Developer Trial for Partitioned Popins, a new approach to web pop-ups.

• Web
• Blog

Learn how to allow or deny a Privacy Sandbox feature usage on the page

• Web
• Guide

Chrome 131 integrates the Storage Access API with FedCM, where FedCM is used as a trust signal to automatically grant storage access.

• Web
• Storage Access API
• Federated Credential Management API
• Blog

Learn how Times Internet adopted Related Website Sets to provide a measured approach to cross-site data sharing.

As you read through the Privacy Sandbox on Android documentation, use the Developer Preview or Beta button to select the program version that you're working with, as instructions may vary. The Protected Audience API on Android (formerly known as

• Mobile
• Protected Audience API
• Guide

This proposal is subject to the Privacy Sandbox enrollment process and attestations. For further information regarding the attestations, please refer to the attestation link provided. Future updates to this proposal will describe the requirements for

• Mobile
• Protected App Signals API
• Guide

In the initial Protected Audience proposal, bidding and auction for remarketing ad demand is executed locally on device. This requirement can demand computation requirements that may be impractical to execute on devices with limited processing power,

• Mobile
• Web
• Guide

Use Protected Audience to run the end-to-end ad bidding, auction, and rendering process. Set up an ad auction on the publisher's page Learn how to configure a Protected Audience API auction. Run a browser based auction with a single seller How to run

Answers to frequently asked questions related to Privacy Sandbox relevance and measurement APIs.

This document describes how to resolve common issues when setting up the Privacy Sandbox on Android. If you see an error not found in this guide, let us know. Some errors have multiple possible reasons for being thrown. Listed below are some of the

• Mobile
• Guide

This page describes how to work with the Federated Learning APIs provided by On-Device Personalization to train a model with a federated averaging learning process and fixed Gaussian noise. Before you begin, complete the following steps on your test

As you read through the Privacy Sandbox on Android documentation, use the Developer Preview or Beta button to select the program version that you're working with, as instructions may vary. The Attribution Reporting API is designed to support key use

• Mobile
• Attribution Reporting API
• Guide

The Battlestar Galactica FTL drive is a complex and sophisticated piece of technology that allows ships to travel faster than the speed of light. It does this by folding space-time around the ship, allowing it to travel through a subspace bubble. The

Ads SDKs in the SDK Runtime are not able to access a publisher's view hierarchy. Instead, SDKs in the Runtime have their own views. The SDK cannot use the same View APIs as they use outside the SDK runtime to determine whether the ad is visible to

• Mobile
• SDK Runtime API
• Guide

For publishers and SSPs who are interested in selling ad space and measuring the performance of ads. Run an auction and score an ad with the Protected Audience API. looks_one Set up your developer environment Enable Privacy Sandbox on your test sites

• Web
• Mobile
• Landing page

Intended to be implemented in the Android Open Source Project (AOSP), this technical explainer discusses the motivation behind On-Device Personalization (ODP), the design principles that guide its development, its privacy via confidentiality model,

Learn how Latin America's leading ecommerce platform Mercado Libre made their journey to reduce reliance on third-party cookies and protect the privacy of their customers.

On-Device Personalization (ODP) is designed to protect end users' information from applications. Applications use ODP to customize their products and services for end users, but they won't be able to see the exact customizations made for the user

Learn how to update audience data by configuring an update URL for a Protected Audience API interest group.

• Web
• Protected Audience API
• Guide

How we collaborate with stakeholders to discuss, test, and adopt privacy-preserving technologies.

Learn how to control audience management by using a Permissions Policy or delegate to a third party by configuring a .well-known permissions URL.

• Web
• Protected Audience API
• Guide

Most advertisers work with several different ad networks to serve ads across publisher apps. If ad networks register their own attribution sources and triggers with the API, they'll receive self-attributed event and summary reports. However,

• Mobile
• Attribution Reporting API
• Guide

Protected Audience (formerly known as FLEDGE) on Android implementations typically involve integration between advertiser apps, publisher apps, sellers, and buyers. This guide is intended for partners who plan to manage custom audiences and run

• Mobile
• Protected Audience API
• Guide

Use Topics and Protected Audience to build and manage your ad audiences. person_add Define audience data Learn how to define an audience by creating an interest group with Protected Audience. manage_accounts Update audience data and ads Learn how to

Quarterly report for 2023 Q4 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

The Native Ads format allows the publisher to customize an ad that's shown to a user. After fetching an ad from the SDK, publishers can then change the layout and look of the ad to align better with the application's user interface: adding a color

• Mobile
• SDK Runtime API
• Guide

The SDK Runtime imposes restrictions on how SDKs can launch new activities. This poses a challenge for full screen ad formats that typically rely on starting a separate activity for enhanced control and user experience. To address this, the SDK

• Mobile
• SDK Runtime API
• Guide

Learn how to participate in an ad auction as a buyer, and make a bid.

• Web
• Protected Audience API
• Guide

Public tester list of the Privacy Sandbox on Android

Latest news, posts, and updates on Privacy Sandbox.

The SDK Runtime is a dedicated runtime environment introduced in Android 14 to enable third-party advertising SDKs to run isolated from the app. This approach provides safeguards and protections around user data collections and sharing: SDK Runtime

• Mobile
• SDK Runtime API
• Guide

This section explains the SDK Runtime architecture, how runtime-enabled SDKs are installed, backwards compatibility, and how to migrate existing SDKs to the SDK Runtime. The SDK Runtime adopts a client-server type of model. The main difference is

• Mobile
• SDK Runtime API
• Guide

Explore the core Private advertising APIs to implement advertising use cases without the need for cross-site tracking. To learn more about what you can do with Privacy Sandbox, check out the additional services, infrastructure, and APIs. Learn about

Learn how to define an audience by creating an interest group with the Protected Audience API.

• Web
• Protected Audience API
• Guide

The Privacy Sandbox on Android Beta program provides stable APIs. You can use the Beta program releases to build and test solutions for limited production testing on Android 13+ mobile devices for all APIs and Android 12+ for Attribution Reporting

• Mobile
• Guide

The Federated Compute (FC) Server is part of Federated Learning offered by On-Device Personalization (ODP). The purpose of this document is to introduce the Federated Compute Server (FC Server), its components, and the technology used. The document

Within Android Studio, install the Android SDK as follows: Follow the instructions on the sample repository to set up the Privacy Sandbox on an Android 14+ device or emulator image to allow end-to-end testing. As a reference while following this

• Mobile
• SDK Runtime API
• Guide

Guidance on the relevance and measurement APIs use cases, configuration, experiment structure, goals, and evaluation best practices for market participants.

• Web
• Guide

Chrome's third-party cookie grace period provides a way for sites experiencing breakage to request additional time to migrate away from third-party cookie dependencies. Chrome is also providing a mechanism to allow sites to opt out of the grace period for a percentage of users.

Sharing updates on the Aggregation Service coordinators, and results of an independent security assessment.

Privacy Sandbox on Android release notes

Protected Audience auctions can be analyzed (either visually or by SQL query with Perfetto. Ad techs can use profiling with Perfetto to measure the performance of Protected Audience auctions, including: Clone the Perfetto and Privacy Sandbox

• Mobile
• Protected Audience API
• Guide

To implement the Topics API, you need to set up your development environment first. to perform the following setup steps: Use the latest Android Privacy Sandbox SDK to get the most up-to-date version of the privacy-preserving APIs. Add the following

• Mobile
• Topics API
• Guide

Measure when an ad click or view leads to a purchase or other events with Attribution Reporting. Introduction to conversion measurement with Attribution Reporting Learn how to measure when an ad click or view leads to a conversion, such as a purchase

Information and resources for online and in-person events.

The SDK Runtime allows ads SDKs run in a sandboxed environment, preventing them from being able to access a publisher's view hierarchy. To display ads, the platform exposes a SandboxedSdkProvider.getView API to the SDK to obtain an ad view, and

• Mobile
• SDK Runtime API
• Guide

Protected Audience debug reporting allows ad tech developers to declare remote URLs to receive a GET request from devices when an auction is won or lost. This enables the following use cases: Event-level debug reporting is available for testing in

• Mobile
• Protected Audience API
• Guide

The Measurement Simulation Library helps you to understand the impact of your Privacy Sandbox integration by presenting historical data as if it were collected by the Attribution Reporting API. This lets you to compare your historical conversion

• Mobile
• Web
• Attribution Reporting API
• Guide

The Privacy Sandbox is a series of proposals to satisfy cross-site use cases without third-party cookies or other tracking mechanisms.

Privacy Sandbox APIs are implemented in Chromium, which is the open source browser used to make Chrome. Code for the Privacy Sandbox APIs can be accessed with Chromium Code Search. You can download Chromium, then run it with flags to allow access to

Frequency capping is an advertising practice that limits the number of ads from a given category that are shown to a user within a given time period. Frequency capping improves the end-user experience by keeping ad impressions fresh and interesting,

• Mobile
• Protected Audience API
• Guide

Check out the relevant GitHub issues for changes to privacy budget: There is no current privacy budget that applies across APIs. Additionally, we have implemented a new rate limit: one origin per source, site or enrollment, for every 24 hours (

• Mobile
• Web
• Guide

Quarterly report for 2024 Q1 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

You have to complete the following steps to build a runtime-enabled SDK: We recommend that your project is organized into the following modules: The project structure in this guide is a suggestion, you may choose a different structure for your SDK

• Mobile
• SDK Runtime API
• Guide

This document summarizes the privacy approach for On-Device Personalization (ODP) specifically in the context of differential privacy. Other privacy implications and design decisions such as data minimization are intentionally left out to keep this

Demos and colabs walk you through the Privacy Sandbox APIs.

Guidance on running a standalone test of Privacy Sandbox Attribution Reporting API.

• Mobile
• Web
• Attribution Reporting API
• Guide

Run unified experiments across Attribution Reporting, Protected Audience API,

Tools and technique to help you understand why third-party cookies are available or blocked.

Reduce or eliminate the ability of bounce tracking to recognize people across contexts.

Test the Attribution Reporting API to understand gaps in measurement results.

An API for on-device ad auctions to choose relevant ads from websites a user has previously visited, designed so it cannot be used by third parties to track user browsing behavior across sites.

• Mobile
• Protected Audience API
• Guide

This section describes how clients can interact with the declared runtime-enabled (RE) SDK APIs. In the case of this guide, we refer to your existing SDK module (or runtime-aware SDK) as the client. If you want to the runtime-enabled SDK directly

• Mobile
• SDK Runtime API
• Guide

There are a number of settings that you can activate or deactivate for devices running Privacy Sandbox on Android. Privacy Sandbox on Android allows device users to control whether the Privacy-Preserving APIs (PPAPI) and the SDK Runtime are enabled

• Mobile
• Guide

Enable Protected Audience and Topics as a publisher

• Web
• Protected Audience API
• Guide

This document proposes a new Jetpack library to help developers with migration to the SDK Runtime. It explains how the SDK Runtime will be supported for previous Android platform versions (from build to execution), and which differences or

• Mobile
• SDK Runtime API
• Guide

Progress updates for Privacy Sandbox on Android.

Protected Audience provides a series of APIs for joining and leaving custom audiences as part of the android.adservices.customaudience package. For debugging purposes there are CLI commands available for listing and viewing custom audiences. This

• Mobile
• Protected Audience API
• Guide

What's in it, what's it for, and how to get involved.

Quarterly report for 2024 Q2 and Q3 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

Learn about the different proposals to make the web and Android more private by default, without reducing functionality or user safety. Prevent covert tracking Reduce pervasive covert tracking and maintain user privacy by default. Fight spam and

The third-party cookie dependency grace period provides a way for sites and services experiencing breakage to request additional time to migrate away from third-party cookie dependencies.

The Bidding and Auction Services for Android design proposal details the execution and data flow of running auctions on Android using the Trusted Bidding and Auction server. To ensure data in transit is handled only by privacy-preserving APIs and

• Web
• Mobile
• Guide

This section explains how to set up and prepare an app to consume a runtime-enabled SDK for local testing. First, create a separate standalone project or module. In this scenario, the app does not contain the SDK code; it declares it as a Maven

• Mobile
• SDK Runtime API
• Guide

Follow the instructions below to declare API-specific permissions and configure SDK access to resources managed by the targeted API. Access to each PPAPI requires an Ad Services normal permission. In your manifest, declare the appropriate access

• Mobile
• Guide

User-Agent reduction limits passively shared browser data to reduce the volume of sensitive information which leads to fingerprinting. The reduction is now complete.

A proposal to improve user privacy by protecting their IP address from being used for tracking.

Verify identity and share configuration details for the Privacy Sandbox relevance and measurement APIs, across Chrome and Android.

Deterministic builds are required for workload attestation in the On Device Personalization (ODP) Trusted Execution Environment (TEE), publicly available on Google Cloud as Confidential Space (CS). The workload images must generate a deterministic

Overview of Privacy Sandbox on Android

New mobile app installations are commonly driven by app install ads. To maximize your ad spend ROI, it's a good idea to not show an ad to install an app on devices that already have that same app installed. In this proposal, we refer to this practice

• Mobile
• Protected Audience API
• Guide

Learn about the Topics API on Android, and the steps involved in implementing it. You can also jump straight into implementing topics. The Topics API can be used to observe and provide access to topics that appear to be of interest to the user, based

• Mobile
• Topics API
• Guide

Learn how to use interests from Topics as an input to the Protected Audience bidding and auction process.

• Web
• Topics API
• Protected Audience API
• Guide

Protected Audience is in Beta and is available for testing on public devices! With Protected Audience, you can: To get started, read the Protected Audience developer guide. Your feedback is appreciated as we continue to develop Protected Audience. We

• Mobile
• Protected Audience API
• Landing page

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

Tools to debug issues with Shared Storage. To inspect the Shared Storage worklets started from the page you are on, you can visit the "Sources" tab in the DevTools panel, and add the "Shared Storage Worklet / Script First Statement" event listener

• Web
• Shared Storage API
• Private Aggregation API
• Guide

Try out the live demo. Follow the steps in the demo instructions to enable the Privacy Sandbox APIs. Opening Chrome DevTools helps you visualize the results of different use cases. Use cases available in the demo: To view what is stored in Shared

• Web
• Private Aggregation API
• Shared Storage API
• Guide

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

• Mobile

Chrome 130 starts an origin trial for HTTP headers logic for Storage Access API.

• Web
• Storage Access API
• Blog

Chrome is providing a lookup service to show how third-party cookie availability is affected by Chrome's third-party cookie grace period, and grace period opt-out configuration.

Lookup tool to query the third-party cookie compatibility status of a site.

To prevent certain types of side-channel cross-site tracking, Chrome has partitioned storage and communications APIs in third-party contexts.

This page is a guide on how users and developers can control and customize the Topics API to suit their preferences.

• Android
• Topics API
• Guide

Learn how to test, deploy, and scale Topics API.

• Web
• Topics API
• Guide

Learn how to implement Topics API with code samples.

• Web
• Topics API
• Guide

Learn about the Topics API, a privacy-preserving alternative to third-party cookies for interest-based advertising. Understand how topics are derived, observed, and accessed by callers, and how this API enhances user privacy.

• Web
• Topics API
• Guide

This page is a guide on how users and developers can control and customize the Topics API to suit their preferences.

• Web
• Topics API
• Guide

Learn about the tools available in Chrome to view Topics API information and debug your implementation.

• Web
• Topics API
• Guide

Recommendations for debugging, troubleshooting, and support resources for Topics on the Web.

• Topics API
• Guide

Learn how to set up the environment for developing with the Topics API, including how to use Chrome flags for testing.

• Web
• Topics API
• Guide

The Topics API enables interest-based advertising (IBA) without compromising user privacy.

• Topics API
• Pathway

Learn how the Protected Audience auction can fit into the existing ad infrastructure.

• Web
• Protected Audience API
• Guide

Chrome's Topics API update lets users proactively block ad topics, giving them more control over their ad experience.

• Web

Learn how reporting IDs work in a Protected Audience auction

• Web
• Protected Audience API
• Guide

This guidance is to be published on the dev site so that ad techs can understand how to implement MTA within Shared Storage + Private Aggregation

• Web
• Shared Storage API
• Private Aggregation API
• Guide

Chrome is extending the grace period that allows sites and services demonstrating user-facing, non-ads breakage to continue to access third-party cookies.

How to perform attribution across mobile apps and web sites

• Attribution Reporting API
• Guide

Chrome 128 starts an origin trial for Multi IdP API on desktop, as well as origin trial for the Button Mode API and Continuation Bundle features for Chrome on Android.

• Web
• Federated Credential Management API

When batching aggregatable reports, it is important to optimize batching strategies so that privacy limits are not exceeded. The following are a few recommended strategies for sending batches of reports to the Aggregation Service. When collecting

• Web
• Protected Audience API
• Guide

For sites taking part in either of the third-party cookie deprecation trials, Chrome provides a grace period to temporarily re-enable third-party cookies. During the grace period, sites can access third-party cookies in Chrome, even if they haven't yet deployed trial tokens. Chrome is now providing a mechanism to allow sites to opt out of the grace period for a percentage of users.

Chrome 126 starts origin trials for the Continuation API bundle and Storage Access API auto-grant

• Web
• Federated Credential Management API

From July 1, 2024, sites and services that have registered for one of the third-party cookie deprecation trials will receive a grace period of 60 days to deploy trial tokens, starting from the date their trial registration was approved.

For sites that need time to adjust to third-party partitioning of storage, service workers, and communication APIs, the deprecation trial has been extended to allow them to temporarily keep their third-party storage, service workers, and communication APIs unpartitioned.

The Privacy Sandbox team was at Google I/O 2024 to share the latest news on third-party cookie deprecation

Chrome 125 starts an origin trial for Button Mode API and updates to CORS and SameSite.

• Web
• Federated Credential Management API

Learn how to control the pace of ad delivery by frequency

• Web
• Protected Audience API
• Guide

Use Shared Storage and Private Aggregation for demographics measurement

• Web
• Shared Storage API
• Private Aggregation API
• Guide

Use Shared Storage and Private Aggregation for unique reach measurement

• Web
• Shared Storage API
• Private Aggregation API
• Guide

Publication date: 2024-04-02 Versions To use the Coordinator Service, including related reports, features and functionality (collectively the " Coordinator Service "), you and the legal entity on whose behalf you are using the Coordinator Service (if

Use Shared Storage and Private Aggregation for K+ frequency measurement

• Web
• Private Aggregation API
• Shared Storage API
• Guide

How to run a sequential auction with Protected Audience and contextual auctions

• Web
• Protected Audience API
• Guide

How to run a render an ad after a Protected Audience auction

• Web
• Fenced Frame API
• Protected Audience API
• Guide

How to run a Protected Audience API auction with a single seller

• Web
• Protected Audience API
• Guide

Learn how to configure a Protected Audience API auction.

• Web
• Protected Audience API
• Guide

How to run a Protected Audience API auction with multiple sellers

• Web
• Protected Audience API
• Guide

Learn how to support conversion attribution measurement by allowing multiple distinct ad techs to generate and receive attribution reports for a given set of impression and click source events and conversion trigger events.

• Web
• Attribution Reporting API
• Guide

The grace period for Chrome's third-party cookie deprecation trials is being extended until June 30, 2024.

Learn more about changes to Chrome's treatment of third-party cookies and understand what actions you need to take to preserve your site's features.

Chrome 123 introduces FedCM Domain Hint API. With the Domain Hint API, developers may provide a better UX by only showing the federated login accounts from the domain that they accept.

• Web
• Federated Credential Management API

Learn how to test your embed workflows and make the necessary updates to prepare for third-party cookie changes

We're responding because we believe that it's important to listen to what IAB Tech Lab is presenting and that the ecosystem has the most up to date, accurate information.

To facilitate testing Chrome uses heuristics that grant temporary access to third-party cookies, for predefined flows, in order to mitigate breakage.

Related Website Sets (RWS) is a web platform mechanism which helps browsers to understand the relationships amongst a collection of domains. This allows browsers to make key decisions to enable certain site functions (such as whether to allow access

Register for the upcoming Private State Tokens Office Hours. Coming on the 27th February in Portuguese and 6th March in English.

Overview of the roadmap for the Federated Credential Management API.

• Web
• Federated Credential Management API

Chrome 122 introduces FedCM Disconnect API and two updates. The Disconnect API allows the browser to terminate the connection between the RP and the IdP.

• Web
• Federated Credential Management API

Join the 12th edition of Privacy Sandbox office hours dedicated to Chrome-facilitated testing, where we will provide some Privacy Sandbox tester updates and answer your questions with product and technical leads.

A checklist for measurement implementations.

• Web
• Mobile
• Attribution Reporting API
• Guide

Suggested testing framework for the Aggregated Services API.

• Web
• Mobile
• Guide

If your first-party site relies on third-party embedded services and third-party cookie deprecation has caused functionality on your website to break, you may be eligible for the deprecation trial for top-level sites.

Learn how to audit your code to look for third-party cookies and what action you can take to ensure you're all set for the end of third-party cookies.

Announcing the Privacy Sandbox Analysis Tool, a DevTools extension with specialized capabilities to help developers deal with the deprecation of third-party cookies and adoption of alternative APIs.

If your site uses third-party cookies it's time to take action as we approach their deprecation. Third-party cookies are restricted by default for 1% of users from January 4th, 2024 to facilitate testing before we plan to ramp up to 100% of users from Q3 2024.

Explore these temporary options while you continue making the necessary changes to migrate away from unrestricted third-party cookies.

Plans and timeline for gradually enabling the Privacy Sandbox relevance and measurement APIs in Chrome 115, ending the origin trial, and enrollment updates.

Policies to allow or block third-party cookies in Chrome Enterprise installations

Answers to frequently asked questions related to Privacy Sandbox testing.

The LoginStatus API enables FedCM API without third-party cookies. The Error API and Auto-Selected Flag API bring more capabilities to FedCM API.

• Web
• Federated Credential Management API

The Storage Access API allows specific cross-site access to be provided with minimal burden to the end user, while still preventing generic cross-site access as is often used for user tracking.

Allow developers to opt-in a cookie to partitioned storage, with a separate cookie jar per top-level site. Partitioned cookies can be set by a third-party service, but only read within the context of the top-level site where they were initially set.

Learn how k-anonymity check will be applied to Protected Audience

• Web
• Mobile
• Protected Audience API
• Guide

Chrome is proposing the ability for third parties to request storage or communication access (both cookie and non-cookie) through the Storage Access API.

To facilitate testing, Chrome has restricted third-party cookies by default for 1% of Chrome users. Chrome plans to ramp up third-party cookie restrictions to 100% of users from Q3 2024, subject to addressing any remaining competition concerns of the UK's Competition and Markets Authority. For an easier transition through the process, we are offering a third-party deprecation trial which allows embedded sites and services to request additional time to migrate away from third-party cookie dependencies for non-advertising use cases.

Learn how the Protected Audience auction can fit into the existing ad infrastructure.

• Web
• Protected Audience API
• Guide

Quarterly report for 2023 Q3 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

This document is a quickstart guide for using Shared Storage and Private Aggregation. You'll need an understanding of both APIs because Shared Storage stores the values and Private Aggregation creates the aggregatable reports. Target Audience: Ad

• Web
• Shared Storage API
• Private Aggregation API
• Guide

If your site uses third-party cookies, it's time to take action as we approach their deprecation. To facilitate testing, Chrome has restricted third-party cookies for 1% of users from January 4th, 2024. Chrome plans to ramp up third-party cookie restrictions to 100% of users from Q3 2024, subject to addressing any remaining competition concerns of the UK's Competition and Markets Authority. In this Cookie Countdown series, we'll guide you through the timeline and immediate actions you can take to ensure your sites are prepared.

Measure Protected Audience API auction data and results

• Web
• Protected Audience API
• Guide

Learn how your Chrome web app can pass attributions to your Android app.

• Web
• Mobile
• Attribution Reporting API
• Guide

Related Website Sets (RWS) is the new name for First-Party Sets. It also brings increased flexibility in defining sets.

Quarterly report for 2023 Q2 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

Chrome 116 ships new FedCM capabilities such as Login Hint API, User Info API, and RP Context API, and starts an origin trial for IdP Sign-In Status API.

• Web
• Federated Credential Management API

Set up Chrome to simulate browsing without third-party cookies.

Privacy Sandbox Demos offer cookbook recipes, sample code, and demo applications, based on Privacy Sandbox APIs.

Updates to top topics selection, the Topics taxonomy and filtering mechanisms, along with speed improvements and enhanced user controls.

Sites that haven't had time to adapt their sites for third-party storage partitioning can take part in a deprecation trial to temporarily unpartition and restore prior behavior of storage, service workers, and communication APIs in content embedded on their site.

In Chrome 115, FedCM supports mediation requirements from Credential Management API which enables users to reauthenticate to the RP in a more streamlined manner after the initial consent.

• Web
• Federated Credential Management API

General availability for these APIs begins in late July with Chrome Stable 115.

Quarterly report for 2023 Q1 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

A new process to new verify developer identity and gather configuration details for the Privacy Sandbox relevance and measurement APIs, across Chrome and Android.

Beginning gradually in Chrome 115, storage, service workers, and communication APIs will be partitioned in third-party contexts. For sites that need time to adjust to this new feature, these deprecation trials will allow them to temporarily keep their third-party storage, service workers, and communication APIs unpartitioned.

Introducing a few updates to FedCM including a new origin trial for auto-reauthentication. When RPs opt-in, this feature enables reauthenticaticating users automatically when they come back after their initial authentication using FedCM.

• Web
• Federated Credential Management API

Beginning gradually in Chrome 115, storage, service workers, and communication APIs will be partitioned in third-party contexts. For sites that need time to adjust to this new feature, these deprecation trials will allow them to temporarily keep their third-party storage, service workers, and communication APIs unpartitioned.

Learn why debugging matters and when to use debug reports in testing.

• Mobile
• Web
• Attribution Reporting API
• Guide

Related Website Sets (RWS) is a way for a company to declare relationships among sites, so that browsers allow limited third-party cookie access for specific purposes.

Learn when the Attribution Reporting API sends aggregatable and event-level reports.

• Web
• Mobile
• Attribution Reporting API
• Guide

Learn how to prevent duplicates in both event-level and aggregatable reports.

• Web
• Mobile
• Attribution Reporting API
• Guide

Read the Private Aggregation API overview and Shared Storage overview. See the use cases and review fundamental concepts for the Private Aggregation API. To ask a question about your implementation, about the demo, or about the documentation: If you

Starting in Chrome 110 (February 2023) we are gradually introducing a fixed value for Android version and device model—the default value will always be `Android 10` on a model `K`.

Evolving First-Party Sets to advance privacy for users and web interoperability for developers.

These services will be available for testing in 2023, for Chrome and Android.

Learn more about Protected Audience API auction features.

• Web
• Protected Audience API
• Guide

Publication date: 2024-02-09 Versions To use the Coordinator Service, including related reports, features and capabilities (collectively the " Coordinator Service "), you and the legal entity on whose behalf you are using the Coordinator Service (if

Quarterly report for 2022 Q4 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

Understand why we shipped this API while it is in incubation in the Web Incubator Community Group.

• Web
• Mobile
• Attribution Reporting API
• Guide

Learn how to register sources to attribute clicks and views to the appropriate events.

• Web
• Mobile
• Attribution Reporting API
• Guide

What aggregation keys are, how they're used in the Attribution Reporting API, and how you can translate goals into keys.

• Web
• Mobile
• Attribution Reporting API
• Guide

Learn how to register attribution triggers to count your conversions.

• Mobile
• Web
• Attribution Reporting API
• Guide

Configure the API to prioritize specific sources or triggers.

• Web
• Mobile
• Attribution Reporting API
• Guide

What you need to know to start working with the Attribution Reporting API. Take advantage of the flexibility of the API. These tools and demos will help you test and understand the API. The background you need to achieve your measurement outcomes.

• Web
• Attribution Reporting API
• Guide

Custom report windows can provide faster event-level reports and selective reporting for aggregatable reports.

• Web
• Mobile
• Attribution Reporting API
• Guide

Part 1 of 3 on debugging Attribution Reporting. Learn why debugging matters and when to use debug reports in testing.

• Mobile
• Web
• Attribution Reporting API
• Guide

Privacy Sandbox ad relevance without third-party cookies.

Part 3 of 3 on debugging Attribution Reporting. Find instructions for how to use debug reports.

• Web
• Mobile
• Attribution Reporting API
• Guide

Part 2 of 3 on debugging Attribution Reporting. Set up your debug reports.

• Mobile
• Web
• Attribution Reporting API
• Guide

Accept-Language Reduction is an effort to reduce passive fingerprinting surfaces in the Chrome browser.

First-Party Sets can allow related domain names that are owned and operated by the same entity to be treated as first-party in situations where first party and third party are otherwise treated differently.

Testing takes time. We're taking a deliberate approach to testing the Privacy Sandbox for the web. The APIs are available for functional testing through origin trials sets the stage for expanded testing in 2023—including live traffic end-to-end experiments—with a focus on understanding ecosystem outcomes and the real-world impact of transitioning away from third-party cookies.

The Federated Credential Management API is shipping in Chrome 108.

• Web
• Federated Credential Management API

Seller API guide and references for the Protected Audience API ad auction. In this article, you'll find a technical reference for the ad auction, as used in the current iteration of the experimental Protected Audience API. Read the developer guide

• Web
• Protected Audience API
• Guide

Seller and buyer guide to generate Protected Audience API auction reports.

• Web
• Protected Audience API
• Guide

For developers and users who want to opt-out of the Protected Audience API.

• Web
• Protected Audience API
• Guide

Troubleshoot worklets and observe Protected Audience API events.

• Web
• Protected Audience API
• Guide

Quarterly report for 2022 Q3 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

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.

Cookies are best fresh, so what are the latest recipes to ensure you can still enjoy spooky season without any stale cookies?

Use a Shared Storage worklet to run A/B testing.

• Web
• Shared Storage API
• Guide

Run a Shared Storage worklet to select a URL and render it in a fenced frame.

• Web
• Shared Storage API
• Guide

Use a Shared Storage to determine what creative a user sees across sites.

• Web
• Shared Storage API
• Guide

Use a Shared Storage worklet to identify known customers.

• Web
• Shared Storage API
• Guide

Generate aggregate data reports using data from Protected Audience and cross-site data from Shared Storage.

• Web
• Private Aggregation API
• Landing page

FedCM origin trial will now be available until the release of Chrome 108, scheduled for November 23, 2022.

• Web
• Federated Credential Management API

To improve privacy, Chrome is changing how storage and communication APIs will behave in future releases. Read more about the upcoming change and how to check if your site is affected by Storage Partitioning.

In October, Chrome will take the next step in reducing the information available in the browser's User-Agent string, to improve privacy for users. With this change, websites and services that rely on the User-Agent string for certain information may need to take action. This post gives some background on what's happening, why Chrome is making this change, and what you can do to prepare.

FLEDGE is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed so it cannot be used by third parties to track user browsing behavior across sites.

FLEDGE Key/Value service

High-level overview of connected services for Attribution Reporting, aimed at technical decision makers.

• Web
• Attribution Reporting API
• Guide

As the Privacy Sandbox timeline changes, learn about the expanding and extending the Privacy Sandbox Relevance and Measurement origin trial and how you can test and give feedback to shape the future of the APIs.

Quarterly report for 2022 Q2 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

Updates including including an expanded Privacy Sandbox Relevance and Measurement trial for Attribution Reporting, FLEDGE, Topics, fenced frames, and Shared Storage. We've published the 2022 Q1 feedback summary report along with hosting more developer Office Hours.

Review a collection of best practices to improve Protected Audience API auction latency.

• Web
• Protected Audience API
• Guide

Learn what noise means, where it is added, and how it impacts your measurement efforts.

• Web
• Mobile
• Attribution Reporting API
• Private Aggregation API
• Guide

Review the latest changes to the Attribution Reporting API.

Learn how to work with, account for, and reduce the impact of noise in your aggregatable reports.

• Mobile
• Web
• Private Aggregation API
• Attribution Reporting API
• Guide

Review the latest changes to the Attribution Reporting API.

Experiment and set up the aggregation service to generate Attribution Reporting summary reports.

CHIPS is a Privacy Sandbox proposal that introduces a mechanism to opt-in to having third-party cookies partitioned by top-level site. The origin trial that started in Chrome 100, will now be available on Chrome 106+ until October 25, 2022.

Quarterly report for 2022 Q1 summarizing the ecosystem feedback received on Privacy Sandbox proposals and Chrome's response.

Updates including including a number of APIs available for origin trial: CHIPS for partitioned cookies and Attribution Reporting, FLEDGE, and Topics as part of the combined Privacy Sandbox Relevance and Measurement trial.

Join the Google Chrome team in our Privacy Sandbox office hours, where developers testing and integrating the Privacy Sandbox technologies can ask questions of Chrome tech leads.

Read Attribution Reporting to see the use cases and key concepts for this API and check the most recent updates. Learn why we shipped the Attribution Reporting API. To ask a question about your implementation, about the demo, or about the

• Web
• Attribution Reporting API
• Guide

Understand the data constraints for source and trigger registration, impact on schedules, as well as reporting limits.

• Mobile
• Web
• Attribution Reporting API
• Guide

Learn about developer testing and the upcoming origin trial allowing for unified experimentation across the Privacy Sandbox relevance and measurement APIs: Topics, FLEDGE, and Attribution Reporting.

The Protected Audience API is a Privacy Sandbox API to serve remarketing and custom audience use cases, designed so it cannot be used by third parties to track user browsing behavior across sites. The API enables on-device auctions by the browser, to choose relevant ads from websites the user has previously visited.

• Web
• Protected Audience API
• Guide

Starting in Chrome 100, CHIPS origin trial allows opting cookies in to "partitioned" storage, with a separate cookie jar per top-level site. Partitioned cookies can be set by a third-party service, but only read within the context of the top-level site where they were initially set.

Securely embed content onto a page without sharing cross-site data.

• Web
• Fenced Frame API
• Landing page

Updates including Privacy Sandbox on Android, CHIPS origin trial, user-agent reduction, the new Topics proposal, and major updates for FLEDGE and Attribution Reporting.

A proposal to keep individual users' IP addresses hidden to prevent cross-site covert tracking.

A proposal to limit the amount of individual user data exposed to sites to prevent covert tracking.

Filters let you define rules for a variety of actions including which conversions are reported.

• Mobile
• Web
• Attribution Reporting API
• Guide

Learn about the role of the contribution budget for Attribution Reporting summary reports and how to allocate it to capture the data you need.

• Mobile
• Web
• Private Aggregation API
• Attribution Reporting API
• Guide

Starting from Chrome 101, the information available in the User-Agent string will be reduced. Sites that haven't had time to migrate away from using the reduced User-Agent string can take part in a deprecation trial to continue receiving the full User-Agent string.

On-device ad auctions to serve remarketing and custom audiences, without cross-site third-party tracking. This article covers the basics of the Protected Audience API and explains some underlying concepts, but doesn't go into much technical detail.

• Web
• Protected Audience API
• Landing page

Protected Audience API is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed so it cannot be used by third parties to track user browsing behavior across sites.

Learn about changes made to Attribution Reporting to reflect community feedback.

Developer guide for on-device ad auctions to choose relevant ads from previously visited websites, designed so it cannot be used by third parties to track user browsing behavior across sites.

• Web
• Protected Audience API
• Guide

Looking back at stats from 2021 and some resolutions for tackling user-agent and cookies in 2022.

Monthly summary of Privacy Sandbox news including a CDS recap and User-Agent testing guidance.

An update on our progress at the 2021 Chrome Developer Summit, with an overview of how we collaborate with stakeholders to discuss, test, and adopt APIs.

Monthly summary of Privacy Sandbox news including the renamed Federated Credentials Management API and W3C TPAC sessions.

How does user-initiated data clearing impact attribution reports? How does that compare with cookie-based measurement?

• Mobile
• Web
• Attribution Reporting API
• Guide

Monthly summary of Privacy Sandbox news including Chrome's user-agent reduction and timeline updates.

Starting in Chrome 95 Beta, an origin trial allowed sites to opt into receiving the reduced user agent string, which will contain only the browser's brand and significant version, its desktop or mobile distinction, and the platform it's running on.

First in the series of monthly summaries for changes across the Privacy Sandbox proposals. Share your feedback on this first edition so we can improve as we go.

First-Party Sets can allow related domain names that are owned and operated by the same entity to be treated as first-party in situations where first party and third party are otherwise treated differently.

The Conversion Measurement API is changing in Chrome 92. Following the API proposal 's changes in the first months of 2021, the API implementation in Chrome is evolving. Here's what's changing: What remains unchanged in Chrome 92 is the set of

Review Chrome platform status, resources, and feature release timelines.

FLoC enables interest-based advertising in a way that preserves privacy. As a user moves around the web, their browser is assigned to an "interest cohort" along with thousands of others with a similar browsing history. This is done without sharing individual browsing history with the browser vendor or anyone else.

Short explanations of key concepts.

Federated Learning of Cohorts (FLoC) provides a privacy preserving mechanism for interest-based ad selection. This article explains how to take part in the FLoC origin trial.

The Privacy Sandbox proposes a set of privacy-preserving APIs to support business models that fund the open web in the absence of tracking mechanisms like third-party cookies. This post provides an update on the status of the APIs and proposals.

The Privacy Sandbox proposes a set of privacy-preserving APIs to support business models that fund the open web in the absence of tracking mechanisms like third-party cookies. This post explains how to participate.

了解如何以买方身份参与广告竞价并出价。

• Web
• Protected Audience API
• Guide

此提案须遵守 Privacy Sandbox 注册流程，并且 证明。如需详细了解这些证明，请参阅 访问 提供的证明链接 。此提案的后续更新将 说明了获得该系统访问权限的要求。 移动应用安装广告（也称为“用户获取广告”）是一种旨在鼓励用户下载移动应用的移动广告。 这些广告通常根据用户的兴趣和受众特征投放，而且经常出现在其他移动应用中（例如游戏、社交媒体和新闻应用）。用户点击应用安装广告后，即会直接跳转到应用商店去下载相关应用。

• Mobile
• Protected App Signals API
• Guide

您可通过 直观 的方式或借助 SQL 查询 通过 Perfetto 来分析 Protected Audience 竞价。广告技术平台可以将性能分析和 Perfetto 相结合，以衡量 Protected Audience 竞价的效果，包括： 克隆 Perfetto 和 Privacy Sandbox 仓库。 在 Android Studio 中，从 privacy-sandbox-samples/Fledge/FledgeKotlin 目录下打开 Protected Audience 示例应用。

• Mobile
• Protected Audience API
• Guide

Protected Audience 提供了一系列 API，用于联接和退出自定义 受众群体（作为 android.adservices.customaudience 软件包 的一部分）。对于 还有一些 CLI 命令可用于列出和查看 自定义受众群体本指南概述了广告技术开发者需要执行的步骤 检查加入的自定义受众群体的状态。 出于安全和隐私方面的考虑，默认情况下，系统不会显示自定义受众群体 并且只能出于调试目的直接进行检查。它们仅可见 使用以下命令： 然后，如需启用 adservices shell

• Mobile
• Protected Audience API
• Guide

借助 fetchAndJoinCustomAudience API，买家可以利用其设备端存在的合作伙伴 MMP 或 SSP 来委托加入自定义受众群体。 大致工作原理是，设备端调用方（无论是 MMP SDK 还是 SSP SDK）会创建一个如下所示的 fetchAndJoinCustomAudienceRequest ： 关于所有可选参数的重要说明：如果这些参数在提取请求内设置，它们的数据就无法被从买家返回的内容替换，从而让设备端调用方可以更好地控制哪些自定义受众群体将保持不变。 fetchUri

• Mobile
• Protected Audience API
• Guide

Protected Audience 调试报告让广告技术平台开发者可以声明远程网址，以便在竞价胜出或落败时从设备接收 GET 请求。它支持以下使用情形： 事件级调试报告适用于 Privacy Sandbox 开发者预览版 9 中的测试。具备广告 ID 的所有设备均支持调试报告。 长期计划是使平台借助不公开汇总服务报告竞价结果。这可确保事后报告无法用于将单个用户的自定义受众群体加入发布商的应用。事件级报告是临时的，在足够的报告框架发布后将停用。 详细了解 Chrome 原始 FLEDGE

• Mobile
• Protected Audience API
• Guide

了解 k-匿名性检查将如何应用于 Protected Audience

• Web
• Mobile
• Protected Audience API
• Guide