Broad Targeting vs Customer List Custom Audiences
In short: Both can inform who a Meta ad set reaches, but one draws on data your own CRM already holds and the other draws on live platform signal. Customer list custom audiences are built by uploading hashed identifiers - emails, phone numbers - which Meta matches to user accounts for targeting, exclusion, or value-based lookalike seeding. Broad targeting has no upload at all; it lets pixel and Conversions API events guide delivery in real time. A customer list is only as good as its match rate and its freshness, while broad targeting is only as good as your conversion volume. Use a customer list when you have offline data worth activating; use broad when your online conversion signal already tells the same story.
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 definitionCustomer 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 definitionSide by side.
The differences that actually change what happens in your account.
| Broad Targeting | Customer List Custom Audiences | |
|---|---|---|
| Data source | Live pixel and Conversions API events tied to the optimization goal. | Offline CRM records - emails, phone numbers, or other identifiers you already hold. |
| How it enters Meta | It never enters as a list; there is nothing to upload. | Hashed before it leaves your system, then uploaded and matched against Meta user accounts. |
| What determines quality | Volume and cleanliness of the optimization event. | Match rate, which depends on how recent, complete, and accurate the underlying CRM data is. |
| Freshness | Always current - reacts to live conversions. | Static between uploads; churned customers stay in and new customers stay out until you refresh the file. |
| Value-based use | Only if the optimization event itself carries a value. | A value column unlocks value-based lookalikes seeded from your highest-value customers specifically. |
| Typical role | Prospecting. | Exclusion of existing customers, direct retargeting to a CRM segment, or a lookalike seed. |
| Failure mode | Not enough conversion volume for delivery to stabilize. | Uploaded once and never refreshed, so it keeps excluding churned buyers and missing recent ones. |
What actually separates them.
A customer list is built from data you already own offline; broad targeting has no offline component and works entirely from what happens on Meta's own conversion signal.
Customer list quality is bounded by match rate - how well Meta can tie a hashed record to a real account - while broad targeting's quality is bounded by conversion volume.
A customer list stays static until re-uploaded, so it drifts out of date between refreshes, whereas broad targeting has no staleness problem since it only ever looks at current signal.
A value column on a customer list enables value-based lookalike seeding, something broad targeting cannot replicate unless the optimization event itself is a value-based conversion.
Customer lists are commonly used as an exclusion layer even inside an otherwise broad ad set, since excluding a hashed match still functions as a hard rule under Advantage+ Audience.
Which one should you use?
Use Broad Targeting when
- You have no CRM data worth uploading, or your existing customer list has a poor match rate.
- You are prospecting for new customers rather than acting on people you already know.
- You have enough online conversion volume that offline data would add little the algorithm doesn't already see.
- You want delivery that reflects current buyer behavior rather than a snapshot of past customers.
Use Customer List Custom Audiences when
- You have a clean, recent CRM export worth activating for retargeting or exclusion.
- You want to run a win-back campaign against lapsed customers identified in your own records.
- You have revenue or lifetime-value data per customer and want a lookalike seeded from your best buyers specifically.
- You need to exclude existing customers from a prospecting push and your CRM is more complete than your pixel data.
Common questions.
Why is my customer list match rate lower than expected?
Match rate depends on how many identifiers you include per record and how closely they match the data associated with each Meta account - stale email addresses, minimal formatting cleanup, or a single identifier per row all lower it. Including multiple identifiers per customer, like email, phone, and name, generally improves the match rate over a single field.
How often should I refresh a customer list?
Often enough that it reflects who is actually still a customer and who has churned - a list that hasn't been refreshed in months is excluding people who left long ago and missing everyone acquired since. Automating the export on a recurring schedule keeps it closer to reality than a one-time upload.
Can a customer list be used for both targeting and exclusion at once?
Not in the same ad set for the same purpose, but a common structure is excluding a customer list in a prospecting campaign while including that same or a related list in a separate retargeting or win-back campaign. The upload itself is reusable across as many ad sets as you need.
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 Engagement Custom Audiences
- Broad Targeting vs Saved Audiences