What is B2B data enrichment? A guide for builders
What B2B data enrichment is, the people and company fields you can add, how enrichment works over an API, and how to run it on your own lists.
Dag Holmen · Updated · 5 min read
Data enrichment is adding the fields you're missing to records you already have. You start with something small, like a LinkedIn URL, a name and a company domain, or just a domain. An enrichment source sends back the rest: the person's title and company, or the company's industry, size, revenue range and location.
In B2B, the records are people and companies, and for builders the work happens in code. An identifier goes in, a structured record comes out, and you decide where it lands. This guide covers what you can enrich, how it works over an API, and how to run it on your own lists without making a mess of them.
People enrichment and company enrichment
There are two kinds of B2B data enrichment, and most pipelines use both.
People enrichment (also called contact or lead enrichment) starts with an identifier for a person and returns a profile: full name, job title, company, company domain, location, and the company's industry and size. The strongest identifier is a LinkedIn profile URL. A first name, last name and company domain is the next best, and it's also how you find a work email. The people enrichment API guide covers both.
Company enrichment starts with a domain, a LinkedIn company URL or a LinkedIn company ID and returns firmographics: name, description, industry, headquarters city, state and country, employee range, revenue range and LinkedIn URL. The company enrichment API guide goes field by field.
Before and after: an example
A demo request comes in with a name and a company website. Here's the record before, and after a company call, a contact lookup and an email lookup.
| Field | Before | After |
|---|---|---|
| Name | Maya Chen | Maya Chen |
| Website | acme.com | acme.com |
| Work email | (empty) | maya.chen@acme.com |
| Job title | (empty) | VP Marketing |
| Industry | (empty) | Software Development |
| Employees | (empty) | 201-500 |
| Revenue range | (empty) | $25M-$50M |
| Headquarters | (empty) | Austin, United States |
The data in that row is fictional, but the shape is real. Two fields in, eight fields out, before anyone on your team opens the record.
How data enrichment works over an API
The pattern is the same for every endpoint:
- You send an identifier in a POST request, with your API key in the
X-Api-Keyheader. - The API looks it up and returns a JSON record, or tells you it found nothing.
- Your code writes the fields you want to your CRM, database, spreadsheet or table.
Here's a company lookup from a domain.
curl --request POST \
--url https://api.b2benrich.com/v1/enrich/companies/domain-to-company \
--header 'Content-Type: application/json' \
--header 'X-Api-Key: YOUR_API_KEY' \
--data '{ "input": "acme.com" }'
The response carries a status, the B2Benrich company_id and the company record in data. Trimmed, with fictional values:
{
"status": "found",
"company_id": "123456",
"data": {
"name": "Acme",
"domain": "acme.com",
"industry": "Software Development",
"employees_range": "201-500",
"revenue_range": "$25M-$50M",
"hq_city": "Austin",
"hq_country": "United States"
}
}
It's a plain REST API, so it works from any language, a script, a workflow tool or an AI agent that can make an HTTP request.
Enrichment vs search
Enrichment answers "tell me more about this record." Search answers "find me records that match these filters." If you already have the people or companies, enrich them. If you need new ones, search first (by job title, company, industry, size or location) and then enrich what comes back. The two work together: search gives you the list, enrichment fills in each row.
Where teams use enrichment
- Inbound routing. Enrich every sign-up or demo request by domain. Route on employee range and industry before a human looks at it.
- CRM cleanup. Fill blank fields and catch people who changed jobs. CRM data enrichment walks through doing this in HubSpot or Salesforce without overwriting good data.
- Completing a list you were handed. An event list with names and companies becomes a list with titles, domains and work emails.
- Product personalization. Enrich new accounts in the background so onboarding can adapt to the company's size and industry without a long sign-up form.
Data enrichment techniques
Enrich on entry. Trigger a call the moment a record is created: form fill, sign-up, CRM import. The record is complete before it reaches anyone.
Backfill. Run your existing records through once. Export, dedupe, enrich, write back.
Re-enrich on a schedule. People change jobs and companies grow, so data you enriched last year has drifted. How often you refresh is your call. A sensible default is to refresh lists right before you work them, and the rest of the database less often.
Waterfall your identifiers. Try the strongest identifier first and fall back. For people: LinkedIn URL, then first name, last name and domain. For companies: domain or LinkedIn company URL, and only then the company name.
Pitfalls to avoid
- Dirty inputs. Strip
https://,www.and paths from domains, and query strings from LinkedIn URLs. Dedupe before you call, not after. - Ignoring not-found. "No match" is a result. Store it with a date so your job doesn't retry the same record every night.
- Mixing raw and enriched data. Keep the original value next to the enriched one, plus an
enriched_attimestamp. You'll want both when you re-enrich. - Overwriting people. If a rep edited a title by hand, don't let a script replace it. Fill blanks by default and flag conflicts.
- Sending to unchecked emails. A found email isn't the same as a deliverable one. Run it through an email verification API before it goes into a sequence.
Choosing a data enrichment API
Test any provider on a sample of your own records, ideally ones where you already know the right answer. Check how many come back, whether the titles match what you know, and how the API reports misses. Ask when a record was last checked, not just how big the database is. Then look at the pricing model. Per-record credits push you to ration enrichment, which is the opposite of what a clean database needs. B2Benrich is one plan: unlimited API usage for $500 a month, no credits. Enriching your whole CRM costs the same as enriching a hundred rows.
Frequently asked questions
- What is data enrichment in simple terms?
- It’s adding missing information to records you already have. You start with an identifier like a LinkedIn URL or a company domain, and an enrichment source returns the rest: job title, company, industry, size, revenue range and location.
- What is a data enrichment API?
- An API you send an identifier to, such as a domain or a LinkedIn profile URL, that returns a structured record as JSON. You call it from your own code or workflow tool and write the fields wherever you need them, like a CRM, a database or a spreadsheet.
- What’s the difference between data enrichment and data cleansing?
- Cleansing fixes or removes what’s wrong in your data: duplicates, typos, bad formats. Enrichment adds what’s missing from an outside source. Most teams clean first, so they don’t pay the cost of enriching duplicates or broken domains.
- How often should you re-enrich B2B data?
- There’s no fixed rule. People change jobs and companies change size, so data drifts all the time. A practical approach is to re-enrich a list right before you work it, and refresh the rest of your database on a slower schedule you set yourself.
- Is contact enrichment the same as lead enrichment?
- It’s the same process with a different label. Lead enrichment usually means enriching new inbound leads as they arrive. Contact enrichment usually means keeping existing CRM contacts up to date. Both use the same people enrichment endpoints.
Related guides
- People enrichment API: from a LinkedIn URL to a full profileHow a people enrichment API works, which fields come back, and how to enrich contacts from a LinkedIn URL, a name and domain or an ID.
- Company enrichment API: firmographics from a domainTurn a domain, LinkedIn URL or LinkedIn ID into a company record: industry, size, revenue range, location and tech stack, over one API call.
- CRM data enrichment: keep HubSpot and Salesforce records completeHow to fill missing fields and fix stale records in HubSpot or Salesforce with an enrichment API, on new leads and on your whole database.