Attribution & Measurement

Privacy Sandbox (Android)

Also known asAndroid Privacy SandboxGoogle Privacy Sandbox

Google's multi-year initiative to introduce privacy-preserving alternatives to GAID-based ad tracking on Android — the platform's eventual SKAN equivalent.

trending

Key takeaways

  1. 01Privacy Sandbox for Android = Google's aggregate, privacy-preserving attribution stack. Roughly Apple's SKAN equivalent.
  2. 02Three core APIs: Attribution API (SKAN-like postbacks), Topics API (on-device interest targeting), Protected Audiences API (on-device audience activation).
  3. 03Rollout timeline: announced 2022, beta testing 2024-2026, expected full availability ~2027.
  4. 04Different design philosophy from SKAN — more developer input, longer transition period, less dramatic immediate impact.

Privacy Sandbox for Android is Google's multi-year initiative to introduce privacy-preserving alternatives to GAID-based ad tracking on Android. Announced in February 2022, the project's goal is to give the Android ecosystem something analogous to Apple's SKAdNetwork — attribution and targeting that work without exposing device-level identifiers — but on a longer rollout timeline with more developer / advertiser input baked into the design process.

Three core APIs in Privacy Sandbox

  1. Attribution API (formerly Attribution Reporting): SKAN-like aggregated install attribution. The ad network gets aggregated postbacks indicating which campaigns drove conversions, without identifying individual users. Includes event-level + aggregatable reports with privacy budgets.
  2. Topics API: on-device interest-based ad targeting. The device locally classifies user activity into "topics" (e.g., "sports", "cooking", "fintech"); apps can request the user's topics to serve relevant ads, without raw activity exposure.
  3. Protected Audiences API (formerly FLEDGE on web): on-device audience activation for retargeting. Audiences are computed on-device; ad-serving decisions happen locally. The browser / OS never sends raw user data off-device.

Plus supporting APIs: SDK Runtime (sandboxed third-party SDK execution), Shared Storage (cross-app data sharing with privacy controls), Aggregation Service (privacy-preserving cross-report aggregation).

Design differences from Apple's SKAN

2026 status

  • Developer beta testing throughout 2024-2026.
  • Major MMPs (AppsFlyer, Adjust, Singular) building Privacy Sandbox support; integration documentation available.
  • Some early-adopter campaigns testing Attribution API in parallel with GAID-based attribution.
  • GAID still broadly available; no forced deprecation date publicly announced as of mid-2026.
  • Most mobile-app advertisers operate Android attribution primarily on GAID, with Privacy Sandbox as an emerging measurement signal.

What to do now

  1. Get familiar with the APIs — start with the Attribution API and SDK Runtime. These will have the biggest direct impact on mobile-app advertisers.
  2. Work with your MMP — major MMPs are building Privacy Sandbox support; understand their integration roadmap and beta-test programs.
  3. Test in parallel — once your MMP supports it, run Privacy Sandbox attribution alongside GAID-based attribution. Compare results, identify gaps.
  4. Invest in first-party signal regardless — CRM, web-to-app, owned-channel measurement matters more as third-party tracking fades on both platforms.

Privacy Sandbox for Android — the three core APIs

APIWhat it doesiOS analogImpact for mobile UA
Attribution APIAggregated install attribution without device IDs — Apple-signed postback equivalentSKAdNetworkReplaces GAID-based deterministic attribution over time
Topics APIOn-device interest classification (e.g., "sports", "fintech") shared with advertisers via the device, not user-trackingNo direct analog (closest: ATT-restricted contextual)Replaces third-party-cookie-style interest targeting
Protected Audiences APIOn-device audience activation — retargeting and lookalikes computed locally without sending raw data off-deviceNo direct analogReplaces cross-app retargeting

Phased rollout 2022-2027 with extensive developer beta testing; GAID continues working in parallel during transition. Major MMPs (AppsFlyer, Adjust, Singular) are integrating Attribution API support now.

Quick answers

What is Privacy Sandbox for Android?

Privacy Sandbox is Google's multi-year initiative to introduce privacy-preserving alternatives to GAID-based ad tracking on Android. Three core APIs: Attribution API (SKAN-like aggregated install attribution), Topics API (on-device interest targeting), Protected Audiences API (on-device audience activation). Announced 2022, expected full rollout ~2027.

How is Privacy Sandbox different from Apple's ATT?

**Apple's ATT** rolled out in a single iOS update (14.5, April 2021), instantly forcing IDFA opt-in. **Privacy Sandbox** is phasing over years (2022-2027+) with extensive developer beta testing and feedback. More design input from the industry, more gradual transition, hybrid coexistence with GAID during transition. The eventual end state is similar (aggregated privacy-preserving attribution), but the journey is meaningfully different.

When will Privacy Sandbox replace GAID?

Expected ~2027 for full rollout, though Google has not publicly announced a forced GAID deprecation date as of mid-2026. Developer beta testing has been running 2024-2026. Major MMPs are building Privacy Sandbox support. Most mobile-app advertisers should expect to operate Android attribution primarily on GAID through 2027, with Privacy Sandbox as an emerging measurement signal in parallel.

What should I do to prepare for Privacy Sandbox?

(1) Get familiar with the APIs — start with Attribution API and SDK Runtime. (2) Work with your MMP — major MMPs (AppsFlyer, Adjust, Singular) are building Privacy Sandbox support. (3) Test in parallel — run Privacy Sandbox attribution alongside GAID-based attribution once your MMP supports it. (4) Invest in first-party signal regardless — CRM, web-to-app, owned-channel matters more as third-party tracking fades on both platforms.

Back to glossary