What is identity resolution?

In practice, identity resolution stitches together fragments of behavior that would otherwise look like separate strangers: a visit from a work laptop, a click on an ad from a phone, a form fill(opens in a new tab) from a home network. Marketing and sales teams use it to answer a basic question about every new visitor: is this someone the company already knows, or someone who has already shown interest, and if so, who exactly. Get that answer wrong and a sales team either chases a stranger or misses a buyer already circling the deal. The matching happens two ways, deterministic and probabilistic, and the mix between them says more about the quality of a vendor's output than the length of its list does.

Deterministic matching versus probabilistic matching

Deterministic identity resolution relies on a known identifier: a logged-in session, a CRM(opens in a new tab) record, or a hashed email match confirmed by a data provider. Because the match traces back to something the person entered or owns, it counts as verified. Probabilistic identity resolution infers a likely match from patterns such as a shared IP address, a device fingerprint, or overlapping browsing windows, and outputs a confidence score instead of a certainty.

The distinction sounds academic until a rep is staring at a lead list and has to decide which names are worth a call. Deterministic matches are the ones they can dial without checking. Probabilistic matches need a second look first. Most vendors blend both, so ask for the ratio before you trust the headline match rate.

Identity resolution versus de-anonymization

The two terms describe the same process from different angles. De-anonymization names the outcome: an anonymous visitor turned into a known identity. Identity resolution names the mechanism, the matching logic that produces it. Cookie tracking is one input to that mechanism, alongside hashed emails, device IDs, and CRM records, which is why a resolved identity survives a cleared cookie or a new device when a cookie alone would not.

Why identity resolution matters for go-to-market teams

Identity resolution turns anonymous website traffic into a workable list of real people and the accounts they belong to. A team without it sees traffic spikes and bounce rates. Add it, and the same report shows that three people at a target account(opens in a new tab) visited the pricing page(opens in a new tab) this week, which is the difference between an analytics dashboard and a sales trigger.

That is also where it sits in an ABM(opens in a new tab) program. Inside an ABM platform like Vector, identity resolution is one input to the Find stage: it supplies the named people behind account activity, and the account they belong to gets staged against evidence the team can inspect.

Account-level identification versus contact-level resolution

Account-level identification answers one question: which company is this traffic from? Nearly every vendor in the category can name the company behind a visit. Contact-level(opens in a new tab) identity resolution asks who inside that company is engaging, and turns a company name into a named buying committee(opens in a new tab) member a team can put in front of an ad or hand to a rep. The two answers do different jobs. Accounts tell you where to look. People tell you what to do.

Where identity resolution runs into trouble

Cross-device matching gets harder every year as browsers restrict third-party cookies and IP addresses get shared across a household or a coworking space. Privacy regulation limits what can be resolved and how long it can be stored. Match rates vary widely with the data sources a vendor can access. A resolution rate quoted without context, with no baseline traffic volume and no split between deterministic and probabilistic matches, reads impressive and means little. Ask for that split before trusting the headline rate.