What Is Contact Data Enrichment?
Contact data enrichment starts with a person identifier and returns structured data about that person. The input is typically a first name, last name, and company domain. The output is a verified email address, phone number, job title, seniority, department, and LinkedIn URL.
Use cases include sales prospecting (finding the right contact at a target company), CRM enrichment (filling in missing fields on existing lead records), and outreach personalization (understanding seniority and department before reaching out).
Contact enrichment differs from company enrichment. Company enrichment returns organization-level data from a domain. Contact enrichment operates at the person level and requires at least a name and company to work from.
What Data Points You Get
A contact enrichment response includes some or all of the following fields, depending on data availability:
- email - Verified work email address
- mobilePhone - Mobile phone number (lower coverage than email)
- directPhone - Direct office line, where available
- jobTitle - Current job title (e.g., "Head of Growth")
- seniority - Seniority level (e.g., "Director", "VP", "C-Suite")
- department - Department (e.g., "Sales", "Engineering", "Finance")
- linkedinUrl - LinkedIn profile URL
Example API response:
POST /v1/contact/enrich
{
"firstName": "Jane",
"lastName": "Smith",
"domain": "stripe.com"
}
Response:
{
"email": "jane.smith@stripe.com",
"emailVerified": true,
"mobilePhone": "+1-415-555-0142",
"jobTitle": "VP of Sales",
"seniority": "VP",
"department": "Sales",
"linkedinUrl": "https://linkedin.com/in/janesmith"
} Email Verification vs Email Finding
These are two different operations that are often confused:
Email finding is the process of discovering what a person's email address likely is. Most providers guess using company email patterns: if the domain is stripe.com and other employees follow firstname.lastname@stripe.com, the algorithm guesses that pattern for the new contact.
Email verification checks whether a found email address actually exists and can receive mail. Verification typically checks syntax, domain MX records, and the mailbox itself (without sending a real email).
DataMerge does both. We find the email address using pattern matching across multiple providers, then verify deliverability before returning it. An email returned with emailVerified: true has passed all three checks. Bounce rates on verified emails run under 2%.
Why Phone Number Coverage Is Lower Than Email
Most enrichment providers return phone numbers for 20-30% of contacts, compared to 60-80% for emails. This gap exists for a few reasons.
Work email addresses are semi-public. They appear in email signatures, on conference speaker lists, on company websites, and in public correspondence. Mobile numbers do not. People guard personal mobile numbers much more carefully than work emails.
Phone data also degrades faster. People change jobs and keep their mobile numbers, but the number gets associated with a new employer. Databases that rely on historical data end up with high rates of stale phone associations.
DataMerge's waterfall approach helps here. By querying multiple providers and returning the most recent match with the highest confidence, we maximize find rate beyond what any single provider can achieve. For contacts where phone coverage is critical, the waterfall is the best available approach short of direct outreach to verify.
How to Use It
You can enrich contacts by email (if you already have it) or by name and domain (if you are prospecting). Both approaches are supported:
// Enrich by known email
POST /v1/contact/enrich
{ "email": "jane@stripe.com" }
// Enrich by name + domain (prospecting)
POST /v1/contact/enrich
{
"firstName": "Jane",
"lastName": "Smith",
"domain": "stripe.com"
} The name-plus-domain approach is useful when building prospect lists. You find a company you want to target, identify who you want to reach (from LinkedIn, a company page, or any other source), and send their name and the company domain to DataMerge to get their verified contact details.
Full documentation: api.datamerge.ai/docs
Frequently Asked Questions
What is contact enrichment?
Contact enrichment is the process of taking a person identifier (name and company domain, or a known email) and returning structured contact data: verified email, phone number, job title, seniority, department, and LinkedIn URL.
What is a verified email vs an unverified one?
An unverified email is a guessed or found email address that has not been checked against the mail server. A verified email has passed syntax, domain, and mailbox checks. DataMerge returns emails with an emailVerified flag. Verified emails have bounce rates under 2%. Unverified emails may bounce 20-40% of the time.
What is the find rate for emails vs phone numbers?
Email find rates typically run 60-80% for well-represented companies and contacts. Phone number coverage is lower, usually 20-40% across providers. DataMerge's waterfall improves on single-provider rates by querying multiple sources and returning the best match.
Can I enrich contacts without a known email address?
Yes. The name-plus-domain endpoint accepts a first name, last name, and company domain. DataMerge infers and verifies the likely email address from company email patterns and returns a verified result. No prior email required.
What is seniority data used for?
Seniority data tells you where in the org hierarchy a person sits: individual contributor, manager, director, VP, or C-suite. Sales teams use it to prioritize outreach (targeting decision-makers first), segment campaigns by level, and route leads to senior or junior AEs based on the contact's seniority.
How do I enrich a list of leads from a CSV?
Export your CSV with columns for first name, last name, and company domain. Use the DataMerge batch API endpoint to submit the list in bulk. Results are returned as a structured JSON array. You can then reimport the enriched data back to your CRM or spreadsheet.
What integrations does DataMerge support for contact enrichment?
DataMerge exposes a standard REST API that works with any HTTP-capable integration layer. Common setups include direct API integration, Zapier or Make automations, Clay workflows, and custom scripts. There is no native CRM plugin yet, but the API connects to Salesforce, HubSpot, and others via webhooks or automation platforms.
How often is contact data refreshed?
DataMerge pulls from live upstream providers on each request, rather than serving cached data from a fixed snapshot. This means the data is as fresh as the underlying providers, which varies by source. For legal name and company data, live domain checks are performed in real time.
