Protected Audiences
Data & TrackingAlso: Protected Audience API · FLEDGE
Quick definition
Protected Audiences is a Chrome browser feature that lets advertisers show remarketing ads without third-party cookies. Interest groups and auctions run locally inside the browser instead of on an ad server, so no single party sees a user's full browsing history. It's part of Google's Privacy Sandbox initiative.
How it varies across Australia
Adoption among Australian advertisers is still early and concentrated in larger programmatic buyers testing the API alongside existing cookie-based retargeting. Most mid-market businesses haven't touched it yet because their ad platforms handle the transition behind the scenes.
See data and tracking maturity across Australian industries →What it actually means
Third-party cookies used to work like a shared notebook. Every site an advertiser could reach wrote a user's visit into the same notebook, and any ad platform could flip through it to build a retargeting list. Protected Audiences deletes the shared notebook and gives each user's own browser a private diary instead.
Here's the mechanism. When a user visits a site, that site can ask the browser to add them to an interest group, something like 'visited this product page.' That group lives only in the user's browser, never on a server. When the user later visits a page with ad space, an auction runs locally inside the browser, using those interest groups plus bids from advertisers, and the winning ad is chosen without any single party seeing the full picture.
This matters because it's Google's answer to the death of the third-party cookie in Chrome, following years of delay. Attribution, conversion tracking and audience segmentation all had to be rebuilt around a browser that increasingly refuses to hand over raw user data. Protected Audiences is one piece of that rebuild, sitting alongside other Privacy Sandbox tools that handle measurement and topic-based targeting separately.
Protected Audiences doesn't kill remarketing. It moves the decision-making into a room nobody outside the browser gets to walk into.
How it shows up
Protected Audiences shows up quietly in the background of Google Display and YouTube remarketing campaigns run through platforms that have already integrated the API. Marketers rarely see it directly. It surfaces in reporting as slightly different reach numbers on remarketing lists once third-party cookie support winds down, and in agency conversations about why last year's retargeting segments don't translate cleanly.
The Australian context
Australian advertisers are exposed to this shift the same way as any Chrome-majority market, but the local effect is muted by two things. Most Australian mid-market businesses buy programmatic media through managed platforms like Google Ads or DV360 rather than building their own bidding logic, so the API transition happens upstream and invisibly. The bigger local risk sits with businesses that built custom retargeting pixels or DIY audience segmentation years ago and haven't revisited that stack since. The Office of the Australian Information Commissioner (OAIC) hasn't issued specific guidance on Protected Audiences, but the broader direction of Australian privacy reform points the same way Chrome does, toward less raw data sharing and more first-party control.
Where people get this wrong
Related terms
Common questions
Is Protected Audiences the same as FLEDGE?
FLEDGE was the earlier name Google used during development. Protected Audiences is the production name for the same underlying API, part of the broader Privacy Sandbox initiative Google is building into Chrome.
Do I need to do anything to use Protected Audiences?
If you buy media through major platforms like Google Ads or a demand-side platform that's integrated the API, the transition largely happens without you needing to change anything. Businesses running custom-built ad tech need to work directly with their developers.
Does Protected Audiences stop remarketing from working?
No. It's designed to preserve remarketing capability without third-party cookies. Targeting precision may shift compared to old cookie-based lists, but the core function of showing ads to past visitors still works.
Why should a marketer who doesn't buy programmatic media care about this?
Because it signals the direction every browser is heading, less raw data sharing, more in-browser processing. Even if you don't touch programmatic buying, the same logic will eventually reshape email tracking, pixel-based analytics and CRM integrations.
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 →