What is identity resolution?
Identity resolution is deciding that records from different sources refer to the same person or company, and merging them under one identifier. In B2B data it links a LinkedIn URL, an email, a phone and a name to one profile.
Also called: entity resolution · record matching · record linkage
Identity resolution in practice
Every source names people differently. A CRM holds an email, a sign-up form a name, an ad platform a hashed email, a dialer a phone number. Resolution is the step that says these are the same person, so that enrichment, de-duplication and attribution work.
"Entity resolution" is the general term, used for companies and products as well as people. The method is the same: pick keys, match deterministically where a key is exact (a LinkedIn URL, an email), and probabilistically where it is not (a name and a company).
How identity resolution works
- Normalize keysLower-case emails, strip tracking parameters from URLs, format phones to one standard.
- Match exact keysA LinkedIn URL, an email or a phone that both records share is a deterministic match.
- Match fuzzy keysName plus employer plus location is scored; above a threshold it is a probable match.
- Assign one IDThe merged record gets one identifier; every source row points at it.
Deterministic vs probabilistic matching
| Deterministic | Probabilistic | |
|---|---|---|
| Key | Exact: LinkedIn URL, email, phone | Fuzzy: name, employer, title, location |
| Result | Match or no match | A score; a threshold decides |
| Error mode | Misses when keys differ | False merges when names collide |
| Use | First pass | Second pass on what the first pass missed |
Limits and when not to use it
- Common names at large employers collide. A probabilistic match needs a second key before it is trusted for contact data.
- Keys change: a person gets a new work email at each job. Resolution has to re-run as records age.
- Resolution across companies and their subsidiaries is a separate problem; decide which entity you mean before matching.
How identity resolution works with Forager
Forager's person lookup resolves a LinkedIn URL, an email or a phone number to one profile (1 credit per request), reverse email lookup resolves an email to a person (5 credits per request), and every contact lookup takes the person identifier so the channels attach to the same record.
- Person enrichment
- Reverse email lookup
- Recipe: resolve email lists to professional profiles to lift ad match rates
- Docs: reverse phone lookup API reference
- $5 free credits
- No credit card
- Run your sample
Questions about identity resolution
What is identity resolution?
Deciding that records from different sources refer to the same person or company and merging them under one identifier, so that enrichment, de-duplication and attribution work.
Is entity resolution the same as identity resolution?
Entity resolution is the general term for matching any kind of record: people, companies, products. Identity resolution usually means the person case. The methods are the same.
What is the best key for matching a B2B contact?
A LinkedIn URL, because it is unique to one person and does not change with jobs. An email is next. A name plus employer is a fuzzy key that needs a second key to confirm.
How does Forager resolve a record I send?
Person lookup accepts a LinkedIn identifier, an email or a phone number and returns one profile with a person ID for 1 credit per request. Contact lookups then use that ID.
Can I resolve a whole list of emails to profiles?
Yes. Reverse email lookup is 5 credits per request and returns the person behind an email. For large lists, the people data feed lets you match in your own warehouse.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
Related terms
Sources
- Forager docs: person lookup API (read Nov 1, 2026)
- Forager docs: reverse email lookup API (read Nov 1, 2026)