Coverage rate
Coverage rate is the share of an input list a data provider or enrichment waterfall returns any result for at all, a breadth measure that's separate from match rate, which asks whether what came back is actually correct.
Coverage rate answers one narrow question: out of everyone on a list, what fraction did a provider return anything for. It says nothing about whether what came back was the right email for the right person, that's match rate's job, or whether it actually reaches an inbox, that's bounce rate's job. A provider can post a strong coverage rate by returning a low-confidence guess for nearly everyone, which looks better on a coverage chart than a smaller, more accurate result set ever would.
Why more providers doesn't mean more useful coverage
Stacking additional providers into a waterfall raises the aggregate coverage rate almost by definition, since each new source has a chance to fill a row the ones before it missed. But past a certain point, an added provider mostly returns records the earlier ones already found, pulled from a different vendor's index of the same public web, not new coverage at all. A waterfall curated for a specific persona and geography can post a lower total provider count and still beat a wider one on coverage that's actually usable, because the sources in it are the ones likely to have data on that specific slice of people.
In practice
Read coverage rate together with match rate and bounce rate, never alone. A high coverage rate with a weak match rate just means a provider is willing to guess more often, not that it's finding more real contacts.
What people get wrong
Coverage rate gets treated as the main scorecard for choosing a data provider, the same mistake as leaning on match rate alone. Both numbers describe how often a provider says something. Neither says whether what it said is true. Bounce rate, checked after the fact, is what actually answers that.
