Facebook Custom Audience Agency Account

A governed facebook custom audience agency account workflow answers four questions before data is uploaded: who collected it, why it may be used, which business controls it, and when the audience must be refreshed or removed.

Access to an ad account is not permission to upload any customer list available to the agency. Customer data, audience ownership, client separation, and offboarding must be designed as explicit controls.

Create a Data Authorization Record

For each source list, record:

Meta’ Customer List Custom Audiences Terms should be checked in their current form before use.

Separate Clients and Purposes

An agency should not combine lists from unrelated clients merely because it manages their accounts.

Use separate:

• Source files or pipelines
• Audience names and IDs
• Business ownership
• Access permissions
• Suppression lists
• Refresh schedules
• Offboarding records

If one list supports several approved purposes, document the scope. Do not create a general “agency audience pool” without a valid ownership and authorization model.

Use a Naming Standard

A useful name can include:

Client_Source_EventWindow_Market_Exclusions_Version

Example components:

• Client or business code
• Purchaser, qualified lead, subscriber, or suppression source
• Lookback window
• Country or region
• Inclusion/exclusion purpose
• Version date

Do not put sensitive customer information in audience names.

Validate the Source File

Before upload or automated sync:

• Remove unauthorized records.
• Apply current suppressions.
• Confirm field formats.
• Separate test records.
• Check duplicate treatment.
• Confirm market and collection window.
• Record row count before and after cleaning.
• Restrict access to the working file.
• Delete temporary exports under the approved schedule.

Do not email raw customer lists between operators.

Define Refresh Logic

Audiences can become stale when customers change status.

Document:

• Full replacement or incremental update
• Refresh frequency
• Source-system cutoff
• Opt-out latency
• Deleted customer handling
• Failed-sync alert
• Owner review
• Audience expiry or retirement

A campaign should not continue using an old list because the scheduled job failed silently.

Govern Exclusions

Common exclusion purposes include existing customers, recent converters, employees, test users, or people who should not receive a specific offer.

For each exclusion, verify:

• Business reason
• Source freshness
• Market applicability
• Campaign attachment
• Owner
• Review date

An exclusion is a control only when it is actually attached to the intended campaigns.

Control Lookalike Source Quality

If a source audience will support expansion, define the source outcome precisely.

Compare:

• All leads versus qualified leads
• All customers versus profitable customers
• First purchase versus repeat purchase
• Gross revenue versus net revenue
• Recent versus stale customers

The largest list is not automatically the best source. Use a business outcome that is reliable, sufficiently populated, and appropriate for the market.

Audit Access

Review who can:

• Export source data
• Configure integrations
• Create or edit audiences
• Use audiences in campaigns
• Share assets with partners
• Delete audiences

Use named people and formal partner permissions. The agency account access guide provides the wider access-control model.

Offboard Without Leaving Data Behind

When a client or provider relationship ends:

1. Stop new audience creation and syncs.
2. Identify every audience and source connection.
3. Export only the agreed operational record, not customer data without authorization.
4. Remove partner and person access.
5. Disable credentials and integrations.
6. Delete temporary source files.
7. Retain or delete audiences according to ownership and documented terms.
8. Confirm completion with the business owner.

Document Sharing and Dependency

When an audience is shared between businesses or depends on an integration owned by another party, record the provider, owner, recipient, permitted use, start date, review date, and termination condition.

Do not build a campaign portfolio around an audience that can disappear without notice. The operating plan should include what happens when sharing ends.

Monitor Audience Health

Track:

• Last successful refresh
• Source row count
• Valid-row rate
• Suppression application
• Unexpected size change
• Campaigns using the audience
• Owner and review date
• Integration errors

A sudden increase can be as suspicious as a decrease if a source filter or client boundary failed.

Create an Emergency Stop Process

If unauthorized data or the wrong client list is uploaded, stop campaign use, preserve the change record, notify the data owner, remove or correct the audience through the approved process, review access, and document affected campaigns and dates.

Build a Source-to-Audience Lineage

Map every audience back to the source table, filter, collection period, suppression step, transformation, upload or sync job, owner, and campaigns using it. If the source logic changes, create a new version instead of overwriting the old definition invisibly.

Test Suppression Latency

Use controlled records to measure the time from an opt-out, deletion, purchase, or status change in the source system to the relevant audience update. Document the acceptable window and escalation path when it is exceeded.

Control Manual Uploads

Manual lists should require approval, encrypted or restricted working storage, row-count evidence, validation, named uploader, and deletion of temporary files. Do not allow operators to download CRM exports to unmanaged personal devices.

Review Audience Overlap

Several approved audiences can still create campaign conflict. Review inclusion and exclusion logic across acquisition, retention, upsell, and suppression campaigns. Record which campaign has priority when a person qualifies for several groups.

Manage Audience Retirement

Retire audiences that have no active purpose, stale sources, expired authorization, or unclear ownership. Before deletion, confirm no campaign, experiment, or reporting process depends on the asset.

Questions for an External Provider

Ask who owns the audience, which Business Portfolio holds it, whether it can be shared, which people can use it, what source evidence is required, how updates occur, and what happens at termination. “Audience access included” is not an adequate ownership explanation.

Audience Governance Checklist

Treat Audiences as Controlled Business Assets

AdAccRun helps eligible advertisers evaluate account ownership, access, and connected-asset requirements. Customer-list authorization and data governance remain the responsibility of the businesses involved.

Speak with AdAccRun on Telegram about your business model, target markets, expected spend, Business Portfolio, and required audience structure.

Frequently Asked Questions

Can an Agency Reuse One Client’ Audience for Another Client?

Do not assume so. Data ownership, authorization, purpose, contractual terms, and platform requirements must support the use.

How Often Should an Audience Be Refreshed?

Use a schedule that reflects how quickly customer status and suppression data change, with alerts when a sync fails.

Who Should Own the Audience?

The structure should reflect the actual business relationship and exit plan. Document ownership and access before upload.