Identity Resolution

What is Identity Resolution?

Identity Resolution sets the foundation for a single-customer view. Identity resolution works by linking customer touchpoints to their customer profile, these are aptly named “links”. By mapping different datapoints into one customer profile, segmentation and insights become possible across the entire MarTech stack.

“Identity Resolution” is a data workflow, whereas the “Single-Customer View” is the output in Lexer’s Understand tool and allows you to activate to different marketing channels.

1896

Problem and pain points

Let’s start with the problem: fragmented data that arises from multiple systems supporting customer experience.

For example, imagine a scenario where a customer was receiving messages from two different marketing campaigns. On Monday the customer receives an email promoting outdoor jackets for outdoor activity, on Wednesday they get a notification for streetwear ensembles. These messages could conflict and prevent conversion: how could this happen?!

A common source of this discrepancy is that the same customer profile actually lives in two segments. Data from two systems, such as ecommerce and email, form the basis of a customer profile, but without resolution these profiles aren’t unified.

This impacts customer experience and also limits progress in the marketing program because it erodes trust. With a low trust in data, it can become difficult to commit to plans, the cycle of learning from campaigns slows down and the whole marketing program can stall.

How it works

Identity Resolution framework

The workflow to Identity Resolution has five steps:

  1. Collect: Lexer connects to customer-facing systems, via integration or solution design, and acquires data into our secure environment.
  2. Clean: The data is then processed so that each record meets data type specifications — i.e. email and mobile formats.
  3. Links: Relationships are discovered between profiles and touchpoints.
  4. Resolve: A profile of the customer is now formed from linked records.
  5. Deploy: A single-view of customer is made available for personalization through attribute calculation, segmentation, and activation.
Note
It can be important to spend some time at step three to ensure that the selected linkage configuration matches the business logic.
1895

Concepts

Here’s a set of terms you’ll see a lot when exploring this topic. This glossary pulls together the Lexer definition of these terms.

Identity Resolution

Identity Resolution is the process of linking records of a person to form a “Single-Customer View” (SCV). An accurate SCV is crucial for powerful segmentation and personalized messaging. Broadly there are two approaches to unification: deterministic and probabilistic.

The deterministic approach trusts the identifiers (such as email, and customer_id) to represent a person and link the records.

The probabilistic approach is more complex but can overcome poor data quality to find links between records.

Identity Resolution is otherwise known as unification, deduplication and stitching. It’s also a more specialized implementation of Record Linkage in that it focusses on people instead of other entities.

Graph

A graph is a useful data structure for representing relationships between records. In this case, we are using a graph to represent the relationships between customers. If you’ve ever played Six Degrees of Kevin Bacon, you’ll understand the concept of a graph. Just replace “movies” starring Kevin Bacon with “customers” buying t-shirts and opening emails and you’ve got a Single-Customer View.

Touch-point

An interaction with a customer such as an in-store purchase, email click or a website login. These are otherwise known as interactions, events, or observations.

Identifier

A datapoint in a profile that directly (deterministically) or indirectly (probabilistically) can be found in another profile or touch-point. A high-confidence identifier will uniquely link to only one customer profiles.

Good examples of identifiers are:

  • Customer ID assigned by a Point of Sale system or CRM
  • System ID assigned by a commerce or marketing application such as Shopify or Klaviyo
  • Email Address provided by the customer at the time of signup, although shared email addresses are common

Examples of identifiers that have linkage with less confidence include:

  • A mobile phone number
  • A web browser or cookie
  • A household address

Link

A link represents a relationship between one or more profiles (entities) or touchpoints (events). A deterministic link is a shared datapoint such as a customer’s email address or customer ID.

Deterministic Identity Resolution

The simplest kind of identity resolution, called deterministic or rules-based record linkage, generates links based on the number of individual identifiers that match among the available data sets. Two records are said to match via a deterministic record linkage procedure if all or some identifiers (above a certain threshold) are identical. Deterministic record linkage is a good option when the entities in the data sets are identified by a common identifier, or when there are several representative identifiers (e.g. name, date of birth, and sex, when identifying a person) whose quality of data is relatively high.

Probabilistic Identity Resolution

Probabilistic record linkage, sometimes called fuzzy matching takes a different approach to the record linkage problem by taking into account a wider range of potential identifiers. For each pair of identifiers between records a model estimates a match or a non-match, and using these weights to calculate the probability that two given records refer to the same entity. Record pairs with probabilities above a certain threshold are considered to be matches, while pairs with probabilities below another threshold are considered to be non-matches. Pairs that fall between these two thresholds are considered to be "possible matches" and can be dealt with accordingly (e.g. human reviewed, linked, or not linked, depending on the requirements). Probabilistic identity resolution is also called probabilistic merging or fuzzy merging.

Defining Success

Success in Identity Resolution means finding the best links between profiles and interactions for a customer profile.

To reach this objective and get linkage just right, we need to solve for two cases — finding too many links (over unification) or too few links (under unification).

Over unification

Over unification is where profiles are merged that should actually be distinct. At the worse case the identity graph can collapse and see many identities against a single profile. Factors leading to over unification include low data quality or spurious input such as false addresses like test@test.com.

To protect against over unification Lexer implements link occurrence thresholds and term frequency analysis. For data that may not have sufficient linkage quality Lexer also supports appending attributes to profiles after resolution has occurred.

Under unification

Under unification occurs when valid links do not match due to a mismatch in formatting. Lexer deploys rich data type specifications to clean and normalize data to maximize the linkage opportunity.

Identity Resolution recap

Lexer's Identity Resolution sets the foundation for a single-customer view and works by linking customer touchpoints to their customer profile. By mapping different datapoints into one customer profile, segmentation and insights become possible across the entire MarTech stack.

Updated:
April 25, 2025
Did this page help you?
Thank you! Your feedback has been received!
Oops! Something went wrong while submitting the form, for assistance please contact support@lexer.io
Welcome to Lexer!
Fundamentals
Getting started
Javascript Tag basics
Data Platform
Javascript Tag
Data in the CDXP
Fundamentals
Getting started
Our glossary
Fundamentals
Getting started
Integrations overview
Fundamentals
Integrations
Onboarding data with Lexer
Data Platform
Data Onboarding
Data onboarding process
Data Platform
Data Onboarding
Importing CSV data
Data Platform
Data Onboarding
Importing JSON data
Data Platform
Data Onboarding
Secure file uploads
Data Platform
Data Onboarding
SFTP uploads and exports
Data Platform
Data Onboarding
AWS S3 uploads and exports
Data Platform
Data Onboarding
Lexer's attributes
Data Platform
Data Types
Predictive attributes
Data Platform
Data Types
Lexer API overview
Data Platform
Developer APIs
Understanding APIs
Data Platform
Developer APIs
API authentication
Data Platform
Developer APIs
API rate limits
Data Platform
Developer APIs
Profile read API
Data Platform
Developer APIs
Activity overview
Insights
Activity
Team report
Insights
Activity
Cases report
Insights
Activity
NPS report
Insights
Activity
Listen overview
Insights
Listen
Searching in Listen
Insights
Listen
Tier filters
Insights
Listen
Saved dives
Insights
Listen
Boolean search
Insights
Listen
Listen CSV exports
Insights
Listen
Visualize overview
Insights
Visualize
Curate image feed
Insights
Visualize
Respond overview
Engagement
Respond
Identity Resolution
Fundamentals
Getting started
My account
Fundamentals
Setup
Manage team
Fundamentals
Setup
Group permissions
Fundamentals
Setup
Classifications
Fundamentals
Setup
Out of the box segments
Fundamentals
Setup
Lexi AI
Fundamentals
Getting started
Browser guide
Fundamentals
Security
Corporate networks
Fundamentals
Security
Multi-factor authentication
Fundamentals
Security
Single sign-on
Fundamentals
Security
Lexer's ultimate troubleshooting guide
Fundamentals
Troubleshooting
Troubleshooting tech issues
Fundamentals
Troubleshooting
Troubleshooting integrations
Fundamentals
Troubleshooting
Troubleshooting Activate
Fundamentals
Troubleshooting
Troubleshooting Respond
Fundamentals
Troubleshooting
Help! My data is missing from the Hub
Fundamentals
Troubleshooting
Lexer data specification
Data Platform
Data Specification
Customer data specification
Data Platform
Data Specification
Commerce data specification
Data Platform
Data Specification
Marketing data specification
Data Platform
Data Specification
Compliance data specification
Data Platform
Data Specification
Data formatting and validation
Data Platform
Data Specification
Product imagery
Data Platform
Data Specification
Currency conversion
Data Platform
Data Specification
Dataset management
Data Platform
Data Management
Getting started with Logs
Data Platform
Data Management
Respond chatbot API
Data Platform
Developer APIs
Activity API
Data Platform
Developer APIs
Lexer Forms overview
Data Platform
Forms
Form builder workflow
Data Platform
Forms
Form conditional logic
Data Platform
Forms
Form settings
Data Platform
Forms
Form segmentation
Data Platform
Forms
Form response analysis
Data Platform
Forms
Form hidden fields
Data Platform
Forms
Form attribute mapping
Data Platform
Forms
Javascript Tag technical guide
Data Platform
Javascript Tag
Javascript Tag use cases
Data Platform
Javascript Tag
Javascript Tag: Shopify Custom Pixel
Data Platform
Javascript Tag
CRM data
Data Platform
Data Types
Transaction data
Data Platform
Data Types
Email engagement data
Data Platform
Data Types
Experian data enrichment
Data Platform
Data Types
Customer Service data
Data Platform
Data Specification
GDPR and CCPA requests
Fundamentals
Compliance
File upload API
Data Platform
Developer APIs
Segment overview
Insights
Segment
Creating segments
Insights
Segment
Smart Search
Insights
Segment
Profile tab
Insights
Segment
Event Explorer
Insights
Segment
Attribute value types
Data Platform
Data Types
Compare segments
Insights
Compare
Compare attributes
Insights
Compare
Activate Overview
Engagement
Activate
Segment activations
Engagement
Activate
Event activations
Engagement
Activate
Activation field mapping
Engagement
Activate
Audience splits
Engagement
Activate
A/B splits
Engagement
Activate
Control group splits
Engagement
Activate
Inbox filtering
Engagement
Respond
Ignored Senders
Engagement
Respond
Forms in Respond
Engagement
Respond
Workflow states
Engagement
Respond
Bulk changes
Engagement
Respond
Scheduled replies
Engagement
Respond
Message templates
Engagement
Respond
Finding conversations
Engagement
Respond
Customer profiles
Engagement
Respond
Grouped messages
Engagement
Respond
Automation rules
Engagement
Respond
Redact messages
Engagement
Respond
Routing customer replies
Engagement
Respond
Interact with comments
Engagement
Respond
Respond workflow tips
Engagement
Respond
Contact Reporting
Engagement
Contact
Contact Queue Filters
Engagement
Contact
Contact WhatsApp Queues
Engagement
Contact
Schedule overview
Engagement
Schedule
Serve overview
Engagement
Serve
Installing Serve
Engagement
Serve
Contact in Serve
Engagement
Serve
Serve Messaging
Engagement
Serve
Serve user management
Engagement
Serve
Forms in Serve
Engagement
Serve
Configuring Serve
Engagement
Serve
Serve reports
Engagement
Serve
Serve Currency
Engagement
Serve
Serve POS QR Code
Engagement
Serve
Activate CSV export
Engagement
Activate
Track Overview
Insights
Track
Track Metric Tables
Insights
Track
Event Tables
Insights
Track
Lexer Product Recommender → Klaviyo Integration
Grow
Lexer Product Recommender → Klaviyo Integration
Where do your best customers live? Use geographic insights to maximize media spend and conversion
Grow
Where do your best customers live? Use geographic insights to maximize media spend and conversion
Suppression audiences: How to use them and maximize your media effectiveness
Enrich
Suppression audiences: How to use them and maximize your media effectiveness
Measure campaign effectiveness: Track your KPIs and report on campaign performance
Enrich
Measure campaign effectiveness: Track your KPIs and report on campaign performance
Converting prospects: Acquire customers from your current, engaged prospect base (and save your ad spend!)
Acquire
Converting prospects: Acquire customers from your current, engaged prospect base (and save your ad spend!)
Understanding customer intent: Effective message personalization for buyers who shop outside their gender
Grow
Understanding customer intent: Effective message personalization for buyers who shop outside their gender
Deepen customer understanding: Use third-party data to identify insights for personalized messaging and increased engagement
Grow
Deepen customer understanding: Use third-party data to identify insights for personalized messaging and increased engagement
Basket analysis: Increasing customer lifetime value through targeted product bundling
Grow
Basket analysis: Increasing customer lifetime value through targeted product bundling
Persona building: Personalize your messaging for maximum return on your campaign investments
Grow
Persona building: Personalize your messaging for maximum return on your campaign investments
Driving customer loyalty: Identify, keep, and grow your most loyal customers
Retain
Driving customer loyalty: Identify, keep, and grow your most loyal customers
Increasing customer lifetime value: Upselling strategies
Grow
Increasing customer lifetime value: Upselling strategies
Reactivating lapsed customers: Retention and growth
Retain
Reactivating lapsed customers: Retention and growth
Welcome offer strategies: Using the Hub for analysis
Acquire
Welcome offer strategies: Using the Hub for analysis
Creating customer forms: Best practices
Enrich
Creating customer forms: Best practices
Connecting your MarTech stack with Lexer!
Enrich
Connecting your MarTech stack with Lexer!
Identifying win-back customers using the Second Last Order: Date attribute
Retain
Identifying win-back customers using the Second Last Order: Date attribute
Understanding customers' purchasing habits: Order Sequence filter
Grow
Understanding customers' purchasing habits: Order Sequence filter
Maximizing customer communications in Respond
Retain
Maximizing customer communications in Respond
Using Product Recommendation in the Hub to encourage repeat purchases
Grow
Using Product Recommendation in the Hub to encourage repeat purchases
Encouraging customer loyalty using birthday campaigns
Retain
Encouraging customer loyalty using birthday campaigns
Increasing customer lifetime value: Converting your one-time buyers into two-time buyers
Grow
Increasing customer lifetime value: Converting your one-time buyers into two-time buyers
Collecting zero-party data using Lexer Forms
Enrich
Collecting zero-party data using Lexer Forms
Measuring your data over time with Track
Enrich
Measuring your data over time with Track
UTM Creation Guidelines
UTM Creation Guidelines
UTM Creation Guidelines
Brand Assets
Brand Assets
Brand Assets
GTM guide to creating marketing materials with Lexer
GTM guide to creating marketing materials with Lexer
GTM guide to creating marketing materials with Lexer
How to use the Lexer Form Builder
How to use the Lexer Form Builder
How to use the Lexer Form Builder
Explore our standard integrations
Explore our standard integrations
Explore our standard integrations
Operating a CDP Practice LP
Operating a CDP Practice LP
Operating a CDP Practice LP
LP Sales Enablement
LP Sales Enablement
LP Sales Enablement
Video Training Courses LP
Video Training Courses LP
Video Training Courses LP
Purpose and Mission
Purpose and Mission
Purpose and Mission
Brand & Marketing LP
Brand & Marketing LP
Brand & Marketing LP
Stage 3 - QBRs and Customer insights
Stage 3 - QBRs and Customer insights
Stage 3 - QBRs and Customer insights
Client Onboarding Journey
Client Onboarding Journey
Client Onboarding Journey
Start your CDP Practice
Start your CDP Practice
Start your CDP Practice
Lexer Messaging
Lexer Messaging
Lexer Messaging
Pain point conversations
Pain point conversations
Pain point conversations
Lexer Ideal Customer Profile & Positioning
Lexer Ideal Customer Profile & Positioning
Lexer Ideal Customer Profile & Positioning
Referral Partner Program Overview
Referral Partner Program Overview
Referral Partner Program Overview
Demo Hub Guide
Demo Hub Guide
Demo Hub Guide