Glossary
What is Privacy Sandbox on Android?
Privacy Sandbox on Android is Google's initiative to build privacy-preserving advertising APIs that reduce cross-app tracking while still supporting personalised advertising and measurement.
The approach
Apple removed a capability and let the industry adapt. Google is attempting to build replacements first and remove the capability afterwards.
The Sandbox is a set of APIs designed so that the useful outputs of tracking — relevant advertising, attribution, frequency control — survive without the underlying cross-app identifier. Processing happens on the device or in aggregate, and what leaves is a result rather than a record.
The main components
- Topics. The device infers coarse interest categories locally and shares a small number of them, rather than exposing browsing or app history.
- Protected Audience. On-device auctions for remarketing, so the audience list never leaves the device.
- Attribution Reporting. Aggregated, noised conversion measurement in place of user-level matching.
- SDK Runtime. Third-party SDKs run in a separate process with restricted access to the host app's data.
What it means practically
Three things follow for anyone planning against it.
Targeting gets coarser. Topics are broad categories, not the granular segments third-party data supported. Expect less precision and, in most tests so far, workable performance.
Measurement gets noisier. Aggregated attribution with deliberate noise means small effects become hard to detect, and thresholds apply as they do elsewhere.
On-device processing changes the architecture. Auctions and audience matching that used to happen server-side move to the device, which is a real engineering change for anyone building on the platform.
The strategic advice is identical to iOS: do not build anything that depends on the current identifier, and invest in first-party data and causal measurement now.
Common questions
When will the GAID be removed?
Google has moved on a longer and more revised timeline than Apple. Treating the identifier as temporary is the safe planning assumption regardless of the published dates.
Should I test Privacy Sandbox APIs now?
Yes, if you have engineering capacity. Migrating under deadline pressure is where errors enter, and the on-device model is different enough to need real integration time.
More in privacy and compliance
The identifiers, consent signals and rules that bound targeting.