Audience Targeting

Lookalike Audiences vs Website Custom Audiences: Modeled Reach or Real Visitors

In short: Both can retarget or seed off your site's traffic, but only one of them is actually made of your visitors. A Website Custom Audience is a real list - people who fired a pixel or Conversions API event on pages you control, segmented by what they did and when. A Lookalike Audience is a modeled population sized as a percentage of a country, and unless you seed it from your website traffic, none of its members ever set foot on your site. Website Custom Audiences decay with signal loss and need Conversions API to stay accurate; lookalikes decay when the seed feeding them is weak or too broad. Use a Website Custom Audience to retarget people who were actually there, and a Lookalike Audience to prospect for people who merely resemble them.

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

Lookalike Audiences

Meta audiences modelled on a seed list, matching users who resemble your source on the signals Meta holds, sized as a percentage of a chosen country.

You pick a source - purchasers, high-value customers, engaged visitors - and a percentage; smaller percentages mean closer resemblance and less reach, larger ones the reverse. A value-based source lets Meta weight by revenue. Their edge has narrowed as broad targeting and Advantage+ audience improved. The persistent error is seeding from a large low-quality list, which models the wrong person very precisely.

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.

	Lookalike Audiences	Website Custom Audiences
Who is actually inside	People Meta believes resemble the seed - no guarantee any of them ever visited your site.	People who generated a real pixel or Conversions API event on your site.
What you enter to build it	A seed audience and a percentage, typically 1% to 10% of a chosen country.	An event source plus rules - which URLs, which actions, how much time on site.
Size control	Set by the percentage chosen, independent of how much real traffic you have.	Set by how many real visitors matched within your retention window.
Freshness mechanism	Fixed at creation - it does not add new members until you deliberately rebuild it.	Rolls continuously, aging visitors in and out as the retention window moves.
Funnel position	Cold prospecting - reach shaped like your best customers, not your actual customers.	Warm retargeting - people who already interacted with your site.
What weakens it	Seeding from a large, low-quality, or overly broad list.	Pixel or Conversions API signal loss undercounting real traffic.
Relationship between the two	Can be seeded by a Website Custom Audience, such as a lookalike of purchasers.	Independent and foundational - needs no other audience to exist.

What actually separates them.

Website Custom Audience membership is verifiable - each person generated a real event - while lookalike membership is probabilistic, and no member necessarily ever visited your site.

A lookalike is frequently built from a Website Custom Audience as its seed, which makes the website audience an upstream input rather than a competing choice.

Website Custom Audience size is capped by actual visitor volume within the retention window; lookalike size is capped by the percentage you choose against Meta's population, independent of how much traffic you have.

Website Custom Audiences decay with pixel or Conversions API signal loss, undercounting real behavior, while lookalike quality decays with a low-quality seed, modeling the wrong person confidently.

Website Custom Audiences sit in the warm retargeting layer of a funnel and lookalikes sit in the cold prospecting layer, so the two get judged on different metrics - retargeting CPA versus efficient cold reach.

Which one should you use?

Use Lookalike Audiences when

You have exhausted or want to extend beyond your retargeting pool and need cold prospecting reach.
You have a clean, value-weighted seed - like purchasers - and want Meta to find similar people at scale.
Your retargeting pool is too small to spend a meaningful prospecting budget against directly.
You are testing tighter (1-3%) versus looser (5-10%) match to trade precision for reach.

Use Website Custom Audiences when

You want to retarget people who actually visited specific pages or took specific actions on your site.
You need tiered exclusions - recent purchasers, cart abandoners - built on real behavior, not modeled resemblance.
Your Conversions API and pixel setup are solid enough that the resulting list reflects real traffic, not a signal-loss undercount.
You need a high-intent seed list to build a lookalike from later.

Common questions.

Can I build a lookalike from a website custom audience?

Yes, this is one of the most common seeding patterns. A Website Custom Audience of purchasers or high-intent visitors typically makes a stronger lookalike seed than a broad page-view list, because the resemblance model has a sharper signal to work from.

Why is my lookalike audience so much bigger than my website custom audience?

Because a lookalike's size comes from the percentage of a country you chose, not from the size of your source list. A 1% lookalike in a large country can be millions of people even if the seed that built it was only a few thousand website visitors.

Does losing pixel signal hurt lookalikes too?

Indirectly, yes. If a lookalike is seeded from a Website Custom Audience and that source is undercounting real visitors due to signal loss, the seed is thinner and less representative, which weakens the resulting model even though the lookalike itself has no pixel dependency.

Which one should I use for retargeting?

Website Custom Audiences, not lookalikes. A lookalike is built for prospecting - reaching people who resemble a source - while a Website Custom Audience is the actual list of people who visited, which is what retargeting requires.

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