Fill rate

How fill rate is measured

Fill rate starts with a clear field and a clear denominator. Pick the field, such as work email or direct dial. Count how many input rows lacked a usable value. After enrichment, count how many of those rows now hold a non-empty value. Divide to get fill rate for that field on that batch.

RichAPI places fill rate next to match rate and data accuracy when describing how to judge an enrichment run 1. Match rate asks whether the provider returned the value you requested for submitted records 1. Fill rate asks a neighboring question about completeness: after the job, measure how complete this field is across the file. The two numbers can diverge when some rows already had values, when providers overwrite blanks only, or when billing counts differ from attempted rows 1.

Waterfall enrichment is one way teams chase higher fill rate without trusting a single vendor. Each step can be scored on its own for the same field 1. A second provider may fill rows the first left blank. The combined fill rate is what the CRM actually sees, as long as deduplication and overwrite rules are explicit.

Fill rate is not accuracy. A filled field can still be wrong, stale, or pointed at the wrong person. Pair fill rate with verification and freshness checks. Data decay keeps eating filled values as people change jobs and mailboxes close 2. HubSpot cites B2B data decaying at about 2.1% a month, or about 22.5% annualized, from MarketingSherpa research 2.

Credit design changes how teams interpret fill rate. RichAPI Email finder costs 5 credits per call and Email verifier costs 2 credits per verdict, with waterfall misses billing zero on those miss-free endpoints 3. A high fill rate that burns credits on disposable or role inboxes is a empty win. Measure fill rate on the rows you will actually use.

Data enrichment programs that only report a vendor headline fill rate miss the operational picture. Require field-level fill rate on your sample, before and after each waterfall step, with the same denominator definition every week.

Ops teams should also freeze a control sample that never enters the waterfall. If fill rate on the control drifts without enrichment, the CRM import path is rewriting blanks and the metric is lying. Keep that control in every monthly scorecard next to the enriched cohort.

Why fill rate matters in vendor bake-offs

Vendor demos lean on a single coverage percentage. Ops teams need fill rate on their own file, field by field, with a frozen sample 1. That is the only way two providers become comparable.

Define blank carefully. Whitespace, placeholder strings, and personal addresses in a work-email field should not count as filled for a B2B motion. Publish the rule before the bake-off so nobody argues after the scores land.

Separate net-new fills from overwrites. A provider that replaces a good CRM value with a different string can look productive on raw fill while creating support tickets. Track both net fill and overwrite rate.

Budget follows fill rate when credits are per call. Email finder at 5 credits and Email verifier at 2 credits make empty misses cheap on waterfall paths that bill zero on a miss 3. New RichAPI accounts get 100 free credits to run a small bake-off sample under the same rules 3.

Re-measure after waterfall enrichment steps, not only at the end. The step that adds a few points of fill at high credit cost may lose to a cheaper step with the same lift. Keep match rate and fill rate on the same scorecard so coverage stories stay honest.

Finally, schedule refresh. Fill rate on day one is not fill rate on day ninety when data decay has moved titles and mailboxes 2. A quarterly re-enrich plan belongs next to the original fill target.

Publish the fill-rate formula in the same runbook as credit budgets. When finance asks why Email finder at 5 credits and Email verifier at 2 credits were spent, the answer should point to net-new verified fills, not to raw vendor coverage slides 3.

Example of raising email fill rate on a conference list

A demand team uploads thousands of conference badge rows with company domain and name but mostly empty work emails. Provider A returns emails for under half the rows. Provider B returns emails for under a third of the remainder. Combined fill rate on the email field climbs well past either vendor alone 1.

They verify every filled address with RichAPI Email verifier at 2 credits per verdict 3. Invalid and disposable rows are stripped, so usable fill rate is lower than raw fill rate. Misses on the verifier cost zero credits 3.

The team stores field-level fill rate, usable fill rate after verification, and credit spend per net-new valid email. Next quarter they re-run a sample to watch decay 2. That is fill rate treated as an operating metric, not as a slide in a vendor deck.

Leadership later asks for a second conference list. The same formula, blank rules, and verification step run again so the two events are comparable. That is how fill rate becomes a durable KPI instead of a one-off claim.

Fill rate vs match rate

Fill rate asks how complete a field is after enrichment. Match rate asks how often a provider returns the requested value for submitted records.