What Is Contact data freshness?

Measure age from the relevant event

Contact data becomes useful or stale in relation to a decision. A role title used in a highly specific opener needs evidence that the person still holds that role. A country field used for segmentation may change less often. Decide which observation or verification event supports each attribute, then calculate age from that event. The CRM import date is only a record of system arrival.

Keep observed-at, retrieved-at and verified-at dates distinct where available. If a provider does not expose the observation date, mark that limitation rather than treating today's API response as fresh research. An email verification performed today tests a contact point under the verifier's method. It does not confirm current employment, authority, interest or whether contacting the person is appropriate.

Refresh around the intended action

Use refresh rules tied to how quickly the field can change and the consequence of getting it wrong. Review high-specificity role claims before they appear in a message. Recheck disputed employment when a reply or public event contradicts the stored value. A fixed monthly schedule can support maintenance, but it should not replace a check triggered by direct contrary evidence.

Preserve uncertainty and restrictions

When a newer source conflicts with a trusted observation, record the disagreement and send it to review. Do not overwrite a suppression flag or protected account status merely because the new row has a later timestamp. A hypothetical record imported today from a six-month-old list is not one-day-old contact evidence. Report the unknown or older observation date honestly. Measure freshness alongside accuracy, completeness and source reliability; refreshing an incorrect association more frequently only makes the same error appear more current.