Data freshness

How data freshness is tracked

Data freshness starts with a timestamp. Every critical field needs a last-verified or last-enriched time, not only a last-touched CRM time from an unrelated workflow edit. Without that stamp, a complete-looking record can be months out of date.

Data decay is why freshness matters. People change jobs, titles, and phone numbers. Mailboxes close. Companies merge or shut down 1. HubSpot's database decay page states that B2B data decays at 2.1% a month, an annualized rate of 22.5%, citing MarketingSherpa research 1. Freshness SLAs exist to outrun that curve on the fields that drive pipeline.

Measurement is simple in form and hard in practice. Pick the fields that matter, such as work email and direct dial. Define what counts as a fresh verification: a provider re-check, a successful send, or a confirmed human update. Then report the share of rows whose last-verified time is inside the SLA window.

Match rate and fill rate can hide staleness. A provider may return a value quickly while that value is already old in the source network 2. Score freshness beside coverage so bake-offs do not reward the fastest stale dump.

Enrichment credit design shapes refresh cost. RichAPI Email verifier costs 2 credits per verdict and Email finder costs 5 credits per call, with waterfall misses billing zero on those miss-free endpoints 3. A quarterly re-verify of the open pipeline is usually cheaper than a bounce-driven emergency scrub after a blast.

Waterfall enrichment helps when one provider goes quiet on a segment. Freshness still needs a clock. A waterfall that only runs once at list creation leaves the same decay problem six months later 1. Put the clock in the CRM and in the enrichment job scheduler.

Store freshness at field level, not only at contact level. A fresh company domain with a stale work email is a common trap. Dashboards that show one green freshness badge for the whole record hide the field that actually burns sender reputation on the next sequence.

When a verification fails, clear or quarantine the value rather than leaving a stale string with a new timestamp. Moving the clock without confirming the value invents fake freshness and trains the team to ignore the SLA.

Why freshness SLAs beat one-time enrichment

One-time enrichment is a project. Freshness is a system. Projects create a clean file for a launch. Systems keep the open pipeline trustworthy every month 1.

Set tighter SLAs on fields that burn reputation when wrong. Work email for outbound deserves a shorter window than firmographic industry tags. A bounced wave from stale emails hits sender reputation faster than a wrong employee count hits a dashboard.

Report freshness by segment. Enterprise accounts may justify weekly checks on buying-committee emails. SMB top-of-funnel can live with a wider window if volume is verified right before send.

Budget the refresh. Email verifier at 2 credits per verdict makes scheduled re-checks predictable 3. New RichAPI accounts get 100 free credits to prove the cadence on a sample before rolling it across the CRM 3.

Do not confuse CRM activity with freshness. A rep note does not re-verify the mailbox. Only a defined verification or enrichment event should move the freshness timestamp.

Tie freshness alerts to data enrichment jobs, not only to human dashboards. When the share of stale open-opportunity emails crosses a threshold, enqueue re-verify automatically. That is how freshness survives a busy quarter.

Pair freshness with fill rate on the same monthly review. A segment can look complete while half the emails are outside the SLA window. Coverage without a clock is how bounce spikes return after a quiet quarter of decay 1.

Field-level freshness also feeds vendor renewals. If a provider's values age out inside 30 days on your sample, the contract conversation should include refresh cadence, not only headline match rate 2.

Example of a quarterly freshness SLA on work emails

A revenue ops team sets a 90-day freshness SLA on work email for any contact in open opportunities 1. Each night a job flags emails whose last-verified stamp is older than 90 days 1.

Those rows go through RichAPI Email verifier at 2 credits per verdict 3. Invalid results trigger Email finder at 5 credits to attempt a replacement 3. Misses on those waterfall endpoints bill zero 3. Fresh timestamps are written only when verification passes.

After one quarter, bounce rate on opportunity email drops, and the team can show leadership the share of open-pipe contacts inside the SLA. They keep match rate and freshness on the same monthly scorecard so coverage never outruns trust 2.

The same job later expands to direct dials on late-stage opportunities with a 60-day window 1. Credits stay predictable because Phone finder and Email verifier prices are known up front on the pricing page 3. The SLA board now shows email and phone freshness side by side for open pipe.

Data freshness vs data decay

Data freshness measures how recently a field was verified. Data decay describes the ongoing loss of accuracy that makes those timestamps necessary.