Privacy Sandbox

Data & Tracking

Also: Google Privacy Sandbox · Chrome Privacy Sandbox

What it isGoogle's replacement for third-party cookies
StatusDelayed, direction still shifting
Built byGoogle, inside Chrome
EffectLess granular ad targeting and measurement

Quick definition

Privacy Sandbox is Google's set of proposed Chrome browser technologies meant to replace third-party cookies while still allowing some form of ad targeting and measurement. It groups users into interest cohorts and runs auctions inside the browser instead of tracking individuals across every site they visit.

How it varies across Australia

Adoption tracking for Privacy Sandbox APIs among Australian advertisers sits well behind the conversation about it. Most local businesses are aware cookies are going away but haven't tested the replacement tools directly, leaning instead on first-party data and server-side tracking as the more reliable near-term fix.

See data and tracking maturity across Australian industries

What it actually means

For years, third-party cookies let advertisers follow a person from a news site to a shopping site to an ad network and stitch together one profile. Privacy Sandbox is Google's attempt to kill that mechanism inside Chrome while keeping enough signal alive that advertising still functions.

Instead of tracking an individual, the browser itself groups people into interest cohorts based on browsing behaviour, then lets advertisers bid against a cohort rather than a person. Conversion measurement moves into aggregated, noisy reports rather than the clean, user-level attribution marketers are used to.

The timeline has been unstable. Google delayed the cookie deprecation deadline multiple times, then in 2024 said it would keep third-party cookies available with a new user choice prompt instead of removing them outright. That reversal matters for anyone doing attribution or retargeting: the ground keeps moving under GA4, server-side tracking and CAPI setups being built to handle a cookieless future that hasn't fully arrived.

What hasn't moved is the direction of travel. Apple's Safari killed third-party cookies years ago. Firefox followed. Regulators are pushing harder on consent everywhere. Building on first-party data, consented email lists and server-side tracking is the safer bet regardless of what Chrome ends up shipping.

Privacy Sandbox isn't a feature you switch on. It's Google redrawing the rules of the auction it also runs.

How it shows up

Privacy Sandbox shows up as gaps and noise, not as a dashboard you check. Retargeting audiences that used to rebuild instantly take longer or stay smaller. Attribution reports from Google Ads start showing modelled conversions filling holes where cookie-based tracking used to sit. Frequency capping across sites gets less precise, so the same person may see an ad more often than intended. None of this arrives as a single event. It accumulates as cookie-based signal quietly degrades in the background.

The Australian context

Australian advertisers face the same technical shift as everyone else but with an added layer from the Privacy Act reforms moving through parliament. Tighter consent requirements domestically are pushing in the same direction as Privacy Sandbox globally, toward less default tracking and more explicit opt-in. Businesses building first-party data collection now are preparing for both changes with one investment rather than reacting twice.

Where people get this wrong

Assuming Privacy Sandbox means cookies are already gone.Google reversed course and kept third-party cookies available with a consent prompt. The rollout has been delayed repeatedly, so plans built on a fixed deprecation date have been wrong more than once.
Waiting for Google to finalise the spec before adjusting tracking.First-party data, consented email capture and server-side tracking are useful regardless of what Chrome ships. Waiting for certainty wastes the time that should go into building that foundation.
Treating Privacy Sandbox as only a Google problem.Safari and Firefox already block third-party cookies by default. Any measurement strategy built around cookies has already been degraded on those browsers for years, whatever Chrome eventually does.

Related terms

Common questions

Is Privacy Sandbox replacing cookies right now?

Not fully. Google delayed and then reversed its plan to remove third-party cookies outright, opting instead for a Chrome consent prompt that lets users choose. The Privacy Sandbox APIs exist and are being tested, but cookies haven't disappeared from Chrome the way originally announced.

How does Privacy Sandbox affect retargeting?

It replaces individual-level tracking with interest cohorts and browser-run auctions, so retargeting becomes less precise. Audiences are built around groups of similar users rather than the exact person who visited your site, which softens both targeting accuracy and reported performance.

Do I need to do anything about Privacy Sandbox right now?

Not urgently, but the direction is clear. Invest in first-party data collection, consented email lists and server-side tracking now rather than waiting for Google's specification to settle. Those investments hold their value regardless of how Privacy Sandbox eventually ships.

Does Privacy Sandbox apply to Safari and Firefox too?

No, Privacy Sandbox is a Chrome-specific initiative from Google. Safari and Firefox already block third-party cookies by default using their own mechanisms, and have done so for years. Chrome is the last major browser still working through this transition.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →