Identity Resolution

Identity Resolution is the process of matching scattered data points and identifiers to recognize that they belong to the same person or account.

Also known as: identity stitching, profile unification, cross-channel identity resolution

Identity Resolution is the practice of stitching together fragmented pieces of data so that a single individual or organization is represented as one consistent profile. A person might appear as an email address in a webinar tool, a cookie ID on a website, a hashed identifier in an ad platform, and a phone number in a CRM; identity resolution links those signals into one unified record so segmentation, attribution, and personalization can operate against the real person rather than against fragments.

What Identity Resolution Means

Identity Resolution covers both the matching logic that decides which records refer to the same entity and the persistent profile that ties the matched records together. The scope spans person-level resolution (across devices, channels, and authenticated states) and account-level resolution (across subsidiaries, divisions, and the contacts within them). Identity can be deterministic (matched on exact values like email or hashed phone) or probabilistic (inferred from patterns and likelihood). Most modern CDPs, customer data infrastructure tools, and identity-specific platforms (LiveRamp, Treasure Data, ID5) provide identity resolution capabilities, and the warehouse layer increasingly hosts identity stitching directly through dbt models or specialized tools.

How Identity Resolution Works

In practice, Identity Resolution works by comparing identifiers and attributes across records using deterministic matching first — exact email, exact phone, exact account ID — and falling back to probabilistic matching where deterministic links are not available. Each match decision is given a confidence score, and a threshold determines whether records are merged into a single profile, kept as candidates for review, or left separate. The output is a unified profile that lets marketers personalize experiences and measure activity accurately across channels and devices. Survivorship logic decides which attributes from which sources populate the unified profile when multiple sources disagree.

Common Pitfalls and Misconceptions

A practical caution is that Identity Resolution is never perfect and carries privacy weight. Aggressive probabilistic matching can wrongly merge two people who share a name and city, producing personalized experiences delivered to the wrong human. Stretching identity stitching into territory consent rules do not cover — using third-party identity graphs without an appropriate legal basis, for example — creates regulatory exposure. Teams also commonly under-invest in monitoring match quality, treating identity resolution as a configure-once feature rather than a continuously tuned model. Another trap is conflating identity resolution with deduplication; they overlap but differ in scope and intent, and treating them as the same problem produces solutions that handle neither well.

Identity Resolution in Practice

The discipline that distinguishes a sustainable Identity Resolution program from a one-time merge is the audit loop. Every match decision is logged, sampled for accuracy, and reviewed to detect drift in match quality over time. Teams that skip this find out about incorrect merges only when a customer complains or a report looks impossible. Mature programs treat identity as a continuously tuned system where the match threshold, the matching attributes, and the survivorship rules are calibrated against measured outcomes, not configured once and trusted forever. Identity quality decays quietly without that feedback loop, and the consequences appear in every downstream system that depends on the unified profile.

Back to the Glossary

Common questions.

What is the difference between deterministic and probabilistic matching?

Deterministic matching links records when identifiers match exactly, such as the same login email. Probabilistic matching estimates the likelihood that records belong to the same person based on shared attributes and patterns. Deterministic is more accurate; probabilistic provides broader coverage.

How does identity resolution relate to a CDP?

Customer data platforms typically include identity resolution as a core function, using it to merge inbound data into unified profiles. Identity resolution is the engine, while the CDP is the broader system that stores, segments, and activates those profiles.

Why does identity resolution matter for attribution?

Accurate attribution depends on knowing that the same person clicked an ad, visited the site, and later converted. If those touchpoints are not linked to one identity, credit gets split or lost, and reporting understates how channels actually contribute.

Is identity resolution affected by the decline of third-party cookies?

Yes. As third-party cookies disappear, cross-site matching gets harder, pushing teams toward first-party identifiers like authenticated emails and logged-in profiles. This shift makes consented, first-party identity resolution more central than ever.

Can identity resolution merge the wrong records?

It can. Overly loose probabilistic rules may combine two distinct people who share attributes, creating a corrupted profile. Good programs tune match confidence thresholds and include ways to detect and unwind incorrect merges.

What is the difference between identity resolution and deduplication?

Deduplication merges records that represent the same entity within one system. Identity resolution stitches together fragmented data points about the same entity across many systems and channels into a unified profile. Deduplication is a subset of identity resolution focused on the within-system case.

What identifiers are used in B2B identity resolution?

Email address is the most common identifier, often supplemented by company domain, LinkedIn URL, phone number, and behavioral identifiers like cookie IDs or session IDs. B2B identity resolution typically operates at both the individual and account levels, linking contacts to their organizations.

Related Terms

Let’s talk about what your next quarter could look like.

Tell us what you’re working on. A senior practitioner reads it, not an SDR queue, and replies, usually within one business day.

Reviewed personally, not routed through a queue.
A conversation about what you’re actually working on, not a generic pitch.
No pressure, just a chance to talk it through.