Introduction: Do You Really Know Who Your Customer Is?
Imagine a customer named Sarah interacts with your business in several different ways.
She signs up for your email newsletter, browses products on your website, contacts customer service, and later makes a purchase. Each interaction generates valuable information, but that information may be stored in a different system.
Your marketing platform knows Sarah by her email address. Your CRM contains her customer record. Your website analytics platform tracks her browsing activity using a browser identifier. Your service team has a record of her recent support request.
Individually, each system holds a piece of the puzzle. Collectively, they could provide a much more complete understanding of Sarah and her relationship with your business.
The challenge? How do you determine which records belong to the same person?
This is where unified profiles and identity resolution in Salesforce Data 360 come into play.
In this article, we’ll explain what these concepts mean, how they work together, and why they matter for businesses looking to deliver more relevant customer experiences.
What Is a Unified Profile?
A unified profile is a consolidated view that links information about the same individual or account across multiple data sources.
Rather than treating every record as a separate customer, Salesforce Data 360 helps businesses connect records that represent the same person or organization.
Let’s return to Sarah and assume we have the following data sources and available information:
| Data source | Information available |
| CRM | Sarah’s name, account information, and contact details |
| Marketing Cloud | Email address, subscription status, and campaign engagement |
| Website | Browsing activity and product interests |
| Customer service | Support history and previous interactions |
| Transaction system | Purchase history and transaction details |
Without a unified profile, these records may remain disconnected, making it difficult for different teams to understand the full customer relationship.
With a unified profile, the business can link the relevant records to create a more complete view of Sarah.
Marketing may better understand her interests, customer service may gain additional context about her history, and other teams may be able to make more informed decisions.
The key takeaway: A unified profile helps a business understand the relationships between its customer records instead of viewing each record in isolation.
One important distinction: a unified profile does not necessarily combine every source record into one replacement record or establish one universally authoritative version of every field. Instead, it links related records and makes their information more accessible for different business needs.
What Is Identity Resolution?
If a unified profile is the result, identity resolution is the process that helps make it possible.
Identity resolution is the process of determining which records from different data sources belong to the same individual or account.
Salesforce Data 360 uses configurable matching rules to identify relationships between records and generate unified profiles.
For example, suppose three records contain the following information:
- Record A: Sarah Johnson, sarah.johnson@example.com
- Record B: Sarah Johnson, sarah.johnson@example.com, with a recent purchase
- Record C: S. Johnson, sarah.johnson@example.com, with website activity
A business may determine that these records belong to the same person because they share a matching email address and meet the configured matching criteria.
Identity resolution evaluates the records according to the rules the business establishes. When records meet those criteria, Data 360 can link them through a unified profile.
This is important because customer information rarely arrives in perfectly consistent formats. Names may be abbreviated, contact information may change, and different systems may use different identifiers for the same person.
Identity resolution helps address these differences, although its accuracy depends on the available data and the matching rules configured.
How Does Identity Resolution Work in Data 360?
Identity resolution is not simply a matter of connecting systems and automatically combining every record. There are several important steps involved.
Step 1: Bring Your Data Together
First, the business identifies the data sources that will contribute to its customer view.
These might include Salesforce CRM, Marketing Cloud Engagement, website activity, transaction systems, customer service platforms, or external databases.
The goal is to make relevant data available within Data 360.
However, bringing data into the platform does not automatically mean that all records have been connected to the correct customer. Additional preparation is needed.
Step 2: Map and Standardize Your Data
Before identity resolution can work effectively, the data must be mapped to the appropriate Data 360 data model objects.
In practical terms, this means making sure that information from different systems is represented consistently enough to be used together.
For example, one system might store an email address in a field called EmailAddress, while another calls it Email. Mapping connects those source fields to the appropriate standardized data model fields.
Data quality also matters. Inconsistent formatting, missing values, outdated contact details, and duplicate records can all affect the results.
The more reliable and consistently structured the source data is, the better the foundation for identity resolution.
Step 3: Define Matching Rules
Next, the business determines how Data 360 should decide whether records belong to the same person or account.
These decisions are configured through identity resolution rulesets.
Matching criteria might include email address, phone number, name, or other supported identifiers, depending on the data model and the business requirements.
Two common approaches are:
Exact matching: Records must match exactly on the selected criteria. For example, two records may match when their email addresses are identical.
Fuzzy matching: Records can match when values are sufficiently similar, depending on the supported matching method. This can help account for certain variations, such as minor spelling differences.
The choice between exact and fuzzy matching involves a trade-off. Strict rules can reduce the risk of incorrectly linking different people, while more flexible rules can help identify legitimate matches when data is inconsistent.
The right approach depends on the quality of the data, the identifiers available, and the business’s tolerance for incorrect matches.
Step 4: Apply Reconciliation Rules
Matching rules determine which records should be linked. Reconciliation rules address a different question: when multiple linked records contain different values for a field, which value should appear in the unified view?
For example, Sarah’s CRM record might contain an older phone number, while a more recently updated source contains her current number.
Depending on the configured reconciliation rules and available data, the business can determine which value should be selected for the relevant unified field.
This distinction is important: matching and reconciliation solve different problems.
- Matching: Which records belong together?
- Reconciliation: Which value should be presented when linked records contain conflicting values?
Reconciliation does not automatically update the original source systems or make the unified profile a master record that overrides them.
Step 5: Generate and Validate Unified Profiles
Once the data is prepared and the rules are configured, Data 360 processes the identity resolution ruleset and produces unified profile outputs.
The business can then review those results to understand how records were linked and whether the outcome aligns with expectations.
For example, are records that belong to Sarah being connected correctly? Have records belonging to different customers been linked accidentally? Are important records remaining separate because the matching criteria are too restrictive?
Reviewing the results is essential. Identity resolution should not be treated as a one-time configuration exercise that never needs to be revisited.
As source data changes and new systems are introduced, the matching rules and resulting profiles may need to be reviewed and refined.
What Is the Difference Between a Unified Profile and a Golden Record?
This is an important distinction when planning a Data 360 implementation.
A golden record generally refers to a trusted master record that consolidates data and establishes authoritative values for an entity.
A unified profile in Data 360 serves a different purpose. It links records that represent the same individual or account, helping the business access the information associated with those records.
Think of it this way:
- A golden record is often intended to establish an authoritative version of an entity’s data.
- A unified profile connects related records to provide a more comprehensive view of that entity.
This means a unified profile does not automatically resolve every data quality issue, correct the original records, or establish a single source of truth for every attribute.
If your organization needs to govern authoritative customer values across source systems, you may need additional data management processes alongside Data 360.
Understanding this difference early can help set realistic expectations for the implementation.
Why Do Unified Profiles Matter to the Business?
Unified profiles are valuable because they can make customer information more useful across marketing, sales, and service. The benefits depend on the data available and how the organization uses it.
1. More Relevant Marketing
When a marketing team can connect customer information across systems, it can build audiences using a broader range of relevant attributes and interactions.
For example, a business may be able to distinguish between a customer who has already purchased a product and someone who has only expressed interest in it.
That information can support more appropriate messaging, audience exclusions, and customer journeys.
2. Better Customer Service
Service representatives often need information from multiple systems to understand a customer’s situation.
A more complete view can help them see relevant interactions and customer history, reducing the need to piece together information manually.
3. More Informed Business Decisions
Connected data can help organizations identify patterns that are difficult to see when information is fragmented.
For example, a business might analyze how marketing engagement relates to purchases, service interactions, or customer retention, provided the necessary data is available and appropriately modeled.
4. Improved Customer Experience
Customers generally expect a consistent experience across channels.
If marketing, sales, and service operate with disconnected information, communications may become repetitive, irrelevant, or poorly timed.
Unified profiles can provide a stronger foundation for coordinating those interactions.
5. A Foundation for Personalization and AI
Unified profiles can support segmentation, activation, and other downstream use cases that depend on understanding the relationships between customer records.
They can also help provide relevant context to personalization and AI-powered experiences when the appropriate data is available and accessible.
However, unified profiles alone do not guarantee personalization or better outcomes. The business still needs appropriate use cases, sound data governance, effective activation, and meaningful performance measures.
Common Identity Resolution Challenges to Watch For
Even a well-designed implementation can encounter challenges. Some of the most important considerations include:
Poor source data quality. Missing, outdated, or inconsistent identifiers can prevent legitimate matches or contribute to incorrect ones.
Overly restrictive matching rules. If the criteria are too strict, records belonging to the same person may remain disconnected.
Overly permissive matching rules. If the criteria are too broad, records belonging to different people may be incorrectly linked.
Unclear business requirements. Teams may disagree about which identifiers should determine a match or which source should supply a particular field value.
Unrealistic expectations. Some stakeholders may assume that a unified profile automatically cleans data, replaces source records, or resolves every customer identity.
Insufficient validation. If teams do not examine the resulting profiles and investigate unexpected matches, configuration issues can persist.
The best way to address these challenges is to define the business requirements before configuring identity resolution, assess the available data, and validate the results against realistic examples.
Questions to Ask Before Implementing Identity Resolution
Before configuring identity resolution in Salesforce Data 360, business and technical stakeholders should align on several key questions:
- What is the business objective? Are unified profiles intended to improve segmentation, personalization, service visibility, reporting, or another outcome?
- Which data sources are in scope? Identify the systems that contain relevant customer or account information.
- Which identifiers are available? Determine whether email addresses, phone numbers, customer IDs, or other supported identifiers are sufficiently complete and reliable.
- What defines a match? Establish the criteria that indicate two records belong to the same person or account.
- How should conflicting values be handled? Define how the unified view should select values when records disagree.
- How will accuracy be measured? Determine how the team will validate matches, identify false positives and missed matches, and monitor results.
- Who owns the data and business rules? Establish responsibility for data quality, identity resolution decisions, and ongoing maintenance.
- How will the unified data be used? Identify the downstream systems, segments, activations, and business processes that depend on the results.
Answering these questions helps ensure that identity resolution supports a clear business need rather than becoming a technical exercise without a defined outcome.
Bringing It All Together
Unified profiles and identity resolution are foundational concepts in Salesforce Data 360, but they serve distinct purposes.
Identity resolution determines which records should be linked based on configured matching rules. Unified profiles provide a consolidated way to access information associated with those linked records.
Together, they help organizations move beyond disconnected customer records toward a more comprehensive understanding of their customers.
The most important takeaway is that successful identity resolution starts with business requirements and reliable data, not simply with configuring matching rules.
When organizations understand what they want to accomplish, prepare their data carefully, define appropriate matching and reconciliation criteria, and validate the results, unified profiles can become a valuable foundation for better segmentation, more relevant customer experiences, and more informed business decisions.
Leave a Reply