Audience Targeting

Broad Targeting vs Custom Audiences

In short: Both are inputs into how a Meta ad set finds people, but one relies on data Meta already holds about behavior and the other relies on data you bring. Broad targeting hands the algorithm nothing but age, gender, and location and lets conversion signal do the work. Custom audiences are built from something you own or generated on Meta - site visitors, a customer list, app activity, engagement - and let you target or exclude a known group directly. They are not really competitors: most working accounts run broad for prospecting and custom audiences for exclusion and retargeting in the same campaign structure. Choose broad to find new buyers, custom audiences to act on people you already know.

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

Custom Audiences

Meta audiences built from data you already own or activity people generated on Meta, such as site visitors, customer lists, app users, or video viewers.

You create them in Ads Manager from a source - pixel or Conversions API events, an uploaded list, app activity, or on-platform engagement - then target or exclude them in any ad set. They power both retargeting and lookalike seeds. Most accounts under-use exclusions, retargeting existing customers alongside prospects, and forget that website-based sources expire on whatever retention window was set.

Full definition

Side by side.

The differences that actually change what happens in your account.

	Broad Targeting	Custom Audiences
What data it runs on	Pixel and Conversions API events tied to the optimization goal, with no named group behind them.	A defined source you control - a pixel event window, an uploaded list, app activity, or on-platform engagement.
Primary job	Prospecting - finding new people who look likely to convert.	Retargeting, exclusion, or seeding a lookalike from people you already have a relationship with.
How you build it	You build nothing; the field stays empty.	You create it in Ads Manager from a source, name it, and set a size or retention parameter.
How fresh it stays	Always current - it reflects live conversion signal on every delivery.	Depends on the source: pixel-based audiences refresh continuously, uploaded lists stay static until you re-upload.
Typical pairing	Run alongside a custom-audience exclusion to keep it from wasting spend on existing customers.	Run alongside broad or interest targeting as the inclusion, or standing alone as an exclusion layer.
Failure mode	No exclusion added, so it keeps re-serving ads to existing customers who would have converted anyway.	Built once and never refreshed, so it keeps targeting or excluding people who no longer match reality.
What it costs you when wrong	Wasted spend on people who already converted, inflating cost per new customer.	A stale audience that either targets churned users or fails to exclude your newest buyers.

What actually separates them.

Broad targeting has no memory of who anyone is; custom audiences are built entirely from a remembered group, whether that memory comes from a pixel, an upload, or on-platform behavior.

Custom audiences can be used to exclude as easily as to include, and the exclusion use case has no equivalent inside broad targeting, which has no group to subtract.

Broad targeting's quality depends on ongoing conversion volume; a custom audience's quality depends on how the source was built and how recently it was refreshed.

A custom audience can seed a lookalike, extending reach to people who resemble it; broad targeting has no seed to extend from, since it starts from the full pool already.

The two are usually combined rather than chosen between: broad or interest-based inclusion targeting paired with a custom-audience exclusion is a common working structure.

Which one should you use?

Use Broad Targeting when

You are prospecting for new customers and have no group worth targeting directly.
You have enough conversion volume for the optimization event to learn without a head start.
You want the widest possible net for a top-of-funnel campaign with a broad product appeal.
You are testing whether your account's conversion signal alone beats every custom-audience hypothesis you have tried.

Use Custom Audiences when

You want to exclude existing customers or recent converters from a prospecting campaign.
You have site visitors, cart abandoners, or a customer list worth retargeting directly.
You want to seed a lookalike audience from your highest-value buyers rather than prospecting blind.
You are running a win-back campaign against people who lapsed, which requires a defined group to target.

Common questions.

Should I always exclude a custom audience even when I'm running broad targeting?

Usually yes. Excluding existing customers or recent purchasers is a hard rule that Advantage+ Audience respects even when the rest of the ad set is wide open, so it costs you nothing and prevents the algorithm from re-serving ads to people who would have converted regardless.

How stale can a custom audience get before it stops being useful?

It depends on the source. Pixel and Conversions API based audiences refresh as long as tracking is healthy, but an uploaded customer list is a snapshot - it keeps including people who churned since the upload and keeps missing everyone acquired after it, until you refresh the file.

Can a custom audience be used as an Advantage+ Audience suggestion instead of a hard include?

Yes, when used as an inclusion it functions the same way any other suggestion does - it gets priority early and the system can expand past it. When used as an exclusion, it still functions as a hard rule, which is the main reason many accounts keep at least one custom audience in play even while running broad.

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