Audience Targeting

Broad Targeting vs Website Custom Audiences

In short: Both can draw on the same pixel and Conversions API stream, but one targets a defined group of past visitors and the other targets nobody in particular. Website custom audiences are built from pixel or Conversions API events, segmented by page, action, time on site, and a retention window, and they are only as accurate as your tracking. Broad targeting uses that same event stream, but as live optimization signal rather than as a named list to include or exclude. Use website custom audiences to act on people who already showed intent; use broad to find people who haven't shown you anything yet.

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

Broad Targeting

Runs a Meta ad set with little definition beyond location, age, and gender, leaving the delivery system to find buyers from conversion signal alone.

You leave interests and behaviors empty and let Meta's optimization use pixel and Conversions API events to locate people likely to trigger your chosen event. It has become the default posture on Meta because the system finds pockets no manual interest stack would ever describe. It needs enough conversion volume to learn, and advertisers frequently kill it mid-learning before delivery has stabilized.

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.

 Broad TargetingWebsite Custom Audiences
Who it can reachAnyone in the eligible population, whether or not they have ever visited your site.Only people who triggered a qualifying pixel or Conversions API event within the retention window.
Role of tracking healthTracking health affects only the optimization event it is bidding toward.Tracking health determines the audience's entire size and accuracy - broken pixel or CAPI coverage directly shrinks the list.
Typical useProspecting for new visitors and buyers.Retargeting site visitors, cart abandoners, or past converters; also a lookalike seed.
How far back it reachesNot applicable - it has no lookback window, only live signal.Bounded by the retention window you set, capped at whatever Meta's current maximum allows.
Effect of browser signal lossWeakens the optimization event overall, making the algorithm learn from less data.Directly undercounts membership, since lost browser events are visitors the audience never learns about.
Fix for signal lossImproving Conversions API coverage strengthens the optimization event feeding delivery.Same fix - server-side event coverage materially changes both the size and quality of the audience.
Failure modeNot enough conversion volume for the algorithm to settle on a pattern.Segmented too broadly, such as all visitors regardless of page or intent, diluting it into something closer to broad reach.

What actually separates them.

01

A website custom audience is a named, bounded group defined by past visits; broad targeting has no group at all, only a live optimization signal.

02

Both draw on the same pixel and Conversions API stream, but broad uses it to steer who gets shown ads next, while a website custom audience uses it to define who is already in the list.

03

Website custom audiences are capped by a retention window, so old visits eventually age out; broad targeting has no such window since it only cares about current signal.

04

Server-side event coverage improves both, but it directly changes a website custom audience's size in a way you can observe, while its effect on broad targeting is only visible through the optimization event's overall quality.

05

Website custom audiences can be segmented by page or action to create intent tiers; broad targeting has no segmentation lever, since it is not built from a defined list to slice.

Which one should you use?

Use Broad Targeting when

  • You are prospecting for entirely new visitors who have never touched your site.
  • Your pixel and Conversions API coverage is too thin to build a meaningfully sized website custom audience yet.
  • You want the widest possible reach for early-funnel awareness rather than a retargeting play.
  • You have enough conversion volume overall for the optimization event to learn without relying on a visitor list.

Use Website Custom Audiences when

  • You want to retarget people who visited a specific high-intent page, like a pricing or checkout page.
  • You are building a cart-abandonment or browse-abandonment sequence.
  • You want a clean, intent-based seed for a lookalike audience rather than seeding from all converters.
  • You need to exclude recent site converters from a prospecting campaign to avoid wasting spend on people who already bought.

Common questions.

Why is my website custom audience smaller than my actual traffic?

Browser-based tracking restrictions mean the pixel alone misses a meaningful share of visits, so the audience undercounts real traffic even when your site's analytics show more visitors. Adding server-side event coverage through the Conversions API recovers some of that gap and typically grows both the size and reliability of the audience.

What retention window should I use for a website custom audience?

It depends on your sales cycle - a short-consideration product benefits from a tighter window that keeps the list focused on recent, warm intent, while a longer sales cycle justifies a wider window to avoid losing people who are still deciding. There is a platform maximum you cannot exceed, so check the current cap when building the audience rather than assuming an old number still applies.

Can I use a website custom audience as a broad targeting suggestion?

Yes, entering it as an Advantage+ Audience suggestion gives it early delivery priority before the system expands past it, which is different from running fully broad with nothing entered. That blended approach is common when you want a visitor-based head start without fencing the ad set to only that group.

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 freeSee how it works

Related comparisons

All comparisons