Privacy Sandbox

What is Privacy Sandbox?

Note: Google discontinued the Privacy Sandbox initiative. In April 2025, Google confirmed it would not deprecate third-party cookies in Chrome after all, and in October 2025 it retired the remaining Privacy Sandbox APIs on both Chrome and Android, including Attribution Reporting, Topics, and Protected Audience, citing low adoption. The description below reflects how the initiative was designed to work while it was active.

Privacy Sandbox was a Google initiative designed to phase out cross-site and cross-app tracking mechanisms, such as third-party cookies and persistent device identifiers, while preserving the ability of advertisers and publishers to deliver targeted advertising and measure campaign effectiveness. It introduced a set of privacy-preserving APIs that aggregated and anonymized user data rather than exposing individual-level signals. The initiative spanned both the web and Android platforms, each with tailored technical approaches to balancing user privacy with advertising utility.

How it works

Privacy Sandbox operated by replacing individual tracking mechanisms with privacy-safe APIs that processed data on-device or within aggregated cohorts, preventing any single party from accessing granular user-level data.

Privacy Sandbox on the Web

On the web, Privacy Sandbox was intended to address the deprecation of third-party cookies, which have historically allowed advertisers to track users across different websites -- a deprecation Google ultimately abandoned. Google had introduced a suite of APIs to replace cookie-based tracking. Topics API, which replaced the earlier Federated Learning of Cohorts (FLoC) proposal, enabled interest-based advertising by assigning users to broad interest categories derived from their browsing history, without exposing that history to advertisers. Attribution Reporting API provided conversion measurement by generating aggregated, noisy reports rather than individual-level click and conversion data. These APIs were designed so that user data never left the browser in an identifiable form, before Google retired them in October 2025.

Privacy Sandbox on Android

On Android, Privacy Sandbox targeted the persistent use of the Google Advertising ID (GAID) and other device-level identifiers that enable cross-app tracking. Google had introduced a set of Android-specific APIs, including Topics API for interest-based advertising on mobile, and the Attribution Reporting API for measuring installs and in-app conversions. The Protected Audience API enabled remarketing and custom audience targeting without requiring ad networks to access raw device identifiers. These APIs shifted data processing to the device itself, limiting what data was shared with advertisers and measurement partners. Google retired all of these Android APIs in October 2025 alongside the web APIs, and GAID access was not restricted as originally planned.

Key Technical Mechanisms

Across both environments, Privacy Sandbox relied on several shared principles. On-device processing kept sensitive data local rather than transmitting it to external servers. Differential privacy techniques added calibrated statistical noise to aggregated reports, preventing re-identification of individuals. Aggregation thresholds ensured that conversion reports were only generated when a minimum number of events was reached, suppressing data for small user segments. These mechanisms were designed to reduce the surface area available for covert tracking while still enabling marketers to evaluate campaign performance at a population level.

Why it matters

Privacy Sandbox was intended to fundamentally change how digital advertising operates, affecting advertisers, publishers, ad networks, and measurement providers simultaneously. Had it proceeded, the shift away from individual-level tracking would have required marketers to adopt new measurement methodologies, including aggregated attribution models and privacy-preserving technologies (PPTs). Instead, third-party cookies remain available in Chrome and GAID access on Android was not restricted, so the disruption these APIs were built to address did not materialize on Google's platforms. Apple's App Tracking Transparency (ATT) framework, which restricts IDFA availability on iOS, remains active and follows a separate path from Privacy Sandbox's discontinuation. Marketers who invested in first-party data strategies, contextual targeting, and aggregated reporting frameworks in anticipation of Privacy Sandbox still benefit from that groundwork for privacy-compliant measurement generally, even though the specific APIs they may have built against are no longer available.

How to implement Privacy Sandbox for mobile measurement

Historical reference: Google discontinued Privacy Sandbox and retired its APIs in October 2025, so the steps below are no longer actionable. They are kept here for historical reference on how Privacy Sandbox-compatible measurement was intended to work.

Implementing Privacy Sandbox-compatible measurement required a structured approach across technical integration, data strategy, and campaign methodology.

1. Audit existing tracking dependencies. Identify all measurement and targeting workflows that rely on third-party cookies on the web or GAID on Android. Map which attribution, retargeting, and analytics systems will be affected when these identifiers are restricted.

2. Integrate Privacy Sandbox APIs. For Android, implement the Attribution Reporting API and Topics API through the Android SDK. Ensure your MMP, such as Airbridge, has updated its SDK to support Privacy Sandbox API calls natively, so attribution data continues to flow through compliant channels.

3. Strengthen first-party data collection. Build consented user identity signals through login flows, CRM integration, and in-app event tracking. First-party data provides a durable measurement foundation that is not subject to Privacy Sandbox restrictions.

4. Adopt aggregated reporting workflows. Transition campaign analysis from user-level reports to aggregated cohort and conversion-level reports. Configure attribution windows and aggregation thresholds to align with Privacy Sandbox API requirements, accepting that some granularity is traded for privacy compliance.

5. Implement a consent management platform (CMP). Where consent can be obtained, consented identifiers such as hashed emails or phone numbers improve match rates and measurement accuracy within Privacy Sandbox boundaries. A CMP ensures consent signals are captured and passed correctly to downstream measurement systems.

6. Test and validate in sandbox environments. Google provides test environments for Privacy Sandbox APIs on both Chrome and Android. Run parallel measurement tests comparing Privacy Sandbox API outputs against existing tracking methods to quantify any gaps before full migration.

7. Monitor the current state of platform-level privacy changes. Privacy Sandbox itself was discontinued in October 2025, and GAID and third-party cookies were not deprecated as originally planned. Track ATT/IDFA on iOS and any future Android or browser privacy initiatives instead, since Privacy Sandbox's roadmap is no longer the relevant reference point.

Related concepts