Data quality metrics turn vague complaints about “dirty CRM data” into numbers you can trend, fix, and defend in a leadership meeting. If you only track one thing, you still don’t know whether the problem is missing fields, stale records, duplicates, or bad contact data poisoning deliverability.

This listicle ranks eight metrics B2B teams actually use in RevOps and GTM workflows — not abstract data-lake theory. For frameworks, definitions, and how metrics fit together, read our complete guide to data quality metrics. For quick answers to common questions, see the data quality metrics FAQ. To connect metrics to the classic dimensions (accuracy, completeness, consistency, and more), bookmark our breakdown of data quality dimensions.

1. Field completeness rate

Field completeness rate is the percentage of records that have a non-empty value for a field you’ve defined as required for a given workflow — for example, work email, mobile phone, job title, or billing country.

How to measure it: Pick the fields that gate routing, enrichment, or reporting. For each field, divide the count of records with a populated value by the total records in scope (often “all open opportunities” or “all contacts owned by sales”). Track it weekly in the same cohort so you’re comparing apples to apples.

Why it matters: Low completeness silently breaks automation. Lead scoring, territory assignment, and sequence enrollment all assume certain fields exist. Teams often blame “bad messaging” when the real issue is half the records missing the data the workflow needs.

Practical example: Your outbound team requires work email and company domain. If 62% of new leads have both fields filled, your completeness rate for that pair is 62%. Raising it to 85% might be worth more than another A/B test on subject lines.

2. Duplicate record rate

Duplicate record rate is the share of your database that represents the same real-world account or person more than once — often expressed as duplicates per thousand records or as a percentage of total records flagged by matching rules.

How to measure it: Run deterministic matching (email, domain + name) and fuzzy matching (nickname variants, typos) on a schedule. Count clusters with more than one member. Many teams pair the metric with a merge rate: how many duplicate clusters you actually resolved in a given period.

Why it matters: Duplicates inflate pipeline, split activity history, and cause reps to contact the same person twice. They also distort attribution and make executive reporting look healthier or worse than reality.

Practical example: After a big event import, you might spike from 2% duplicate rate to 6%. If you don’t measure it, marketing celebrates “record growth” while sales dials the same VP three times from three CRM cards.

3. Email hard bounce rate

Email hard bounce rate is the percentage of sent messages that permanently fail — invalid address, unknown user, or dead domain — as opposed to soft bounces (mailbox full, temporary failure).

How to measure it: From your ESP or engagement platform, take hard bounces divided by emails sent for a cohort (campaign, sequence, or domain). Exclude one-off operational blasts if you’re benchmarking ongoing prospecting quality.

Why it matters: Hard bounces are both a deliverability risk and a data quality signal. A rising hard bounce rate often means you’re importing unverified lists or your CRM is full of decayed addresses. That hurts inbox placement for the whole domain, not just the bad rows.

Practical example: If 4% of your cold sequence hard-bounces, that’s a red flag for list sourcing or verification — well above what you’d expect from systematically verified B2B email data.

4. Enrichment match rate

Enrichment match rate is the percentage of input records for which your enrichment process returns the target attributes you care about — typically verified work email, mobile number, or firmographic fields — at least once.

How to measure it: Divide successful enrichments by attempted enrichments over a time window. Segment by region, industry, and data source if you can; match rate almost always varies by segment.

Why it matters: Match rate tells you whether your data acquisition layer is doing its job. A low match rate looks like a sales problem (“reps can’t get meetings”) when it’s actually an upstream completeness and coverage problem.

Practical example: Single-vendor enrichment often lands in the 40–60% range for hard contacts. Waterfall-style enrichment — trying multiple providers in sequence — pushes match rates much higher because each vendor has different coverage. Platforms like FullEnrich automate waterfall enrichment across 20+ data providers, run triple email verification on addresses returned, and apply multi-step validation so mobile numbers are verified and actionable — which is why RevOps teams track match rate alongside bounce rate.

5. Average record age (data freshness)

Average record age measures how long it has been since a record’s key attributes were verified or observed — for example, days since last email validation, last successful call, or last CRM update tied to a trusted source.

How to measure it: Define “fresh” per object: contacts might use last-enriched date; accounts might use last website crawl or last opportunity touch. Compute the median or average age across active records. Median is usually more honest than mean when a few ancient rows skew the average.

Why it matters: B2B data decays constantly — people change jobs, companies rebrand, and domains die. Freshness explains why two teams with similar completeness can get totally different reply rates.

Practical example: If your median contact hasn’t been touched in 18 months, your “complete” CRM is still a gamble for outbound. Refreshes and re-verification belong in the same conversation as net-new acquisition.

6. Cross-system consistency rate

Cross-system consistency rate is the percentage of linked records where a field matches across systems of record — CRM, billing, data warehouse, or marketing automation — within defined rules (same normalized domain, same employee count band, etc.).

How to measure it: Join records on a stable key (CRM ID, account ID). Compare prioritized fields: company name, domain, country, ARR band, employee range. Count mismatches; consistency rate is 100% minus the mismatch share.

Why it matters: RevOps lives at the intersection of tools. When billing says “enterprise” and CRM says “SMB,” forecasting and CS handoffs both break. Consistency metrics surface integration and process issues early.

Practical example: After a CRM migration, you might find 12% of accounts have a different domain in CRM than in your billing tool. That’s a consistency problem — and a precursor to duplicate leads and failed automations.

7. Validity rate (format and rule conformance)

Validity rate is the percentage of values that pass structural and business rules: emails match RFC-style patterns, phone numbers parse to E.164, picklists contain only allowed values, and custom fields respect ranges you’ve defined.

How to measure it: Run scheduled validation jobs (in the CRM, in reverse ETL, or in a warehouse) and score each field. Roll up to an overall validity rate or keep per-field dashboards for owners.

Why it matters: Validity is the bridge between “we have a value” and “we have a value we can use.” A populated phone field that fails mobile validation is completeness without usability.

Practical example: If 30% of “mobile” numbers in CRM fail a basic carrier/mobile check, your connect-rate problems may be a validity issue — not a messaging issue. Our data quality checks guide covers how to design those rules without boiling the ocean.

8. Time-to-resolution for data issues

Time-to-resolution for data issues is the average (or median) time from when a quality problem is detected — failed sync, bounce spike, duplicate cluster, broken integration — until it is fixed or quarantined.

How to measure it: Log incidents in tickets or a dedicated data-quality queue. Track created-at to resolved-at. Break down by category: integration, vendor file, user entry error.

Why it matters: Most teams obsess over detection and ignore throughput. A metric nobody owns trends toward “we have 200 open Jira tickets about Salesforce.” Time-to-resolution forces ownership and prioritization.

Practical example: A webhook stops updating firmographics from your enrichment tool. Detection took 6 hours; root cause and backfill took 9 days. That’s your baseline time-to-resolution — and the number to cut next quarter.

Putting the metrics to work

You don’t need a twenty-tab dashboard on day one. Pick three metrics tied to your biggest revenue risk — usually completeness, duplicates, and email hard bounces for outbound-heavy teams — and review them on a fixed cadence. When leadership asks “is our data getting better?”, you’ll have an answer.

For a structured assessment playbook, use our data quality assessment guide. If CRM-specific hygiene is the pain point, read CRM data quality and CRM hygiene. Governance-minded teams should connect metrics to policy in our data quality governance article. Finally, waterfall enrichment is the most direct way to improve match rate and verified completeness without stacking a dozen vendor contracts by hand.

Want to see how verified enrichment behaves on your own leads? Start with 50 free credits on FullEnrich — no credit card required — and compare match rate and bounce outcomes against your current source of truth.