Google launches Privacy Sandbox on Android in beta, starting with a small number of Android 13 devices and bringing the OS in line with Apple's ATT updates
Context & Ripple Effects
This beta is the third step in a deliberately slow rollout. Google announced its plan in February 2022 with an Ad ID preserved for two years and a promise of less disruption than Apple's ATT, opened a Developer Preview on Android 13 that April exposing the Topics API and SDK Runtime, and has since been trialing the same Topics and FLEDGE tools with Chrome users before bringing them to phones.
The differentiator Google has emphasized from the start is process: as the Mobile Dev Memo analysis noted, this is a two-year transition built with ad industry input, unlike Apple's ATT, which shipped with little external consultation. Today's beta moves that transition from developer machines onto real consumer devices.
First-order effects
- A small percentage of Android 13 users now run with Privacy Sandbox APIs active, meaning advertisers and app developers get their first real-device signal on how Topics-based targeting performs at scale.
Second-order effects
- Mobile ad-tech vendors now have to maintain dual stacks — sandbox APIs where enabled, the still-supported Ad ID elsewhere — extending the SDK integration burden that the Android 13 preview already signaled via SDK Runtime.
Third-order effects
- If the staged model holds, mobile targeting converges on OS-level privacy APIs controlled by the platform owners, with Google's long runways and Apple's hard cutoffs defining two competing templates for how the ad industry absorbs the change.
The trend: Mobile advertising is migrating from third-party tracking identifiers to platform-operated privacy APIs, with the pace set by whether the OS owner stages the shift (Google) or forces it abruptly (Apple).