Audience Targeting

Advantage+ Audience vs Website Custom Audiences: Delivery Behavior vs Your Own Traffic

In short: Website Custom Audiences are built from what actually happens on your site - pages viewed, actions taken, inside a retention window - and Advantage+ Audience is how Meta chooses to use that list once you hand it over. Fed as a suggestion, a Website Custom Audience only biases early delivery, same as an interest would; fed as an exclusion, it fully holds. The quality question splits cleanly too: a Website Custom Audience is only as good as your pixel and Conversions API setup, while Advantage+ Audience's quality depends on how much conversion signal the whole account has accumulated. Chooser: fix your tracking before you touch audience mode, because a thin or broken pixel weakens both the list and everything Advantage+ Audience tries to expand from it.

By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026

Advantage+ Audience

Meta's automated audience selection, where anything you enter acts as a suggestion rather than a boundary and delivery is free to expand beyond it.

You supply an audience suggestion - interests, custom audiences, demographics - and Meta prioritizes it briefly before searching the full eligible pool. It is now the default in most objectives and has largely superseded manual detailed targeting. The mistake is reading an unchanged reach estimate as proof nothing changed: exclusions and age or location limits still bind, but your interest selections effectively do not.

Full definition

Website Custom Audiences

A Meta custom audience built from pixel or Conversions API events, segmented by pages visited, actions taken, time on site, and a retention window.

Rules run against the events your site sends, so accuracy tracks pixel and CAPI health directly, and the retention window caps how far back membership can reach. Use them for retargeting tiers and as lookalike seeds built on high-intent actions. Browser signal loss means these lists undercount real traffic, so adding a server-side event stream materially changes their size and quality.

Full definition

Side by side.

The differences that actually change what happens in your account.

	Advantage+ Audience	Website Custom Audiences
What it depends on	Aggregate conversion signal across the account, not any single data source.	Your site's pixel and Conversions API event stream directly.
Effect of browser signal loss	Indirect - a weaker signal overall means less to expand from.	Direct - undercounts real visitors, since browser-only events get dropped; server-side CAPI events are what close the gap.
How membership is defined	Not applicable - it has no membership of its own.	By rules against events: which pages, which actions, within a chosen retention window.
Used as inclusion	Interprets any audience handed to it as a suggestion, expanding past it.	In manual mode, restricts delivery to the list; under Advantage+ Audience, becomes a suggestion like any other input.
Used as exclusion	Honors exclusions fully regardless of mode.	Is the standard suppression source - for example excluding recent purchasers from prospecting.
Retention window	No equivalent concept.	A hard cap - anyone whose qualifying visit falls outside the window drops off automatically.
What improves it	More conversion volume flowing through the account.	Better event coverage - server-side tagging, deduplication, more complete parameter data.

What actually separates them.

A Website Custom Audience's quality is a data-engineering problem - pixel and CAPI coverage - while Advantage+ Audience's quality is an account-volume problem - how much conversion signal exists to expand against.

Website Custom Audiences carry a retention window that silently drops people over time; Advantage+ Audience has no equivalent decay since it is not a stored list.

Excluding a Website Custom Audience holds under any audience mode, but including one only holds as a hard filter when Advantage+ Audience is off.

Website Custom Audiences undercount real traffic when browser tracking is blocked, which is a tracking problem; Advantage+ Audience can still perform reasonably even with an undercounted signal because it draws on account-wide data too.

Improving Conversions API coverage makes a Website Custom Audience larger and more accurate immediately, and it also improves whatever Advantage+ Audience expands from it, since better source signal produces better modeled reach.

Which one should you use?

Use Advantage+ Audience when

You want a Website Custom Audience to seed retargeting-style delivery without capping the campaign strictly to site visitors.
Your Conversions API coverage is solid, giving Advantage+ Audience good signal to expand from even beyond the website list.
You are running prospecting and only want the website list as a directional hint, not the entire eligible pool.
You need exclusions of recent site converters to hold firmly while leaving inclusion flexible.

Use Website Custom Audiences when

You need a retargeting ad set that only reaches actual past visitors of a specific page or funnel step.
You are building a lookalike seed and need a clean, high-intent source - cart abandoners or checkout starters, not just any site visitor.
You want to diagnose tracking health, since a Website Custom Audience that stops growing is often the first visible sign of a pixel or CAPI break.
You need delivery locked to known visitors for a defined retargeting window, run without Advantage+ Audience expansion.

Common questions.

Why is my Website Custom Audience smaller than my actual traffic?

Browser-based tracking undercounts visitors because of iOS restrictions, ad blockers, and cookie limits, so a pixel-only setup will always show fewer people than actually visited. Adding server-side Conversions API events closes most of that gap since they do not depend on the visitor's browser cooperating.

Does the retention window reset if someone visits again?

Yes - each qualifying visit or event refreshes that person's place in the window, so repeat visitors stay in the audience longer than one-time visitors. Someone who only visited once will drop off once their visit ages past the window, regardless of what else happens in the account.

If I use my Website Custom Audience as a suggestion under Advantage+ Audience, will it still work as retargeting?

It will bias delivery toward that list early on, but Meta can and will serve to people outside it once it finds better-converting users elsewhere. If you need delivery to stay strictly inside your site visitors, exclude everyone else or run the ad set with Advantage+ Audience off.

Should I fix my pixel or switch to Advantage+ Audience first?

Fix tracking first. Advantage+ Audience expands on whatever signal the account has, so a broken or thin pixel weakens both your Website Custom Audiences and anything built on top of them, no matter which audience mode you run.

Or stop choosing between them.

AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.

Try AdFlint free See how it works

Related comparisons

All comparisons