Meta Ads

Custom Audience

Also called Retargeting list, saved audience

A list of people you already have some connection with — customers, site visitors, video viewers — uploaded or matched for targeting.

Quick facts: Custom Audience

Category
Meta Ads
Also called
Retargeting list, saved audience
Level
Beginner
Affects
Retargeting reach, exclusions, lookalike quality
Where to see it
Meta Ads Manager (Audiences), Events Manager
In this article4
  1. How a custom audience works
  2. Why custom audiences matter
  3. Where custom audiences go wrong
  4. How to act on it

How a custom audience works

A custom audience is a list of people Meta has matched to accounts on its apps, and it can be built two ways. You upload identifiers you already hold — email addresses, phone numbers — which are hashed before they leave your computer, so Meta matches them against its own records without either side reading the other’s list. Or you let Meta assemble the list from activity it can already see: people who visited your website, watched a video, opened a lead form, messaged your page or engaged with your Instagram profile.

Activity-based audiences update themselves and carry a retention window, meaning the number of days somebody stays on the list after the action. Uploaded lists are frozen until you replace them. Very small audiences will not deliver at all, because Meta will not run ads against a group small enough to identify individuals.

Why custom audiences matter

They are the closest thing paid social has to a warm room. Someone who looked at a product page last week needs less persuading than a stranger, and results from these audiences usually cost less — which is also why they run out faster.

They do a second job that gets far less attention: exclusion. Taking existing customers out of prospecting stops you paying cold prices for people you already have, and taking recent buyers out of a sales campaign stops the irritation of being sold something somebody just bought. They are also the seed for a lookalike audience, so the quality of the seed decides the quality of everything built on top of it.

Where custom audiences go wrong

Uploading a list you have no permission to use is the serious one. A bought or scraped file breaks Meta’s terms and, in most countries a Nepali business sells into, the local privacy law as well.

The technical failure is thinner coverage than expected. Website audiences depend on the Meta pixel firing, and browsers block a growing share of that, so a recent-visitors list is smaller than your analytics implies. Audiences built from activity inside Meta’s own apps avoid that problem entirely, which makes them more dependable than people assume, especially for a business without a strong website.

The last mistake is letting a list rot. A customer file exported years ago and never refreshed describes a business that no longer exists.

How to act on it

Build the engagement audiences first, since they need nothing but activity you already have. Then add website audiences with retention windows that match how people genuinely buy from you — short for an impulse purchase, longer for a considered one — rather than accepting the default and forgetting it.

Keep the customer file current and permissioned, and upload phone numbers as well as email addresses where that is what your customers gave you, which in Nepal is most of them. Seed anything derived from your best segment rather than your longest list. And keep the number of audiences you actively use small: a folder of forty half-remembered lists is how retargeting becomes unmanageable.

Do and do not

Do

  • Build engagement audiences even without a website
  • Match retention windows to how people actually buy
  • Exclude existing customers from prospecting campaigns

Do not

  • Upload a list you have no permission for
  • Seed lookalikes from your longest, weakest list
  • Let a customer file sit unrefreshed for years

Questions people ask about this

Is a custom audience the same as retargeting?

Not quite. The custom audience is the list; retargeting is one thing you do with it. Most retargeting campaigns are built on custom audiences of recent visitors or engagers, but the same lists are also used to exclude people, to seed lookalikes, and to sell something different to existing customers. Treat the list as an ingredient, not a recipe.

Can I upload my customer phone numbers to Meta?

You can upload contact details you collected lawfully and have permission to use for marketing. They are hashed before leaving your computer, so Meta never receives readable numbers. Bought or scraped lists are not acceptable, whatever the seller claims. If you are unsure whether your consent covers advertising, settle that before uploading rather than afterwards.

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

Because the two are counted differently. The audience only includes visits the pixel managed to record and match to a Meta account, and browser restrictions, blockers and refused consent all remove people from that count. Analytics uses its own rules and its own definition of a visit. Expect the audience to be the smaller of the two.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.