Customer List Custom Audiences vs Website Custom Audiences: CRM Data or Site Behavior
In short: Both are Custom Audiences built from first-party data, but the data comes from opposite places. A Customer List Custom Audience is your own CRM records, hashed and uploaded, static until you refresh them yourself. A Website Custom Audience is built from pixel or Conversions API events, rolling continuously within a retention window as visitors age in and out with no manual work. The customer list can reach people who never touched your site at all - offline buyers, loyalty members - while the website audience can reach people you have never identified, as long as they triggered an event. Use the customer list for identity-based targeting and value-weighted seeding, and the website audience for behavior-based retargeting tiers that update themselves.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Customer List Custom Audiences
A Meta custom audience created by uploading hashed customer identifiers, matching your CRM records to Meta accounts for targeting, exclusion, or lookalike seeding.
You upload emails, phone numbers, and other identifiers, hashed before they leave your machine, and Meta matches what it can to user accounts. A value column unlocks value-based lookalikes. Match quality depends on how recent and complete the data is, and the list is static: last quarter's upload keeps excluding churned buyers and keeps missing everyone acquired since, unless you refresh it.
Full definitionWebsite 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 definitionSide by side.
The differences that actually change what happens in your account.
| Customer List Custom Audiences | Website Custom Audiences | |
|---|---|---|
| Data source | Your own CRM or offline records, uploaded and hashed. | Pixel or Conversions API events fired by actual site behavior. |
| Update mechanism | Static snapshot, changes only when you re-upload it. | Rolls continuously, ageing members in and out on the retention window automatically. |
| Who it can reach | Only people you already have contact data for. | Anyone whose browser or server sent a matching event, known or anonymous to you. |
| Segmentation basis | Whatever fields you upload - value, purchase tier, account status. | URL visited, event fired, time on site - all behavior-based. |
| Signal loss exposure | None - the identifiers come from you directly, no browser dependency. | Real - browser tracking restrictions undercount it unless Conversions API is solid. |
| Staleness risk | Silently keeps excluding churned buyers and missing new ones until refreshed. | Self-corrects continuously as the window rolls, no manual refresh needed. |
| Best for | Known-identity retargeting, suppression, and high-fidelity lookalike seeding. | Behavior-based retargeting tiers and intent-based lookalike seeding. |
What actually separates them.
A customer list only ever contains people you already had contact records for; a website custom audience can contain anonymous visitors you have never identified.
Customer list membership is frozen at upload time and goes stale without manual refresh, while website custom audience membership rolls continuously within its retention window with no action from you.
Customer list segmentation depends on whatever fields you upload - tier, value, product - while website custom audience segmentation depends on what your pixel or Conversions API actually tracked - URL, event, time on page.
Website custom audiences are exposed to browser signal loss and need Conversions API to stay accurate, while customer lists have no browser dependency since the identifiers come from you directly.
Both can seed a lookalike, but a customer list seed carries your value data natively while a website custom audience seed reflects real-time buying intent instead.
Which one should you use?
Use Customer List Custom Audiences when
- You want to exclude or target people using CRM records - loyalty members, past buyers, churned accounts - regardless of whether they have visited the site recently.
- You have offline conversions - in-store, phone, sales team - that never generate a pixel event.
- You want a value-weighted seed for a lookalike built on actual revenue, not inferred site behavior.
- Your website tracking is new or unreliable but your customer database is solid.
Use Website Custom Audiences when
- You want to retarget people based on what they did on your site recently, not who they are in your CRM.
- You need rolling, self-updating retargeting tiers - viewed product, added to cart, started checkout.
- You want to build a lookalike seed from high-intent behavior rather than a static customer roster.
- Your pixel and Conversions API are set up well enough that the resulting list reflects real traffic accurately.
Common questions.
Which is more accurate, a customer list or a website custom audience?
It depends what you mean by accurate. A customer list is accurate about identity but frozen at upload time, while a website custom audience is accurate about recent behavior but can undercount real traffic when browser signal is lost. Neither is universally more accurate - they measure different things.
Can I combine both in one ad set?
Yes. You can include one and exclude the other, or include both together, in the same ad set's audience controls. A common pattern is targeting a website custom audience of recent visitors while excluding a customer list of existing buyers.
Do I need to refresh my customer list the way a website audience refreshes itself?
Yes. A website custom audience ages members in and out automatically as its retention window rolls, but a customer list only updates when you manually re-export and re-upload it, so it needs a recurring refresh schedule to stay current.
Which is better for a lookalike seed?
It depends on your goal. A value-based customer list produces a revenue-weighted lookalike, while a website custom audience built from high-intent events like checkout produces an intent-weighted lookalike - test both if you can build a clean version of each.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- Advantage+ Audience vs Broad Targeting
- Broad Targeting vs Detailed Targeting
- Broad Targeting vs Interest Targeting
- Broad Targeting vs Custom Audiences
- Broad Targeting vs Lookalike Audiences
- Broad Targeting vs Website Custom Audiences
- Broad Targeting vs Customer List Custom Audiences
- Broad Targeting vs Engagement Custom Audiences