Audience match rate is not the audience you can reach

A customer list reports a high match rate, but the campaign reaches far fewer people than expected. The upload may be working exactly as designed.

Matching is one stage between a source list and advertising delivery. A matched record still needs to be eligible for the intended use, available in the relevant environment, and reachable under the campaign’s settings.

Draw the stages separately

Start with source records, then accepted records, matched records or identities, eligible audience size, and delivered reach. Confirm the unit at each stage.

A list of 10,000 rows does not necessarily represent 10,000 distinct people. Duplicate contacts, multiple identifiers, and invalid records can change the relationship between rows and audience estimates.

Suppose 9,000 rows are accepted and a platform reports an 80% match rate. Do not automatically call that 7,200 reachable customers unless the platform defines both the denominator and identity in a way that supports that calculation.

Check formatting before changing strategy

Validate the supported fields, normalization, file structure, and error report using the platform’s instructions. Preserve the source record count and exclusion reasons.

Google’s Customer Match guidance discusses formatting and the use of supported customer information. Follow the requirements for the chosen integration and use only data approved for that purpose.

Adding more fields is not a reason to send information the organization is not authorized to share. Hashing does not change that decision.

Explain eligibility separately from matching

Ask whether the audience is usable for the selected campaign type, market, account, and inventory. Review minimum size rules and processing status using current platform documentation.

Next inspect the campaign’s own constraints. A list can be usable while additional geography, device, schedule, or frequency settings leave only a small delivery opportunity.

An audience expansion feature can also change who receives the ads. Confirm whether the list is a strict targeting boundary, an input to optimization, or an observation segment.

Audit freshness and removals

A successful initial upload is not a complete audience process. Define how additions, corrections, expired records, and removals reach the destination.

Keep the last completed update time visible. A large audience can look healthy while containing customers who should no longer be included for the specific campaign.

Test the integration with approved records and inspect the resulting status. Avoid expecting an individual customer to see an ad on demand as proof that matching works.

Report what is known

A useful handoff might say: “The file was accepted, matching completed, and the audience is eligible. Delivery remains limited after geography and frequency controls.”

That description points to a different next step from “half the file was rejected.” Keep the evidence for each stage so troubleshooting does not restart at the upload every time.

For exposure questions after delivery begins, use the frequency-cap guide. Match rate is a data-processing measure; the campaign still needs its own evidence of reach and useful outcomes.