Domain → Page → Contacts · match on the page, not on the domain

Lead to account matching on the company page

The short answer

Lead to account matching links each new lead to the account it belongs to in your CRM. Matching on the email domain fails on personal addresses, country domains, subsidiaries and companies whose email domain differs from their website. Store each account's LinkedIn company ID, resolve each lead's email to the person's current employer page, and match the two.

Updated
Read
4 min
Clip
0:29
On this page6 sections
  1. What is lead to account matching?
  2. Why does lead to account matching on email domains fail?
  3. How does lead to account matching work with the company page?
  4. Why does only the current job count?
  5. How do you resolve a lead’s email to an account with the API?
  6. Sources and method
From the explainer Domain to Page to Contacts: why we use two API calls, 2:51 to 3:20.

A new lead fills in a form with a work email. Before anyone calls, your CRM has to decide which account that lead belongs to. Most setups decide on the email’s domain. It is the same shortcut the guide on how to find employees of a company from its domain takes apart, run in the other direction: from a person to a company.

What is lead to account matching?

Lead to account matching is the step that links a new lead to the company account it belongs to in your CRM.

Definition Lead to account matching also called lead-to-account matching
Linking each new lead to the company account it belongs to in your CRM, so it reaches the right owner and the right deal.

PreciselyLead to account matching assigns a lead to an existing account. Matching on the email domain fails on personal addresses, country and alias domains, subsidiaries, and companies whose email domain differs from their website. Matching the LinkedIn company ID of the lead's current employer, resolved from the email, against the ID stored on each account avoids those cases.

That step decides who owns the lead, how it is routed, how it is scored, and whether it joins a deal already in progress. When it fails, leads go to the wrong rep, wait in a queue nobody owns, or open a second account for a company you already work with.

Why does lead to account matching on email domains fail?

Because the domain in an email and the domain on an account are two different facts, and they disagree more often than it seems:

  • No accountA personal address carries no company
  • No accountThe account is filed under doctolib.fr
  • No accountThe account holds the website, news.microsoft.com
  • A second accountA subsidiary’s domain opens a new company
Four leads, four domain lookups, no reliable match. None of them raises an error.Watch this moment 2:51
  • Personal addresses carry no company. A gmail.com address matches nothing, or matches every lead that ever used Gmail.
  • Country and alias domains. A lead writing from doctolib.de misses an account filed under doctolib.fr.
  • The email domain is not the website. Microsoft’s page lists news.microsoft.com as its website, and its people write from microsoft.com. An account keyed on the website never sees them.
  • Subsidiaries write from their own domains. A lead from a company your account owns opens a second account under the subsidiary’s domain.

Every one of these fails quietly. The lead is routed somewhere, just not to the right place.

The domain in an email and the domain on an account are two different facts.

How does lead to account matching work with the company page?

Here is how to match leads to accounts so that it holds: both sides get the same key, the company page of the employer, written as its LinkedIn company ID. Three steps:

  1. Give every account its company ID, once. Resolve each account’s domain with Domain to LinkedIn, check the name, and store the page and its ID with Company Enrichment.
  2. Resolve each lead’s email to the person. Reverse Email Lookup returns the person behind the address and their career, each job with the company ID of its page.
  3. Match on the current job. Take the job where job_is_current is true, and compare its company ID with your accounts. Equal IDs, same company.
s•••••••@figma.com
Reverse Email LookupCurrent jobFigmaID 3650502Past jobMicrosoftID 1035 · ignored
The real match, run on November 10, 2026: the current job carries Figma's ID, and so does the account. The past job is ignored.Watch this moment 2:51

When no account carries the ID, you learn something useful: either a new company, or a person who moved from an account you know. Both are visible, instead of a lead silently attached to the wrong account. Once the lead is matched, routing it to the right owner is the next step, and the CRM hygiene use case applies the same key to cleaning the accounts themselves.

Why does only the current job count?

Because the career is not the account. A reverse email lookup returns every position the person held, and in the run above, the same person had worked at Microsoft years before joining Figma. A match on any job in the career would attach the lead to both. Keep the current job, and keep the past ones for what they are: a sign that someone who knew your product at one account now works at another.

For builders

One endpoint resolves the lead; the accounts carry the ID from the earlier steps. This part shows the call with a real run.

How do you resolve a lead’s email to an account with the API?

POST/v2/enrichment/email-to-personAPI reference

An email address in, the person behind it out, with every job and the company ID of each.

Send

email
The full address the lead gave you. A partial address does not match.

Read

found, person
The person, or found: false when no one matches.
person.experiences[]
The whole career: company_linkedin_url, company_linkedin_id and job_is_current for each job.

Each person found is one record; plans and rate limits are on the BlitzAPI pricing page.

A real run

On November 10, 2026, we looked up the work email of a Figma director, masked here. The response, trimmed to two of the person’s jobs, without the job titles:

{
  "found": true,
  "person": {
    "experiences": [
      {
        "company_name": "Figma",
        "company_linkedin_id": "3650502",
        "job_is_current": true
      },
      {
        "company_name": "Microsoft",
        "company_linkedin_id": "1035",
        "job_is_current": false
      }
    ]
  }
}

The account for Figma holds 3650502: the lead belongs to it. Microsoft’s 1035 is a past job and stays out of the match.

Before you ship

  • Backfill the company ID on every account first, from its domain, with a name check.
  • Match on company_linkedin_id from jobs where job_is_current is true. A person can hold two current jobs: route by the one that matches an account.
  • Route unmatched leads to review with the employer the lookup found, instead of creating an account from the email domain.
  • Matching on any job in the career: past employers are not the lead’s account.

Sources and method

Published
API calls run on

The four leads in the first diagram are illustrative and masked; the domain cases behind them (Microsoft's website and email domain, Doctolib's country domains) were read with the BlitzAPI API on November 10, 2026 and in matching tests run on October 11, 2026.

The BlitzAPI team ran the reverse email lookup in the second diagram and in the builders section on November 10, 2026. The person is described by job title only and the address is masked.

Questions this raises

What is lead to account matching?

Lead to account matching is the step that links a new lead, usually a person with an email address, to the company account it belongs to in your CRM. It decides who owns the lead, how it is routed and scored, and whether it joins an existing deal. Most tools match on the email domain, which works until the domain and the account disagree.

Why does lead to account matching on email domains fail?

Because a domain is a weak key. Personal addresses carry no company, country and alias domains differ from the one on the account, subsidiaries write from their own domains, and many companies send email from a domain that is not their website. Each case leaves a lead unmatched or opens a duplicate account, and none of them raises an error.

What is the best key for lead to account matching?

The LinkedIn company ID of the company the person works for now. Store it on each account once, from the account's domain, then resolve each lead's email to the person and their current job, which carries the ID of the employer's company page. Two equal IDs mean the same company, whatever domains are involved.

Can you match a lead with a personal email address to an account?

Only if the address can be tied to a person. A reverse email lookup returns the person and their career when it recognizes the address, and the current job then gives you the employer's company page. When the address cannot be resolved, keep the lead unmatched and ask for a work email rather than guessing an account.

Data shouldn't be
the problem

Grab. Connect. Build.