Identity resolution

The problem

Your data is fragmented. One system has an email with no name, another has a phone with no owner, a scrape gave you a LinkedIn URL but no way to call. Each fragment points at a real person, but nothing ties them together, so the records stay half-useful and duplicates pile up.

Matching by hand does not scale, and matching on the wrong field is worse than not matching at all: two people share a name, an old email outlives a job, a recycled phone number now belongs to someone else. Resolution has to start from the fragment you actually hold and end at a person you can verify, not a best guess.

A worked example

Say a scrape left you with a single row: a LinkedIn URL and a name, nothing you can act on. Here is the path from that fragment to a verified, reachable contact.

1. Step 1, confirm the person

   Run the name through the People Finder to pull a full public-record profile. It returns a short candidate set, a shortlist to confirm against, so you match the one whose company and location line up with what you already know and rule out namesakes before going further.

2. Step 2, resolve the channels

   Feed the name and company domain to the Email Finder for a verified business email, and hand the LinkedIn URL to the Mobile Finder for a direct number. Both charge only on a hit, so a fragment that resolves to nothing costs nothing.

3. Step 3, verify before you use it

   Send the resolved email through the Email Validator so you only keep a deliverable address. The row you started with, one URL and a name, is now a named person with a checked email and a mobile you can dial.

What we see teams do to resolve a fragment

These lookups run on our own platform, so we can see how teams turn a scrap of data back into a real person, not just describe it.

• They resolve from whatever fragment they hold. The People Finder turns a bare name, phone, or address into current contact details, so a scrap of data becomes a person you can act on.
• They match against depth. Every fragment is resolved against the 4.6M+ contacts in the lead database, so an orphaned email or phone gets tied back to a current record instead of sitting unusable.
• They treat a lookup as a shortlist to confirm, not a single guaranteed hit. A match returns a candidate set to work against, so teams keep the record whose company and location line up with what they already know and rule out namesakes before reaching out.
• They confirm deliverability before they use it. A resolved email goes through the Email Validator, so it ends as a working contact rather than a bounce.