Key takeaways
- Audience matching associates submitted identifiers with identities recognized by a destination platform.
- Uploaded, accepted, matched and usable audience counts describe different stages.
- Use permitted identifiers and keep exclusions synchronized when membership changes.
Overview
A platform may require specific identifier formats, hashing, collection permissions and minimum audience sizes. Upload success does not mean every record matched or that an audience is ready to serve. Matching and activation can be asynchronous. Follow the destination’s current policies and keep suppression and removal behavior aligned with the original purpose and permissions.
How it works
Confirm eligibility, permitted use and the platform’s required identifiers.
Normalize and prepare the data exactly as the destination specifies.
Review the upload, match status and final audience eligibility before activation.
Understand what the destination can match
A destination may accept email addresses, phone numbers or other specified identifiers under its product rules. Normalize them according to the documented format and map them to the intended person or account. A company list with domains alone is not interchangeable with a person-based audience product that expects customer identifiers.
Check eligibility and permitted data use before activation. Google Customer Match, for example, describes using customer information to connect with recognized users across supported Google surfaces. The current product documentation and policies determine the available identifiers and use conditions. A provider’s ability to return an identifier does not establish permission to upload it elsewhere.
| Stage | Meaning | What it does not prove |
|---|---|---|
| Submitted | Records sent to the platform | Valid format or permitted use |
| Accepted | Records passed the relevant upload checks | A recognized destination identity |
| Matched | Identifiers associated with platform identities | Immediate campaign eligibility or reach |
| Usable or reachable | Audience meets applicable delivery conditions | Every matched person will see an ad |
Source material: Google Ads — About Customer Match ↓
Treat hashing as a format, not universal permission
Some destinations require identifiers to be hashed under a documented method. Hashing can be part of the transfer design, but it does not make collection context or permitted use irrelevant. Apply the platform’s normalization and hashing sequence exactly where required; different input formatting can create a different hash and reduce matching.
Keep suppression and deletion behavior connected to the audience lifecycle. If someone becomes ineligible or withdraws a relevant preference, a recurring sync should remove or exclude the identifier according to the destination’s supported process and applicable rules. A one-time upload without a removal plan can leave outdated membership active.
Diagnose match rate without overstating reach
In an illustrative upload, 1,000 submitted records become 900 accepted records and 600 matched identities. Match rate is 60% of submitted or about 66.7% of accepted records, depending on the stated denominator. Neither figure means 600 people will receive an impression. Campaign settings, platform eligibility and delivery conditions still matter.
Review formatting failures, duplicate identifiers and coverage by source before buying more data. A low match rate may reflect a destination’s user population rather than incorrect source records. Compare equivalent cohorts and product definitions, and preserve the sync receipt so the team can distinguish a successful upload from an audience that is ready for its intended use.
What this looks like in practice
A team prepares an eligible customer exclusion list for an ad platform. The upload is accepted, then processed; the final matched audience is smaller than the source list because some identifiers are not recognized.
Examples explain the concept; they are not reported customer results.What to check
Separate uploaded, accepted, matched and active counts. Inspect denominator definitions, rejection reasons and synchronization of removals.
Common mistake
Treating hashed personal identifiers as automatically anonymous or interpreting a successful upload as approval to activate any list.
Audience matching vs. Entity resolution
Entity resolution establishes identity relationships across records. Audience matching applies destination-specific identity matching and policy rules to build an eligible campaign audience.
Read the Entity resolution definition →Questions answered
What is Audience matching?
Audience matching connects eligible customer or prospect identifiers with records recognized by an advertising or engagement platform so a permitted audience can be included or excluded in campaigns.
Does hashing remove permission requirements?
No. Hashing changes the representation used for matching; it does not independently authorize collection or upload. Follow the platform and applicable requirements.
Why is match rate lower than upload acceptance?
Acceptance checks file or record eligibility, while matching asks whether the platform recognizes the identifiers. Audience availability can add further policy or size conditions.
Does hashing make customer identifiers anonymous?
Hashing is not a blanket guarantee of anonymity, especially when a platform can match the values to known users. Treat the identifiers under the applicable data and platform requirements. Use the documented transfer method while preserving the purpose, permissions and lifecycle controls.
Why can an accepted audience still be unavailable for a campaign?
Acceptance, matching and campaign eligibility are separate checks. The destination may apply size, policy, account or surface-specific requirements. Inspect the platform’s current status and documentation instead of assuming a successful upload response means the audience is immediately usable everywhere.
References and further reading
Primary documentation and source material for this topic. Sources checked September 14, 2026; provider requirements can change.
- About Customer Match ↗Google Ads
- Data minimisation ↗UK Information Commissioner’s Office
UK-specific guidance. The ICO flags this page as under review following legislative changes.
Continue reading on the blog
Explore all articles and guides →Put the concept to work.
Explore the relevant AstroFabric workflow and see how the pieces connect.
Help keep this guide useful. Suggest a correction or browse the full glossary.