Custom Audiences

A custom audience is a group of people you define in Meta Ads Manager from a source of your own, instead of from Meta's interest and demographic categories. Meta's Marketing API guide lists the main types: customer file audiences built from uploaded customer data, website audiences built from people who visited your site or took actions, mobile app audiences, offline audiences from actions such as store visits or customer service calls, and lookalike audiences built from an existing audience. Canvas engagement audiences are also listed. You build them in the Audiences section of Ads Manager, then select them as an included or excluded audience when you set up an ad set. Think of a custom audience as a saved list of people that Meta keeps matching against its users.

Each type works through a different source. A website audience depends on the Meta Pixel or the Conversions API passing events from your site, so the audience is only as complete as your tracking. A customer file audience depends on the identifiers you upload, which Meta matches to accounts. App audiences depend on your app's events. Because the data is yours, Meta's documentation says the advertiser owns and manages it, and you must accept the Custom Audience Terms for the business before you can use these audiences. Without acceptance the API returns an error that the terms are not accepted. Matching and processing are not instant, since updates to customer file audiences can take up to 24 hours. Check the audience's status and size in Ads Manager before you use it, since an empty or tiny audience delivers poorly.

Custom audiences interact with nearly everything else. You can target them for retargeting, exclude them to avoid showing prospecting ads to existing buyers, or use them as the seed for a lookalike audience. Their size changes your delivery: a small audience raises frequency quickly and costs more per result. Meta's Marketing API limits are generous but real, with up to 500 standard customer file audiences and 10,000 website audiences per ad account. Name your audiences with the source and date, so you can tell a fresh list from an old one at a glance. Test one new audience at a time against your current best, so you can tell which source actually improves results.

Typical mistakes start with exclusions. Many accounts retarget existing customers alongside new prospects, paying to advertise to people who have already bought. Others build an audience once and forget that its source goes stale: a list does not update itself, and a website audience only includes visitors within the retention window you set. Another error is building audiences too small to deliver. Also note Meta's recent policy: from September 2, 2025, audiences that suggest health conditions or financial status are flagged and cannot be used to run campaigns. Customer file audiences unused in any active ad set for more than two years are flagged for deletion. If you rely on website audiences, test that your tracking fires on the key pages each month.

Start with the audiences that pay for themselves: past purchasers as an exclusion on prospecting, and recent website visitors who did not convert as a retargeting group. Check the size of each in Ads Manager, and check when the source last updated. Then create a lookalike of your best customers and test it against broad targeting with the same creative. Review your active audiences monthly: remove ones you no longer use, refresh lists, and confirm that tracking still feeds the website audiences. This week, open your ad sets and confirm that your buyers are excluded from every prospecting ad set. Keep an audience inventory in a simple sheet, with the source, size, owner, and last update.