Skip to main content
Use this guide to turn a consented first-party list into a reviewed audience for Google Ads, Meta, or LinkedIn. It is for paid-ad matching, not outbound messaging.

​
Prerequisites

Before you enrich or upload anything, confirm:
  1. You may use the source list and any added identifiers for paid ads.
  2. The platform, geography, and ad account are in scope.
  3. You have a suppression list for current customers, employees, active opportunities, closed-lost accounts, and recent converters.
  4. You have a clear approval owner for paid enrichment and for audience upload.
Do not guess an ad account ID. Discover and confirm the account before a paid enrichment run or an upload.

​
Inspect the current account and upload contract

Search the connected workspace before you plan a live audience. These commands only inspect available tools; they do not enrich a list, create an audience, or upload members.
Record the account name, account ID, platform, permission state, and supported audience operations. Ask the approval owner to select the account when more than one is available.

​
Plan a baseline and an enriched audience

Ask your coding agent to produce the plan before it runs a paid layer:
The baseline uses first-party identifiers already in the source list. The enriched audience adds only approved identifiers. Keep both lists separate so you can measure the value of enrichment instead of assuming it.

​
Validate the upload data before approval

Before any upload, require the plan or Play to check that the audience is:
  • Suppressed against the approved exclusion list.
  • Deduplicated and free of empty identifier fields.
  • Clear about whether each identifier is raw or already hashed.
  • Free of double-hashed values.
  • Recorded with source-row lineage and the identifier source.
A valid file is not a completed audience. Do not call the audience successful until the platform accepts the upload and its status is read back.

​
Approve, upload, and read back status

After approval, create one clearly named audience per platform and per object: one baseline and one enriched audience. Capture the account name and ID, audience name and ID, uploaded rows, invalid rows, request IDs, and current status. Report platform match rate only when the platform exposes it. An accepted upload and a matched audience are different outcomes.

​
Platform guides

Google Ads

Create and sync Customer Match audiences.

Meta

Create and sync Custom Audiences.

LinkedIn

Create and sync Matched Audiences.

Choose where audience data lives

Start with a CSV, use the Database for durable processing, and write only approved outcomes to the CRM.