Build and audit a Facebook Custom Audience

By Maestro · Updated October 6, 2026

A Facebook Custom Audience is a group Meta builds from one eligible source. Create it in Meta, then verify the source, permission, status, exclusions and planned use before another operator relies on it.

An evidence reference names a dated receipt. The fingerprint locks the exact register revision an operator approved.

Creating the audience is the easy part. The harder part is proving what the audience contains, whether you may use the source, when it last refreshed, who should be excluded and what the ad set will actually do with it.

Use the workspace below to choose one source. It will give you one of three results:

• Ready for operator review: the source, permission, audience state, exclusions and use are supported by current evidence.
• Repair: the intended use is possible, but the description, suppression or account setup conflicts with the evidence.
• Hold: a required fact is missing or failed. The result names the owner and the exact evidence to request.

The workspace does not upload a list, create an audience or change an ad set.

Choose the source first

The source changes the setup and the evidence you need.

Meta's Custom Audience overview separates advertiser sources from activity on Meta. The labels and available sources can vary. Check the source chooser in the account before writing the plan.

If the source is unclear, stop there. “Website visitors,” “CRM leads” and “engaged people” are not complete audience rules.

App activity path

1. Verify the app, SDK or dataset and the intended event in Events Manager.
2. Open Audiences, choose Create audience, choose Custom Audience, then choose the available app-activity source.
3. Select the app and define the event, inclusion logic, retention and exclusions exposed in the current account.
4. Name and create the audience.
5. Save the source, rule, creation receipt, first reliable event observation and current status. If the app or event is absent from the chooser, Hold instead of substituting another source.

Offline activity path

1. Verify the selected offline dataset and a current accepted-event receipt.
2. Apply eligibility, data-use and suppression rules before events are sent.
3. Open Audiences, choose Create audience, choose Custom Audience, then choose the available offline-activity source.
4. Select the source, define the event rule and retention, add the required exclusions, then name and create the audience.
5. Save submitted and processed counts separately with the current native status receipt. An accepted event count is not a matched-person count.

Meta changes source labels and may not expose every route in every account. If the named source is not present, capture that observation and Hold. Do not rewrite the plan around a source you did not verify.

What each status proves

Teams often treat these as one number. They are not.

1. Source rows or events tell you what the source system observed.
2. Eligible inputs apply your permission, quality, date and exclusion rules before anything is sent.
3. Uploaded or submitted inputs tell you what the connector or operator attempted to send.
4. Processed inputs tell you what the platform accepted for processing, when that receipt exists.
5. Match evidence is the platform's account of recognized records. An upload count is not a match count.
6. Estimated audience size is a planning estimate. A hidden estimate is Unknown, not zero.
7. Ready is a platform status. It does not prove exclusive targeting, delivery or qualified reach.
8. Delivered reach exists only after an eligible ad set delivers and the native report records it.
9. Business outcomes belong to the later campaign and CRM cohort. They cannot be filled from audience status.

That separation prevents a common mistake: “We uploaded 1,000 contacts, so the audience has 1,000 people.” Meta still needs to process and attempt to match the eligible identifiers. The native audience estimate and eventual delivered reach are later facts.

Build a website Custom Audience

Meta's website-audience instructions describe a Pixel source, event or URL criteria, Any or All logic, retention and inclusion or exclusion rules. Its current guidance also says a website audience starts populating when it is created. It does not backfill earlier visitors.

Create the website audience in this order:

1. Verify the correct Pixel or dataset and the event history in Events Manager.
2. Open Audiences, choose Create audience, choose Custom Audience, then choose Website.
3. Select the verified source.
4. Set the Any or All logic, event or URL rule and retention window.
5. Add the event-level exclusions required by the rule.
6. Name and create the audience.
7. Record the creation time, then wait for the current status instead of assuming earlier traffic will backfill.
8. Save a dated source receipt and the first reliable event date with the account-only setup evidence.

Keep these fields in that account-only setup receipt before another operator relies on the audience:

1. Pixel or dataset reference
2. Exact event or URL rule
3. Any or All logic
4. Audience creation date
5. First reliable event date
6. Retention window
7. Event-level exclusions
8. Current status and observation date
9. Source owner
10. Receipt location

The portable register keeps the redacted source reference, combined inclusion rule, retention, owner and dated lifecycle evidence. It does not duplicate the organization, ad-account ID or account-only creation receipt.

The creation date matters. A team can have months of website traffic and still create an empty new audience if earlier activity is not eligible to backfill.

Watch the website setup controls

TJ Murray's February 2026 walkthrough shows the path through Audiences, Custom Audience, Website, Pixel and event selection at 00:06. At 00:41, he adds an exclusion. At 01:12, he uses the retention control.

The walkthrough shows his account and an ecommerce example. The 180-day value he selects is not a universal maximum or a recommendation for your B2B cycle. Use the video to locate the decisions. Use current Meta documentation and your account receipt to describe the actual setup.

Build a customer-list Custom Audience

A customer-list audience begins with the dataset, not the CSV.

Write the eligibility rule first. For example:

Include permission-reviewed evaluation contacts with a valid company email observed by 1 October 2026. Exclude current customers, open opportunities, opted-out contacts and records without an approved advertising-use basis.

Then save counts at each step:

The Harbor example is fictional. It shows why 1,040 uploaded must not become 1,040 matched.

Meta's customer-list Help describes hashing and matching. Meta's Customer List Custom Audiences Terms put the responsibility for applicable rights, permissions or lawful basis on the advertiser and require later opt-outs to be removed where the terms apply.

Hashing changes how identifiers are transferred and compared. It does not give you permission to use a dataset.

Create the customer-list audience in this order:

1. Apply the written eligibility and suppression rules before export.
2. Prepare only Meta-supported identifiers for eligible records. Keep the raw file outside this portable register.
3. Open Audiences, choose Create audience, choose Custom Audience, then choose Customer list.
4. Select the available upload or partner-connection path and confirm that you have the required rights and permissions.
5. Upload the file or connect the source, map the identifier columns and resolve reported mapping errors.
6. Name and create the audience.
7. Save the uploaded and processed counts separately. Wait for the current estimate and Ready status rather than treating the upload count as a match count.
8. Save the native status receipt, suppression refresh receipt and later-removal process.

In the fictional Harbor build, Revenue Operations starts with 1,260 evaluation contacts. The written rule removes customers, open opportunities, opt-outs and records without an approved advertising-use basis, leaving 1,040 eligible inputs. The operator uploads those 1,040 records through Customer list, maps the supported identifier columns and names the audience “Harbor Grid: permission-reviewed evaluation contacts.” Meta shows the audience as Populating, so the register keeps processed, matched and estimate Unknown. It also returns Hold because the permission decision receipt is still missing. The upload completed; the audience is not ready for use.

Your register should name:

• dataset owner;
• eligibility rule and cutoff;
• permission reviewer and evidence reference;
• upload or sync method;
• later opt-out removal process;
• suppression owner;
• last successful refresh;
• failed-refresh handling; and
• a reference to the native audience receipt.

Do not place emails, phone numbers or other raw identifiers in the portable register.

Build a Meta engagement audience

An engagement audience needs an exact action. “People who engaged” is too broad.

Name the Page or Instagram account, video, form, event or other eligible surface. Then name the action: watched 50% of a selected video, opened a selected form, submitted that form, messaged the Page or another option shown in the account.

Create it in this order:

1. Open Audiences, choose Create audience, choose Custom Audience, then choose the available Meta engagement source.
2. Select the exact Page, Instagram account, video, form, event or other object.
3. Select the exact action and retention window. Add exclusions for people who already took the later action when the sequence requires it.
4. Name and create the audience.
5. Save the selected object, action, retention, creation receipt and current status. Keep the later ad-set inclusion mode and exclusions as a separate receipt.

For a lead-form audience, “opened but did not submit” and “submitted” describe different groups. They may need different exclusions and a different next step.

Meta engagement happens on Meta's surfaces, but that does not remove the need to check source identity, available history, retention, status, exclusions and planned use.

Ready does not mean exclusive delivery

A Custom Audience can be Ready and still be used as an Advantage+ suggestion.

Meta's current controls guidance separates audience controls from suggestions. It lists Custom Audience exclusions separately. An included Custom Audience may guide delivery without creating an exclusive boundary.

Save a dated ad-set receipt that answers:

1. Is the included Custom Audience a hard control or a suggestion?
2. Is a further-limit option available for this campaign?
3. Is “Use as a suggestion” selected?
4. Which Custom Audiences are excluded?
5. Which campaign type, objective and account produced this screen?

If the included audience is a suggestion, say so. Do not call the delivery “retargeting only.”

Ben Heath's March 2026 walkthrough shows a Custom Audience inside the suggestion area at 08:35. At 12:15, he demonstrates a further-limit path and changes the suggestion setting in his account.

The video is a dated creator demonstration. It does not establish which controls your account or campaign exposes.

Exclusions only work when their sources are current

An exclusion name can look correct while its source is stale.

For each suppression audience, record:

• group being suppressed;
• source system and rule;
• last successful refresh;
• expected refresh method;
• owner;
• failure state;
• applicable later-removal process; and
• current native receipt.

Common B2B suppression candidates include customers, open opportunities, active sales conversations, completed next actions and opted-out contacts. These are planning examples. They are not universal Meta defaults.

Fictional Hold: Ready audience, stale suppression

Cedar Dispatch has a fictional customer-list audience marked Ready. Its customer and opt-out suppression sync failed six days before review.

The result is Hold. Ready proves the audience's platform status. It does not prove the exclusions include the six days of later changes.

The repair request is plain:

RevOps: repair the customer and opt-out suppression sync. Save the new successful-run receipt and the audience refresh receipt. Then ask the operator to review a new record revision.

Diagnose a small or unavailable audience

Do not jump from “small” to “the Pixel is broken.” Work through the states in order.

1. Source identity: Is this the intended Pixel, app, Page, form, video or list?
2. Source history: Did qualifying activity occur after the audience could start populating?
3. Rule: Does the selected event, URL or action match the intended behavior?
4. Retention: Is the window valid and compatible with the available history?
5. Eligibility: Did permission, date, quality or suppression rules remove the inputs?
6. Upload or sync: Did the source operation complete, fail or remain pending?
7. Processing or match: What does the native receipt actually report?
8. Estimate: Is it a number, hidden, unavailable or still populating?
9. Status: Is the audience Ready, Populating, unavailable or in another current state?

Meta's size troubleshooting page notes that Ready status and audience estimates do not always appear together. Preserve the actual state. Do not convert a hidden estimate into zero.

Fictional known-zero case

Maple Ledger starts with 18 fictional renewal records. Its current permission, date and suppression rules leave zero eligible inputs.

That is a known zero, not missing data.

The correct result is Hold with a reason: no eligible records remain under the current source rule. The next action is to review the source definition or choose another supported source. Uploading an empty file would not solve the problem.

Keep one audience register

The audience register should be the object another operator reviews. It should contain references and counts, not person-level data.

Source and rule

• source family;
• source asset or dataset reference;
• inclusion rule;
• retention window;
• observation date;
• source owner; and
• dated lifecycle evidence references.

Keep the organization, ad-account reference, creation time and first reliable event date in the account-only setup receipt. The portable register uses redacted references and contains no account ID.

Permission and removals

• dataset provenance;
• permission reviewer;
• evidence reference;
• applicable notice or consent review;
• later opt-out removal process; and
• unresolved questions.

Population states

• source rows or events;
• eligible inputs;
• uploaded or submitted inputs;
• processed inputs;
• match evidence;
• estimate;
• platform status; and
• delivered reach, if a later eligible campaign exists.

Exclusions and refresh

• each suppression group;
• last successful refresh;
• owner;
• failure state; and
• suppression receipt;
• the same groups in the planned delivery exclusions; and
• current delivery-mode receipt.

Planned use

• control or suggestion;
• current ad-set receipt;
• separate exclusions;
• account and campaign context; and
• what remains Unknown.

Review

• Ready, Hold or Repair;
• reason codes;
• plain next action;
• exact evidence requests;
• assigned owners;
• reviewer and review time;
• evidence locations; and
• record fingerprint.

Any edit to source identity, permission, population evidence, suppression or inclusion mode should reopen review.

What the downloads do

• Blank audience register: collect one source without raw identifiers.
• Worked fictional registers: compare Ready, pending match, suggestion, stale suppression and known-zero states.
• Build prompt: turn supplied facts into a complete register. Missing facts remain requests.
• Review prompt: evaluate a completed register against the same predicates.
• Execution bundle: run the reference evaluator and verify JSON or Markdown exports in a clean directory.

The prompts cannot decide whether a dataset is lawful, query your ad account or invent native receipts. They preserve what you provide and tell you what is missing.

Common mistakes

Treating uploads as matches

Keep source, eligible, upload, processed and match states separate.

Calling a hidden estimate zero

Hidden, unavailable and still populating are Unknown states. A measured zero is different.

Treating Ready as delivered

Ready is not reach, frequency, qualified pipeline or performance.

Using hashing as permission

Hashing is part of processing. Permission needs its own evidence.

Forgetting later removals

A list can be permitted when first uploaded and become stale when later opt-outs are not removed.

Assuming included means exclusive

Check whether the included Custom Audience is a control or an Advantage+ suggestion. Check exclusions separately.

Saving raw identifiers in the handoff

Use secure source-system references, counts and receipts. Keep person-level data out of the portable register.

Related Maestro resources

• Use the Facebook retargeting guide after the audience evidence is ready and you need the source-to-message plan.
• Use the Facebook lookalike audience guide to decide whether a source population is fit for a prospecting seed.
• Use the Facebook lead ads guide to design a native form and prove CRM delivery.
• Use the Facebook Ads audit to diagnose an active campaign from delivery through CRM outcomes.
• Use the Facebook Ads for B2B guide for the broader campaign decision.

Sources

• Meta: About custom audiences
• Meta: About Customer List Custom Audiences
• Meta: Create a website custom audience
• Meta: Troubleshoot Custom Audience size
• Meta: Advantage+ audience controls and suggestions
• Meta: Customer List Custom Audiences Terms
• Meta: Business Tools Terms