Data enrichment
Updated October 21, 2026
Data enrichment is the process of adding missing fields to a record you already hold, such as a contact or a company, using data from outside sources. It turns a partial record, such as a name, an email address or a website, into one you can segment, score and route. Each added field has a cost and an age, so teams enrich the records they plan to act on.
In short: Data enrichment fills the empty fields on a person or company record, such as job title, industry or company size, by matching the record against outside data sources when you need them.
How data enrichment works
Enrichment is a lookup. You send what you know about a record and get back what an outside source knows about it.
The steps are the same in most setups. First you pick a key that points at one record without ambiguity. A LinkedIn profile URL points at one person. A name on its own does not, because many people share a name. Second, the key goes to a data source, which returns a structured record. Third, you map the returned fields onto your own record and decide which values may overwrite what you have. Fourth, you store where and when each value came from, so a later run can tell fresh data from old.
The key you start with decides what you can get back. RichAPI Company enrichment takes one field, a LinkedIn company page URL, and does not accept a domain or a company name 2. RichAPI Profile enrichment requires a LinkedIn profile URL as input 1. To enrich from an email address, you first call the endpoint that finds the LinkedIn URL for that email, then pass the URL to Profile enrichment, which is two calls and two charges 1. The first of those steps is a reverse email lookup.
Enrichment fills in rows you already have. Search and list building create new rows. Lead enrichment is enrichment applied to people, and the company fields it returns are called firmographics. A waterfall is one way to run enrichment, by asking several sources in turn until one returns a value.
When to use data enrichment
Teams enrich at three points. The first is on form fill, so a new inbound lead reaches routing with a title and a company attached. The second is on list import, before the list goes into a sequence. The third is on a schedule, because records age.
Each point has a cost trade-off. Enriching every record in a CRM on every run spends credits on rows nobody will contact. Enriching only at the moment of action spends less, but adds a call between a form fill and the first sales reply. A common split is real-time enrichment for new inbound leads and batch enrichment for older records you plan to contact again.
The legal side follows the data. When you obtain personal data about someone from a source other than that person, Article 14 of the GDPR requires the controller to give them specific information, including the source of the data 3. The deadline is a reasonable period after obtaining the data, and at the latest one month 3. The UK regulator states the same one-month limit for data obtained from other sources 4. Plan that notice before you plan the volume.
Example of data enrichment
A sign-up form on a B2B site asks for a work email and a company LinkedIn page. The team wants industry and company size on every new account, so routing can send larger companies to sales.
The RichAPI Company enrichment reference documents the call they would make 2. The request body has one required field, url, which must be a LinkedIn company page URL 2.
curl -X POST https://api.richapi.ai/api/v1/enrich_company \
-H "x-api-key: $RICHAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.linkedin.com/company/example-co/"}'The documented response is a flat object with name, website, industry, companySize, headquarters, founded, followerCount, specialties, description, logo and linkedinUrl 2. The reference types companySize as a string and advises treating it as a band label, not a headcount integer, until you inspect a live response 2. The routing rule should therefore compare bands, not numbers.
The same reference also shows the limit of this flow. If the form had collected only a website, this endpoint could not use it, because it does not accept a domain or a company name 2. Choosing the input key comes before any field mapping, and it decides which records you can enrich at all.
After the call, the team writes industry and companySize to the account record together with the date of the call. A later run can then refresh only the accounts whose values are older than the limit the team has set, instead of enriching the whole CRM again.
Data enrichment vs data append
The two terms overlap, and vendors use them loosely. In this glossary, data append means adding one field type to many rows, such as phone numbers to a list of emails. Data enrichment means filling a record with the fields a source returns for it. The difference shows up in how a job is scoped and paid for. An enrichment job is scoped per record, so the question is which records deserve a lookup. An append job is scoped per column, so the question is which field the list is missing. Both depend on a reliable match key, and a weak key writes wrong values in either case. The table sets out the practical differences.
| Data enrichment | Data append | |
|---|---|---|
| What it answers | What else is known about this record? | What is the value of this one field for each row? |
| Input | One identifier per record, such as a profile or company URL | A list plus the field to add |
| Output | A structured record with many fields | The same list with one new column |
| Cost driver | Records enriched | Rows processed |
| Main risk | Stale fields that look complete | Wrong matches written into one column |
| Use it when | You act on individual records, such as inbound leads | You prepare a list for one channel, such as phone outreach |
Frequently asked questions
What is data enrichment in a CRM?
In a CRM, data enrichment fills empty fields on contact and company records, such as job title, industry and company size, from an outside source. It can run when a record is created and again in batches on older records, so routing and scoring rules have the fields they need.
How much does data enrichment cost?
It depends on how the source bills. At RichAPI, Profile enrichment costs 1 credit per call, or 2 with social metrics, and Company enrichment costs 1 credit per call 1. Both bill on any 2xx response, including one that returns few fields 1.
Is data enrichment the same as lead generation?
No. Lead generation finds people or companies you do not have yet. Data enrichment adds fields to records you already hold. The two often run in sequence, with a search step that creates new rows and an enrichment step that fills them in before outreach.
Do I need to tell people when I enrich their personal data?
Usually yes, under the GDPR 3. Article 14 says that when personal data comes from a source other than the person, the controller must give them specific information, at the latest within one month 3. Article 14 also lists exceptions, so check your case with counsel 3.
The bottom line
Data enrichment adds fields to records you already hold, using an outside source and a key that points at each record. It does not find new prospects, and it does not keep data fresh on its own. Pick the input key first, enrich at the moment you act, and store a source and a date with every field you add.
Sources
- RichAPI llms-full.txt (catalog and billing rules), RichAPI
- How to turn a LinkedIn company page into a company record, RichAPI
- Art. 14 GDPR, Information to be provided where personal data have not been obtained from the data subject, gdpr-info.eu (text of Regulation (EU) 2016/679)
- The right to be informed, Information Commissioner's Office (UK)