What is a match rate?

That definition matters because match rate gets used two ways in marketing tools, and the two don't mean the same thing. The first describes accuracy: out of every hundred website visitors(opens in a new tab) or ad audience(opens in a new tab) members, how many did the system connect to a verified identity, whether a named contact(opens in a new tab) or a resolved account. The second describes volume: how many rows a tool returns, regardless of confidence(opens in a new tab). A platform can post a high number by loosening its confidence threshold and calling near-matches a hit. That number looks impressive in a sales deck and falls apart the first time a rep calls a contact who was never there. An honest match rate only counts identities the system can stand behind. Guesses, probabilistic near-matches, and household-level inference dressed up as a person inflate the number without adding anything you can act on.

How match rate is calculated

Most vendors calculate it the same way: divide the number resolved to an identity by the total pool of visitors or audience members, then multiply by 100. The formula is simple. The dispute is over what counts as "resolved." Some platforms count a cookie(opens in a new tab)-matched household. Others count a business email guessed from a domain lookup. Only a few count a specific person confirmed against a verified data source. Ask any vendor(opens in a new tab) quoting a match rate what identity confidence threshold sits behind the number before you compare it to anyone else's.

Why a higher match rate isn't automatically better

Two vendors can quote very different match rates and still be measuring different things, and the higher number doesn't make the better platform. If one figure includes probabilistic guesses and the other only counts confirmed identities, the smaller number is the one your sales team should trust. Inflated match rates create a specific, expensive failure: reps get handed contacts who don't exist, or accounts get counted as engaged because of a visitor who was never identified. The cost shows up later, in pipeline that never closes and a sales team that stops trusting the data feed.

Account-level and contact-level match rates

Account-level tools report match rate against companies: did the system work out which business an IP address or cookie belongs to? Contact-level tools report it against people: did the system work out which named person on the buying committee(opens in a new tab) at that company just looked at the pricing page? The two numbers answer different questions. A platform that only works at the account level can post a high match rate and still leave you with a list of company names and no one to call. The contact-level number is harder to earn and more useful once you have it, because it tells your sales team who to call.

Match rate and intent measure different things

Match rate measures how many visitors or audience members get resolved to a real identity. Intent data measures behavior, like a job change, a pricing page visit, or research activity. A visitor can be matched to an identity and show no buying behavior at all, and a company can show strong first-party engagement with a match rate that never reaches the specific person behind it. The same holds for ad targeting: a lower, verified match rate can build a more accurate audience than a higher, inflated one that includes near-guesses, because the audience is made of people who exist.

What to ask before you trust a match rate

Match rate is a useful metric only when you know what's behind it. Before treating a vendor's number as a reason to buy, ask three things: what threshold counts as a match, whether the number describes people or just companies, and whether the identities hold up when a rep tries to use them.