A custom audience is a group of people you build in Meta Ads Manager from your own sources, such as visitors to your website, people on your customer list or people who have watched your videos, so you can show ads to them or keep ads away from them. Unlike interest targeting, it starts from people who have already had some contact with your business.
How a custom audience works
You choose a source and a rule, and Meta matches the people that rule describes to Facebook and Instagram accounts. The main sources are:
- Website activity. People recorded by your Meta Pixel or the Conversions API, filtered by page, event or time on site. A website custom audience can look back up to 180 days.
- Customer lists. A file of email addresses or phone numbers from your CRM. Ads Manager normalises and hashes each value before upload, and Meta compares the hashes with its own records.
- App activity. Users of your app who took a specific action, reported through the Meta SDK or an app attribution partner.
- Offline activity. People who bought in a shop or over the phone, sent to Meta as offline events.
- Meta sources. People who engaged with your Facebook Page, Instagram account, videos, lead forms or events.
Not everyone matches. A list of 2,000 customer emails can produce a much smaller audience, because some people use a different address on Facebook and some have no account at all. Meta shows the matched size as a range, and an audience has to reach a minimum size before it will deliver.
Once built, the audience maintains itself. A rule such as “visited the pricing page in the last 30 days” adds new visitors each day and drops people when their 30 days are up.
Why it matters
People who already know you are usually cheaper to convert than strangers. A physiotherapy clinic in Clapham can show a booking reminder to people who viewed its treatments page but did not book; an online shop can stop showing a first-order discount to people who have already bought. Custom audiences make both possible, and they are also the seed for a lookalike audience, where Meta looks for new people who resemble your best customers.
They also involve personal data. Uploading a customer list to Meta, or tracking visitors with the pixel, falls under UK GDPR and PECR. You need a lawful basis for sharing the list, a privacy notice that tells customers it happens, and cookie consent before the pixel fires for UK visitors. The ICO has been clear that marketing cookies need opt-in consent, so website audiences are usually smaller than your raw traffic suggests.
Common mistakes
- Uploading a list with no lawful basis. A list collected to deliver orders is not automatically available for advertising. Check what your privacy notice says first, and leave out anyone who has opted out of marketing.
- Building audiences too narrow to deliver. “Viewed the checkout in the last three days” may hold a few dozen people on a small site. Widen the window or combine sources.
- Forgetting exclusions. Showing acquisition ads to existing customers wastes money and irritates them. Use audience exclusions to keep buyers out of prospecting campaigns.
- Letting customer lists go stale. A list uploaded once, two years ago, no longer reflects who your customers are. Refresh it regularly or connect your CRM so it updates.
- Assuming the audience is a hard boundary. With Advantage+ audience switched on, Meta can treat a custom audience as a suggestion and reach beyond it. If you need a strict limit, check the setting.
How to act on it
Start with three audiences most businesses can build in an afternoon: everyone who visited your site in the last 180 days, people who reached a high-intent page such as pricing or contact in the last 30 days, and current customers from a list. Name each one with its source and window, so you can still tell them apart in six months.
Use the high-intent group for retargeting campaigns that bring visitors back to finish what they started, and the customer list as an exclusion on prospecting. Then check your consent set-up: if the cookie banner holds the pixel back until consent, make sure the Conversions API handles consented events properly so your audiences are not starved. Look at audience sizes monthly. A sudden drop usually means tracking has broken, not that interest has dried up.