Salesforce data enrichment: adding firmographics safely

Salesforce data enrichment means filling lead, contact and account fields such as industry, employee count, revenue, parent company and phone from an outside provider. Done well, it feeds routing, scoring, segmentation and territory design. Done carelessly, it overwrites what reps know, matches records to the wrong company and burns credits on junk. Decide which fields a provider may write, when, and how you will check the result before you connect anything.

What is enrichment actually for, and what can't it fix?

Enrichment exists to make a decision possible that a blank field blocks. If no rule, report or person uses a field, enriching it adds cost without value.

The usual decisions are these:

• Routing: send a lead to the right team by size, region or industry without a person reading it first.
• Scoring: weight fit attributes alongside engagement, so a small student signup does not outrank a qualified buyer.
• Segmentation: build campaign audiences by industry or size band that marketing can trust.
• Territory and capacity planning: count addressable accounts per segment before carving patches.

Enrichment cannot fix a missing process. It will not merge duplicates you already have, settle who owns an account, or make reps log activity. It also cannot tell you whether a company is a good customer for you. That judgment still comes from your own win and loss history.

What kinds of enrichment providers are there?

Providers fall into four broad groups, and many sell more than one. Buy for the group that serves your decision, not for the longest field list.

• Firmographic data describes the company: industry codes, headcount, revenue band, location, ownership and corporate family.
• Contact data describes people: job title, seniority, department, direct phone and business email.
• Technographic data lists the software and platforms a company appears to run, useful when your product replaces or plugs into something.
• Intent data suggests which companies are researching a topic now, based on content consumption signals the provider collects.

Coverage varies by region, company size and industry. Ask each shortlisted provider to enrich a sample of your own records, including hard cases, and grade the output yourself.

How does an enrichment provider connect to Salesforce?

Most providers offer an AgentExchange (formerly AppExchange) package, and many also expose an API. Middleware and batch files cover the gaps. The right route depends on timing needs and who will own the connection.

• AgentExchange package: fastest to start, with field mapping screens and scheduled jobs built in. Check what objects and fields it creates, and how it uses your API allocation.
• Direct API calls: Flow or Apex calls the provider when a record is saved. This gives full control over logic, but you own the code and its error handling.
• Middleware: an integration platform calls the provider and writes results back. Useful when several systems need the same enriched data.
• Batch file: export records, send them to the provider and import the returned file. Slow, but workable for a one-off backfill.

Our integration options guide compares these patterns in more depth, including security review and ownership after launch.

Does Salesforce still offer its own enrichment data?

Not in the way it once did. Data.com Clean and Prospector are retired, and current options either rely on partners or on data you bring yourself.

Salesforce Help lists Data.com as a retired product. Clean and Prospector stopped working in mid-2020, and the old Data.com fields left behind in some orgs no longer update. If your org still has those fields, check whether any report or automation depends on them.

Data 360, the product formerly called Data Cloud, has its own enrichments. These bring unified data onto record pages as copied fields or related lists. They surface data you have ingested into Data 360, so they only add firmographics if a provider feed lands there first.

Agentforce sales features also describe research and prospecting agents that pull from CRM, web and third-party sources. What they write back to fields, and which licenses include them, changes often. Ask your Salesforce account team what is current before you design around them.

Should enriched values overwrite what reps entered?

Usually not. Store provider values in their own fields, then decide per field group which value wins and when.

A rep who spoke to the buyer often knows the real headcount or the correct division. A blind overwrite throws that away and teaches reps to distrust the data. Keep a separate enriched field, such as Enriched Industry, beside the working field. A Flow can copy it across only when the working field is empty.

Add two support fields on each enriched object: Enrichment Source and Last Enriched Date. They let you audit coverage, spot stale values and switch providers later without guessing which values came from where.

Normalize before you report. Providers return their own industry labels and raw headcounts. Map them to your picklist values and size bands in one place, so a provider change does not break every report and routing rule.

How do we avoid matching records to the wrong company?

Match on website domain first, with company name, address and phone as backup, and review low-confidence matches before they write. False matches do more harm than blank fields.

Shared and free email domains are the classic trap. Exclude consumer mail providers before matching, or thousands of leads collapse onto one company. Subsidiaries are the second trap. A regional office can inherit the global parent's revenue and headcount, which then sends it to the enterprise team.

Most providers return a confidence score. Set a threshold, write only above it, and send the rest to a review queue. For parent and subsidiary links, our account hierarchies guide explains how to hold corporate families without inflating every location.

When should enrichment run?

Run it when a record is created, before routing reads the fields, and again on a schedule for records that matter. Avoid enriching everything nightly by default.

Timing is the part teams most often get wrong. If routing runs on save and enrichment arrives seconds later, routing reads blanks. Either wait for the enrichment callout to finish or re-run assignment once fields arrive. Our lead routing guide covers that sequencing from the routing side.

For scheduled refresh, scope tightly. Open opportunities' accounts, target accounts and active customers justify regular refresh. Leads that went cold long ago usually do not.

What drives enrichment cost, and how do we avoid waste?

Most providers charge by credits, records enriched or contacts revealed. Cost therefore tracks how many records you send, so cutting junk input is the cheapest saving.

• Filter out test submissions, spam, student and personal addresses before any call goes out.
• Merge duplicates first, so you do not pay to enrich the same company several times.
• Skip records that already have a recent Last Enriched Date.
• Reveal contact details on request, not for every contact in bulk.
• Check how refreshes are counted, since some contracts treat each refresh as a new credit.

Ask providers how failed matches, partial matches and refreshes are billed. Those terms differ more than headline rates do.

What compliance questions come with enrichment?

Contact enrichment brings personal data into Salesforce from a third party, so privacy rules apply. This is not legal advice; involve your privacy or legal team before contracting.

Ask each provider where the data came from and what notice or consent applies. Confirm how it handles deletion and opt-out requests, and whether it will re-add someone who asked to be removed. In Salesforce, make sure enriched contacts still respect your opt-out and do-not-call fields, and that a refresh cannot clear them.

Record provenance on the record itself with the Enrichment Source field. When someone asks where you got their details, you can answer. Our data privacy compliance guide covers consent objects and deletion handling in Salesforce.

How do we know enrichment is paying off?

Measure fill rate, match accuracy, routing outcomes and conversion by segment, before and after launch. Agree the baseline first, or you cannot show a change.

• Fill rate: the share of new leads and accounts with each key field populated after enrichment.
• Match accuracy: a sampled review of enriched records, checked by a person against the company website.
• Routing accuracy: how often leads are reassigned by hand after routing, and how many land in a catch-all queue.
• Conversion by segment: whether enriched size and industry bands actually separate good leads from weak ones.
• Rep trust: how often reps override or flag enriched values, which shows where data is weakest.

Who should govern enrichment once it is live?

Give one named owner responsibility for the provider, field mappings and spend. Without that, mappings drift and credits disappear.

That owner approves new enriched fields, reviews the confidence threshold and watches monthly credit use. Field changes go through the same change control as any other schema change. Keep the enrichment rules inside your broader data governance program rather than running a separate one.

Which of our projects involved enrichment?

A staffing firm we supported had bought a lead-enrichment tool alongside Salesforce but never had it working. As part of fixing its dashboards and activating Marketing Cloud Account Engagement, we resolved the integration so leads were enriched automatically. We also built templated geographic lead reports on top of it.

What should phase one of an enrichment rollout include?

Phase one should enrich a few fields that drive one decision, usually routing or scoring, and prove the result. Add contact data, intent and refresh schedules once that holds.

• Name the decision enrichment will support and the fields it needs.
• Clean duplicates and filter junk sources before the first call.
• Test shortlisted providers against a sample of your own records.
• Create enriched fields, Source and Last Enriched Date, plus picklist mappings.
• Set the overwrite policy per field group and the match confidence threshold.
• Sequence enrichment ahead of routing and test with a realistic batch.
• Capture a baseline, launch to one inbound source, then review results with sales.

If you are unsure where enrichment fits in your org, our integration team can review your current setup and design the connection with you.