Frequently asked questions
What does identity resolution solve?
The problem of multiple records, signals, and data points pointing to the same person or company. Without it, you treat one buyer as three leads and three companies as one account. With it, the picture stays clean as data flows in.
How is identity resolution different from deduping?
Deduping is reactive. You find duplicates after the fact and merge them. Identity resolution is proactive. Incoming data is matched to existing records at write time. The first is a cleanup job; the second is infrastructure.
What identifiers does identity resolution rely on?
For people: email, LinkedIn URL, name + employer pair, sometimes phone. For companies: domain, legal name, employer ID. The harder cases need fuzzy matching across multiple signals; the easy cases just need a clean primary key.
What breaks identity resolution most often?
Job changes (person moves, all signals point to old company) and rebrands (company changes name, no new signal to connect old to new). Both are solvable with active monitoring; both surprise teams that assumed identity resolution was done once.
Does Landbase handle identity resolution?
Yes. Incoming signals and data points get matched to canonical account and person records before they're scored. The CLI lets you inspect the match logic per record so you can debug edge cases.
.png)
.png)