Glossary · Data and enrichment

What is data enrichment?

The short answer

Data enrichment is the process of adding missing information to records you already have, using an outside source. In B2B, a row with only a company domain comes back with the company's name, industry, size, location and email provider, and a contact's profile link comes back with their role and verified work email.

Updated
Read
3 min
Written by
Antoine Blitz
On this page8 sections
  1. Real data
  2. How does data enrichment work?
  3. What can data enrichment add to a B2B record?
  4. Why do records need to be enriched again?
  5. Data enrichment, data cleansing and waterfall enrichment: what is the difference?
  6. How do you enrich data with an API?
  7. Related terms
  8. Questions people ask

Real data

A CRM row before and after enrichment

Figma, starting from a CRM row that holds one field: the domain figma.com. Three calls fill in the rest.

Returned by the BlitzAPI API on

POST/v2/enrichment/domain-to-linkedin

Step 1: from the domain to the company

Before
figma.com, and nothing else
Company
Figma
Company page
linkedin.com/company/figma

The same call also returned other company pages that list figma.com as their website, such as user communities, in a separate field: telling them apart is part of the job.

POST/v2/enrichment/company

Step 2: the company record

Industry
Design Services
Size band
1,001–5,000 employees
Employees on LinkedIn
3,013
Founded
2012
Headquarters
San Francisco, California, United States
Email provider (MX)
Google (aspmx.l.google.com)
POST/v2/jobs/company

Step 3: current hiring

Job postings
113

Read from total_results: the postings Figma published in the 30 days through October 28, 2026.

How does data enrichment work?

Data enrichment takes an identifier your record already holds, matches it to the right company or person in an outside source, and appends the fields you asked for. The match is the hard part: a domain can be claimed by several company pages, and a name by thousands of people.

  1. Start fromAn identifier you holdA company domain, a company or profile URL, or an email address
  2. MatchThe right entityThe one company or person the identifier points to, in the source
  3. AppendThe fields you asked forEach with the value the source holds on the day of the call
Every enrichment runs the same three steps; the second one decides whether the facts you add belong to the right record.

The Figma example above runs those steps on a CRM row that held only a domain. One call matches the domain to the company, a second returns the company record, a third counts its open job postings.

What can data enrichment add to a B2B record?

Data enrichment can add four kinds of data to a B2B record, each from its own starting point:

Kind of data Examples Typical starting point
Company data Industry, size, headquarters, founding year, email provider A domain or a company page
People data Current role, seniority, employer, work history A profile URL or a work email
Contact data Verified work email, direct phone number A profile URL
Signals Open job postings, tools named in them A company page

Company data on its own has a name in the glossary: firmographic data. The tools a company uses are its technographic data.

Why do records need to be enriched again?

Records need to be enriched again because the facts they hold change while they sit in the CRM. People change jobs and titles, companies hire, move, merge and rebrand, and email addresses stop working when someone leaves. An enriched record is true on the day of the call; after that, it drifts. That is why enrichment runs twice: once when a record enters the CRM, and again on a schedule.

Data enrichment, data cleansing and waterfall enrichment: what is the difference?

Data enrichment adds what a record is missing, cleansing fixes what it already holds, and waterfall enrichment asks several sources in turn for the same missing field.

What it does When it runs
Data cleansing Fixes what is already there: duplicates, typos, formats Before matching; often a one-off project, sometimes on a schedule
Data enrichment Adds what is missing, from an outside source When a record enters the CRM, and on a schedule
Waterfall enrichment Asks several sources in turn for the same missing field When one source alone does not find the field

Which is which?

Five jobs on the same CRM. Which one is each?

  1. Adding industry, size and headquarters to a list of domains

  2. Merging two contacts that turn out to be the same person

  3. Asking a second source for the work emails the first one did not find

  4. Rewriting "VP, Sales" and "Vice President Sales" as one title

  5. Getting a contact's current role from their profile link

Show the answers
  1. Adding industry, size and headquarters to a list of domainsEnrichmentNew facts come from an outside source and are added to rows you already hold.
  2. Merging two contacts that turn out to be the same personCleansingNothing new comes in: the fix works on what the CRM already holds.
  3. Asking a second source for the work emails the first one did not findWaterfallThe same missing field, asked of several sources in turn until one finds it.
  4. Rewriting "VP, Sales" and "Vice President Sales" as one titleCleansingStandardizing a format fixes values that are already there.
  5. Getting a contact's current role from their profile linkEnrichmentAn identifier you hold brings back a fact you did not have.

How do you enrich data with an API?

Enriching data with an API takes one call per identifier, from wherever the records live: a CRM, a spreadsheet, a workflow tool such as Clay or n8n, or an AI agent.

Company Enrichment turns a company page into a full record, Email Enrichment returns a verified work email from a profile URL, and the profile enrichment use case shows how the calls chain on a contact list. Each call returns structured JSON, so the fields land in your own columns without manual work.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on October 28, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests.

Industry and size band are the labels the company publishes on its own page, shown as returned.

Questions people ask

What is the difference between data enrichment and data cleansing?

Cleansing fixes what is already in your records: duplicates, typos, outdated values, inconsistent formats. Enrichment adds what is missing, from an outside source: industry, headcount, role, verified email. A CRM routine usually does both: clean first so that records match correctly, then enrich, then refresh on a schedule.

What data can you add to a B2B record?

Company data (industry, size, location, founding year, email provider), people data (current role, seniority, work history), contact data (verified work email, direct phone number) and signals (hiring activity, technology use). Each comes from a call keyed on what the record already holds: a domain, a profile URL or an email address.

How often should CRM data be enriched?

Once when a record enters the CRM, then on a schedule, because people change jobs and companies move, grow or rebrand. Records in active deals and target accounts deserve a monthly refresh; the rest of the database can follow a quarterly cycle.

What does lead enrichment mean?

Data enrichment applied to inbound leads: a form submission with a name and a work email comes back with the person's role and company, so the lead can be scored and routed without asking for more fields. A reverse email lookup does it from the email address alone.

With BlitzAPI

Put it to work

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

From the domain to the company

curl -X POST https://api.blitz-api.ai/v2/enrichment/domain-to-linkedin \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"figma.com"}'

API reference

The company record

curl -X POST https://api.blitz-api.ai/v2/enrichment/company \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company_linkedin_url":"https://www.linkedin.com/company/figma"}'

API reference

Current hiring

curl -X POST https://api.blitz-api.ai/v2/jobs/company \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_linkedin_url": "https://www.linkedin.com/company/figma",
    "job": {"date_posted": {"last_days": 30}},
    "max_results": 1
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.