What Match Rate Should You Expect From a Contact Enrichment API?
When a RevOps or sales team sizes up a contact enrichment API, the first question is almost always the same: "what's your match rate?" It's the right instinct pointed at the wrong number. Match rate is the easiest figure in the category to inflate and the hardest to compare across vendors — no two providers define it the same way, and several have a quiet incentive to define it generously.
There is no universal match-rate range that applies to a single-source API or a waterfall. Measure returned fields and independently accepted fields on the same representative input sample. A candidate match does not prove correctness, deliverability or reachability.
This guide covers what a match rate really measures, the ranges you can realistically expect, what pushes the number up or down, and how to test a provider on your own data before you commit — so a percentage on a sales slide doesn't end up deciding your pipeline for you.
What match rate should you expect?
No comparable independent benchmark was verified for this guide. Report how the provider defines a match, which field was requested, the submitted sample and the acceptance rule. Evaluate architectures by their observed incremental contribution on that sample.
- Single-source API: Evaluate coverage and accepted fields in the markets it serves. One provider can be a good fit without representing every region or role.
- TargetWise provides waterfall contact enrichment, company enrichment and reverse email lookup through REST, MCP and a workspace dashboard. Contact lookups use 15+ specialist sources and return available work emails and business phones. Returned phones are unclassified unless the response says otherwise; a returned email is not a deliverability guarantee. See the contact enrichment API.
- Business phone, direct dial and mobile: These are different field scopes. Measure each requested type separately and confirm classification and ownership where the workflow needs them. No comparable cross-provider phone benchmark was verified.
Coverage requires a defined sample
No comparable independent benchmark verified for fixed single-source, waterfall or phone ranges. Record the same inputs, requested field, market, date, acceptance rules and costs before comparing results.
Why you can't take that number at face value
A reported match rate is meaningful only when its definition, sample and acceptance policy are recorded. Check these conditions before trusting a percentage.
What a match rate actually measures
The arithmetic is simple: match rate = records returned ÷ records submitted. Send 1,000 contacts, get 850 back, that's an 85% match rate. The problem hides in the word "returned."
Hand the same 1,000 records to two providers. One returns everything it can assemble — including guessed pattern addresses like first.last@company.com that it never actually checked. The other returns only addresses it has verified as deliverable. The first posts 92%; the second posts 68% — on identical input. The percentages look comparable. They are not. They're measuring different things.
The terms vendors blur
Much of the confusion in evaluating enrichment APIs comes from four terms used interchangeably in sales decks that mean different things in practice:
| Term | What it measures | Why it isn't enough on its own |
|---|---|---|
| Match rate | Share of submitted records that come back with any result. | Says nothing about whether the result is correct or reachable. |
| Coverage | Share of a target universe the provider holds any data on. | Holding a record isn't the same as returning the field you asked for. |
| Fill rate | Share of the requested fields actually populated per record. | A record can count as "matched" with the one field you needed left blank. |
| Accuracy / verified rate | Share of returned data confirmed correct and deliverable. | The number that maps to pipeline — and the one least often quoted. |
When a vendor quotes "95%," ask which of these they mean. A 95% match rate sitting on a 70% verified rate is a completely different product from 95% verified — often at the same price.
Five ways the number gets inflated
Because the figure is self-reported and rarely defined, there are well-worn ways to make it look bigger than the usable data behind it. Watch for:
- Pattern guessing. Returning first.last@domain.com because the format is common, without checking the mailbox exists. Counts as a match; bounces on send.
- Catch-all domains. Some company domains accept mail to any address, so an SMTP check "passes" for a mailbox nobody reads — counted as deliverable when it isn't.
- A company match dressed up as a contact match. The provider found the company but not the person, and still logs a match on the record.
- Counting any field. A job title or a LinkedIn URL comes back but no email or phone — and the record is still tallied as matched.
- Cherry-picked samples. The demo runs on a list curated to the provider's coverage sweet spot, not your messy real one.
None of these are necessarily dishonest — they're definitional. Which is precisely why the only match rate you can trust is the one you measure yourself.
The number that actually matters: verified rate
Returned-field coverage is one stage of the workflow. Define independent identity, deliverability and phone-reachability checks before relying on those fields. Google’s sender guidelines describe authentication, permission and user-reported spam requirements; they do not establish the universal 2% total-bounce or 1% hard-bounce thresholds previously stated here.
So measure two numbers, not one: match rate (records returned) and verified rate (records confirmed deliverable and reaching the right person). The second is the one your revenue is downstream of.
Seen as a funnel, the headline match rate is the widest point — and everything that matters happens below it:
A match rate you can't verify is a bounce rate you haven't measured yet.
What actually drives your match rate
Six factors move the number more than the provider's logo does. Read a vendor's headline rate through them:
1 · Input quality
What you feed in. A name plus a company domain matches far better than a name alone. Garbage in, low match out.
2 · Database coverage
One source versus many. The biggest single lever — waterfall exists precisely because no one database covers everyone.
3 · Data freshness
Professional contact information changes as people move roles and companies change. Measure freshness in your own records and store source observation or verification dates when available. Retrieval time alone is not a verification date.
For implementation, see the reverse email lookup API and its supported inputs.
4 · Verification strictness
Strict checking lowers the reported number and raises the usable one. Loose providers pad the rate with guesses.
5 · ICP & segment fit
Coverage isn't uniform. The same API can hit 78% on enterprise and 11% on a local segment. The data has to fit who you sell to.
6 · Channel
Email is easier than phone; direct dials are scarcer and decay faster. A blended "match rate" hides which one is failing.
A recent retrieval can still return an outdated employer or contact channel. Compare current identity and employment evidence before using the record; do not apply an unsourced annual job-change rate to every professional or geography.
How we keep the match rate honest
TargetWise retrieves available work-email and business-phone fields through eligible contact routes. Returned values are not guarantees of mailbox deliverability, phone reachability or mobile classification. Paid plans provide a monthly usage balance, and unresolved requested fields consume no balance.
How to test a provider — and what to do with the misses
A match rate in a deck is a marketing claim, not a measurement. Run your own:
- Test on your list, not theirs. Send 100 accounts from your real ICP — never the vendor's curated sample.
- Measure verified coverage, not records returned. Actually send to the emails and count the bounces; dial the numbers and count the connects.
- Ask how they define a match. "Returned anything" versus "verified deliverable" — get the definition in writing before you compare quotes.
- Break it down by segment. A blended number hides the segments where coverage collapses to single digits.
- Watch for repeated phone numbers. The same number across several contacts at one company is a main switchboard line, not a direct dial.
The records that don't match
Some records remain unresolved, depending on the identifiers, field and market. Preserve those outcomes and decide whether stronger evidence or a later relevant event justifies another lookup.
- Re-run on a cycle. A contact missing today often surfaces next month as sources refresh and new ones are added. Decay cuts both ways — records appear as well as expire.
- Layer a second pass. A different source mix catches what the first missed — the whole logic of waterfall, applied to the leftovers.
- Route the high-value ones to manual research, where an SDR's time is justified by deal size.
- Suppress, don't guess. The one thing not to do is invent an address to hit a coverage target — that's exactly how a clean match rate turns into a dirty bounce rate.
Why pay-per-match changes the cost math
Pricing rules differ by provider, operation and plan. Record attempted-call charges, returned-field charges, subscriptions and unused balances separately. A returned-field rule does not remove a fixed subscription commitment or establish that a field is independently accepted.
The difference shows up in cost per usable record. Take 1,000 records at a 65% match rate, and compare a credit model that bills every attempt against pay-per-match (figures illustrative):
| Cost component | Question to resolve |
|---|---|
| Subscription | What fixed monthly or annual commitment applies? |
| Consumption | Does the operation charge for attempts, returned fields or accepted results? |
| Unresolved TargetWise contact fields | Use no email/phone balance; attempts still count toward request limits. |
| Effective accepted-result cost | Allocated subscription, usage and verification cost divided by accepted results; not a fixed price for every coverage level. |
Unresolved requested TargetWise email and phone fields consume no usage balance. The paid monthly subscription still applies, and unused included balance resets at renewal. Effective cost per accepted result therefore changes with utilization and field acceptance; it is not flat for every match rate.
TargetWise provides waterfall contact enrichment, company enrichment and reverse email lookup through REST, MCP and a workspace dashboard. Contact lookups use 15+ specialist sources and return available work emails and business phones. Returned phones are unclassified unless the response says otherwise; a returned email is not a deliverability guarantee. See the contact enrichment API.
Retrieve work emails and business phones for selected records
Use the dashboard, REST API or a compatible MCP host for selected, individual records. TargetWise does not expose CSV upload or asynchronous bulk enrichment. Evaluate returned work emails and unclassified business phones using your own acceptance policy.
Frequently asked questions
What match rate should I expect from a contact enrichment API?
There is no verified universal range. Measure returned work-email and phone fields on a representative sample, state the input and denominator, and report independently accepted results separately. Architecture and provider counts do not establish a guaranteed percentage.
What is a good match rate for an enrichment API?
A useful rate meets the field, market and acceptance requirements of your workflow. Compare accepted coverage, incorrect identities, latency and total cost on the same sample. A higher raw return rate can contain more unusable data.
Why do match rates vary so much between providers?
Input identifiers, geography, field scope, coverage and acceptance rules differ. A person match, a returned email and a verified current mailbox are different outcomes. Define the same metric before comparing providers.
What's the difference between match rate and verified rate?
Match rate counts outcomes under an explicit return rule. Verification evaluates a stated property of a value or identity. Report its denominator and evidence; email deliverability, phone reachability and permission to contact are separate questions.
What factors affect contact enrichment match rates?
Important factors include identifier quality, requested fields, market coverage, record freshness, source overlap and acceptance rules. Measure their effect by segment rather than assigning a universal order or percentage.
How is match rate calculated?
Match rate equals records returned divided by records submitted, expressed as a percentage. Send 1,000 records and get 850 back and the match rate is 85%. The figure says nothing about whether those 850 are correct or deliverable, which is why it should always be read alongside a verification or bounce measurement.
Is a higher match rate always better?
No. Evaluate whether the additional returned fields belong to the intended person and meet the workflow’s acceptance rules. Coverage is different from correctness, deliverability or reachability.
How do I test an enrichment API's match rate before buying?
Freeze a representative, authorized input sample and acceptance policy. Run each provider using identical identifiers and field scope, then assess identity, returned fields, independently accepted fields, no-match handling, latency and total cost by segment.
What's a normal email bounce rate from enrichment data?
A returned address is not a deliverability guarantee, and no universal bounce threshold was verified for this guide. Monitor your own delivery results and provider-specific sender requirements. User-reported spam rate is a different measure from bounce rate.
Does pay-per-match pricing change how much the match rate matters?
Confirm the billable event and any fixed subscription. TargetWise’s unresolved requested email and phone fields use no usage balance, but paid plans renew monthly and unused balance resets. Cost per accepted result depends on utilization, rates and your acceptance policy.