Data quality
How Often Should You Re-Enrich CRM Data?
CRM records drift as people change jobs and companies move. A cadence for re-enriching contact data: what to refresh, when to do it and how to budget credits.
By the GTM Scoop team · Published · 4 min read
Every CRM record is at its most accurate on the day it is created. After that, people change roles, companies move or merge, and phone numbers get reassigned, and nothing in the CRM notices. A one-time cleanup fixes today's records, then they start to age the same way.
The fix is a cadence: a plan for which records get enriched again, when, and with how many credits. This post sets one out. It assumes you know what enrichment does; if not, start with what data enrichment is.
Why a cleanup does not last
- Job changes and promotions make titles, emails and direct lines wrong without anyone touching the record.
- Companies move offices, open and close locations, merge and change names.
- Phone numbers are reassigned, and shared inboxes replace people who left.
- New records arrive with typos, personal addresses in work-email fields and missing company details.
We are not going to quote an industry-wide decay rate. It varies with your market and with how a list was built, and a borrowed number is a poor basis for a budget. Measure your own on a sample instead: B2B contact data accuracy explains how.
Re-enrich on events, not only on a timer
A calendar cadence is a backstop. The records most worth refreshing are the ones about to be used:
- When a lead is created, before routing and scoring run, so territory and size rules have fields to work with.
- Before a campaign or a new sequence goes out to a list.
- When an email bounces or a number fails, a sign that the rest of that record may be stale too.
- When an account moves into an open opportunity, so the buying group in the CRM is current.
- When territories are redrawn, since routing depends on location and size.
- When a list arrives from an event, a partner or a purchase.
A starting cadence by record type
Treat these as defaults to adjust once you have measured how fast your own data drifts.
New leads: at creation
Enrich every new lead as it arrives. It is the cheapest refresh you will ever do, because the record has not been used yet and its gaps are obvious.
Open pipeline: every quarter
Accounts with live deals are where a wrong title or a departed champion costs the most. A quarterly pass keeps contacts and company details current while the deal is open.
Target accounts: before each campaign
Refresh the accounts at the top of your target list before each campaign rather than on a fixed date, so the people you are about to contact are the people still there.
Customers: twice a year
Customer records feed renewals, expansion and lookalike analysis. Twice a year is usually enough to catch moves, new decision makers and changes in size.
Dormant records: only before you use them
Contacts nobody plans to touch do not need refreshing on a timer. Enrich them again when a re-engagement campaign is planned, and archive what no longer matches anything.
Budget credits to the cadence
On GTM Scoop, one enrichment credit enriches one account. Starter includes 200 credits a month and Growth 500; the Free plan does not include enrichment. Credits refill every month, on monthly and annual plans alike. Three rules shape how far they go:
- A start needs at least as many remaining credits as the list has rows.
- Only the rows that match are charged, and a failed job costs nothing.
- Starting an enrichment that is already running returns the running job, so a retried start is never charged twice.
A worked budget: a team that enriches about 120 new leads a month and refreshes 80 pipeline accounts needs about 200 credits, which fits Starter's 200. Add a quarterly refresh of 900 target accounts and that month needs far more than Growth's 500. Spread the refresh over three months instead, 300 a month, and the total stays within Growth. GTM Scoop pricing explained has more examples.
Running a refresh in GTM Scoop
- Bring the records in. Salesforce and HubSpot syncs pull up to 5,000 contacts at a time into Connect Data, up to 20 syncs an hour. A CSV export works too.
- Map the columns. Matching tries phone number, then email, then address and ZIP, so map every phone, email, address and ZIP column you have.
- Check the coverage: you see how many rows can be matched before you commit any credits.
- Enrich, then review which signal each record matched on (phone, email or address) and spot-check a sample.
- Send the refreshed records back. In HubSpot, a contact with the same email is updated instead of added twice; Salesforce receives records as Leads or Contacts, so decide how your org handles duplicates before you send. CRM enrichment for HubSpot and Salesforce covers both.
Keep a record of each refresh
- Store the date each record was last enriched, in a field of its own.
- Keep the signal it matched on, so anyone can see how the match was made.
- Decide which fields a refresh may overwrite. A direct line a rep confirmed on a call is worth more than any reference dataset.
- Keep a suppression list. When someone opts out, remove them everywhere, so a refresh never adds them back.
Automate it
Once the cadence is settled, script it. The REST API runs the same steps as the web app: create an upload, map it, start a run, start the enrichment job, check its status about once a minute and read the results. There are no webhooks, so a scheduled job that polls is the usual pattern. Read the credit balance first: the credits endpoints return both monthly balances and say whether a list of a given size fits.
Try it in GTM Scoop
Pull contacts in from HubSpot or Salesforce, or upload a CSV, and see how many rows match before you spend a credit.