The Match Rate Your Onboarding Vendor Reports Is Measured Against a Denominator You Did Not Choose

When a CRM onboarding vendor hands you a match rate, the number feels straightforward: you uploaded a file, they found a percentage of those records in addressable inventory. The question most buyers do not think to ask is what the denominator of that percentage actually contains, and who decided what belongs in it.

The answer shapes every conclusion you draw from the number.

What the Denominator Actually Measures

A match rate is a fraction. The numerator is the count of records from your file that the vendor resolved to at least one addressable identifier. The denominator is the count of records the vendor considered eligible for matching.

That denominator is not always your full file. Vendors routinely remove records before the match process begins. Common pre-match removals include records with malformed email addresses, records flagged as duplicates within your upload, records associated with geographic regions the vendor's graph does not cover, and records that do not meet minimum data field requirements for the matching logic the vendor uses.

If your file contained 200,000 records and the vendor quietly removed 40,000 before starting the match, a reported 70% match rate describes 70% of the remaining 160,000, not 70% of your original file. The effective match rate against your full file is closer to 56%. Both numbers can be reported honestly depending on how the vendor defines the denominator, and buyers often receive only one of them.

Why Different Vendors Return Different Rates From the Same File

This is the situation that confuses buyers most during vendor evaluations. You send the same CRM export to two onboarding providers. One returns a 72% match rate. The other returns a 58% match rate. The natural interpretation is that the first vendor has a better graph.

That may be true, but it is not the only explanation. The vendors may be measuring against different denominators. The first vendor may apply generous pre-match filtering that removes your hardest-to-match records before calculating the rate, producing a cleaner numerator-to-denominator ratio. The second vendor may count every record you uploaded, including records in geographic areas or data states that are genuinely difficult to resolve.

A vendor with a nominally lower match rate but a stricter denominator definition may actually be resolving a larger absolute number of your customers into addressable inventory. The rate you compare is a ratio. The reach you buy is an absolute count.

The Pre-Match Removal Categories Worth Asking About

Before accepting a match rate as a campaign planning input, it is worth asking your onboarding vendor to describe what categories of records were excluded before matching began. Useful questions include:

Deduplication logic. If your CRM file contains multiple records for the same person under different email addresses, some vendors deduplicate before matching and count that consolidated record once. Others match each record independently and then deduplicate the output. These approaches can produce meaningfully different reported rates from the same underlying file.

Geographic scope. Identity graphs have stronger coverage in some markets than others. If your vendor pre-filters records to the geographies where their graph is densest, match rates will look higher than they would against your full file, including customers in lower-coverage regions.

Email validity thresholds. Some vendors apply their own email syntax or deliverability validation before attempting a match. Records that pass your internal CRM validation but fail the vendor's stricter check are removed before the denominator is set.

Record age or activity filters. Some vendors exclude records that have not appeared in their graph within a recency window, treating them as unlikely to match before attempting to match them. This can meaningfully reduce the denominator for files that contain a mix of recent and historical customer data.

None of these practices are inherently wrong. Some of them produce a more actionable number by focusing the reported rate on the segment of your file that is plausibly matchable. The issue is that buyers comparing rates across vendors, or tracking rates over time with the same vendor, are often comparing numbers built on different foundations.

What a More Useful Evaluation Looks Like

Rather than comparing headline match rates directly, a more stable evaluation approach asks for the absolute count of matched records alongside the rate, and requests a breakdown of how many records were removed before matching and why.

For a campaign planning decision, the question that matters most is: how many of the specific customer segments I need to reach were resolved to addressable inventory? A 70% match rate against a denominator from which your highest-value customers were pre-filtered tells you less than a 55% rate calculated against your full file with segment-level detail.

If your campaign depends on reaching a specific behavioral cohort within your CRM, it is worth asking the vendor to report match rates at that segment level separately, not just across your full file. A vendor might match your full file at 65% while matching your target segment at 40%, or at 80%, depending on how that group's data characteristics align with the vendor's graph coverage. The aggregate rate will not reveal that difference.

Tracking Rates Over Time Requires Denominator Consistency

Match rate trending is a legitimate operational metric. If your rate is declining over successive uploads, it may signal data quality issues in your CRM, graph coverage changes, or shifts in your customer population toward harder-to-match segments.

But that signal is only interpretable if the denominator definition stays consistent across periods. If your vendor changes pre-match filtering logic, updates deduplication rules, or expands or contracts the geographic scope of their graph, a rate change may reflect those methodological shifts rather than anything about your data or their coverage.

It is a reasonable practice to ask your onboarding vendor to document their denominator definition in writing and to flag any changes to that definition when they occur. Vendors that improve their graph will often report that improvement as a rate increase, which is accurate, but it will also compress your ability to track the underlying data quality signal you were watching.

The Rate Is a Starting Point, Not a Verdict

Match rate is a useful input. It is not a complete description of what you can reach, how accurately those records were resolved, or how the matched population compares to the customers you actually need for the campaign in front of you. Treating it as a complete verdict on vendor quality, or as a stable planning number without understanding the denominator behind it, builds a media plan on an assumption the vendor never explicitly made.