Salesforce Data 360 Customer 360: Unified Profiles, Identity Resolution, Architecture & Use Cases

What Is Salesforce Data 360 Customer 360?

Salesforce Data 360 Customer 360 is an approach to bringing customer information from multiple systems together so organizations can understand customers across sales, service, marketing, commerce and other interactions.

The challenge is straightforward.

Enterprise customer data rarely exists in one place.

A single customer may appear as:

• A Salesforce contact
• An ERP customer
• A marketing subscriber
• An e-commerce account
• A website visitor
• A support customer
• A mobile application user
• A loyalty member

Each system may use a different identifier.

Data 360 provides the architecture for connecting these records, mapping them into a common data model, resolving identities and creating unified profiles that can be used across Salesforce applications and business processes. Salesforce describes Data 360 as a cloud-native data platform designed to unify siloed enterprise data and make it available for analytics, AI and agentic applications.

The important distinction is that a unified profile is not simply a copied master customer record.

Salesforce explicitly states that Data 360 identity resolution does not create a golden record and is not an MDM system. Instead, unified profiles link matching records so organizations can use the appropriate source data for a specific business use case.

Salesforce Data 360 Customer 360 at a Glance

Why Do Enterprises Need Customer 360?

Most enterprises have a data fragmentation problem.

Imagine a customer who:

• Purchased products three times
• Opened two support cases
• Visited the website five times this week
• Clicked three marketing emails
• Has an active sales opportunity
• Has an outstanding invoice

That information might exist in five or six different systems.

A sales representative may see only the opportunity.

A service agent may see only the support cases.

Marketing may see only campaign engagement.

Finance may see only invoices.

The customer, however, experiences all of these interactions as one relationship with the company.

Customer 360 attempts to close that gap.

Salesforce Data 360 Customer 360 Architecture

A simplified architecture looks like:

Salesforce CRM → ERP → Marketing → Commerce → Service → Website & Mobile → Data Warehouse → Data 360 → Data Preparation → Customer 360 Data Model → Identity Resolution → Unified Customer Profile → Insights & Segments → Activation → Sales | Service | Marketing | Commerce | Analytics | Agentforce

Salesforce's current Data 360 architecture combines ingestion, modeling, identity resolution, unified profiles, real-time processing and activation.

What Is a Salesforce Unified Customer Profile?

A unified customer profile is a connected view of records that Data 360 determines belong to the same customer or account.

For example:

Salesforce

Contact ID: 003123

E-commerce

Customer ID: CUST-8921

Marketing

Subscriber ID: SUB-4421

Website

User ID: USER-99281

Data 360 can use identity resolution rules to determine whether these identifiers represent the same individual.

The resulting unified profile connects the source records.

It does not necessarily replace them.

Salesforce describes unified profiles as a way of linking customer IDs across Salesforce and external systems into a comprehensive view.

Unified Profile vs Golden Record

This distinction is important for enterprise architecture.

A traditional MDM approach may attempt to establish:

"This is the single authoritative version of the customer."

Data 360 takes a different approach.

The unified profile answers:

"Which records belong to this customer?"

That distinction matters because different business processes may need different source-system values.

For example:

Finance

May trust ERP billing information.

Sales

May trust CRM account ownership.

Marketing

May use consent and engagement information.

Service

May need current case and entitlement information.

Data 360 can connect these records without forcing every application to abandon its source of truth.

Salesforce explicitly states that identity resolution does not select winning values or overwrite existing source data.

Salesforce Identity Resolution

Identity resolution is one of the most important capabilities in a Customer 360 implementation.

Its purpose is to determine which records represent the same person, household or account.

For example:

John Smith

[email protected]

and

J. Smith

[email protected]

may be the same person.

But:

John Smith

[email protected]

and

John Smith

[email protected]

could represent different individuals.

The matching logic needs to account for such situations.

How Salesforce Data 360 Identity Resolution Works

Identity resolution uses match rules and reconciliation rules.

Salesforce describes match rules as criteria that determine which profiles should be unified. Multiple match rules can be created, and a unified profile is created when a configured match rule is activated.

Common matching attributes include:

• Email
• Phone
• Address
• Name
• Party identification
• Application identifiers
• Social identifiers
• Other supported contact-point data

The appropriate rules depend on:

• Business model
• Data quality
• Customer type
• Geography
• Regulatory requirements
• Risk tolerance

Identity Resolution Example

Suppose an enterprise has these records.

CRM

Name: Rahul Sharma
Email: [email protected]
Phone: +91 XXXXXXX

E-commerce

Name: Rahul S.
Email: [email protected]

Marketing

Name: Rahul Sharma
Email: [email protected]
Subscriber ID: 8912

Mobile App

User ID: APP-4421
Email: [email protected]

Data 360 can identify the common relationship between these records.

The resulting unified profile provides the organization with a connected customer context.

Match Rules vs Reconciliation Rules

These two concepts solve different problems.

Match Rules

Answer:

"Are these records the same entity?"

For example:

• Same email
• Same phone
• Same email + name
• Same address + name

Reconciliation Rules

Answer:

"Which source information should be used for a particular view or business requirement?"

This is important because multiple source systems may contain different values.

For example:

Identity resolution determines the relationship.

Reconciliation helps determine how the information should be represented for the relevant use case.

Salesforce Customer 360 Data Model

A common data model is essential when information comes from different systems.

Salesforce's Customer 360 Data Model provides standardized data guidelines and organizes data into subject areas made up of Data Model Objects, or DMOs.

Examples of subject areas include:

• Customer
• Product
• Engagement
• Sales
• Service
• Commerce

This helps different systems communicate using common concepts.

Why the Data Model Matters

Consider three systems.

CRM

Account_ID

ERP

Customer_Number

Commerce

Buyer_ID

They may all refer to the same business entity.

The data model provides a common structure for representing that entity.

The architecture becomes:

Source Fields → Data Lake Objects → Data Model Objects → Unified Customer Profile

Salesforce describes DLOs as the source-oriented layer and DMOs as the harmonized layer aligned with the Customer 360 Data Model.

DLO vs DMO in Customer 360

Data Lake Object

DLOs represent data brought from source systems.

They retain source-oriented information.

Think:

"What did the source system send us?"

Data Model Object

DMOs provide the harmonized structure.

Think:

"How should this information be represented consistently across the enterprise?"

This distinction becomes particularly important when integrating multiple systems.

Customer 360 Data Flow

A practical data flow looks like:

Step 1: Source Systems

CRM, ERP, marketing, website and other systems generate data.

Step 2: Ingestion

Data enters Data 360 through supported connectors, APIs or other integration mechanisms.

Step 3: Preparation

Data is cleaned and transformed.

Step 4: Mapping

Source information is mapped to the Customer 360 Data Model.

Step 5: Identity Resolution

Matching rules connect records belonging to the same entity.

Step 6: Unified Profile

Data 360 creates the connected profile.

Step 7: Insights

Calculated metrics and business signals can be created.

Step 8: Segmentation

Customers can be grouped based on relevant attributes and behavior.

Step 9: Activation

Information can be used by sales, service, marketing, commerce, analytics and AI applications.

Salesforce's architecture documentation describes this broader lifecycle as ingesting, processing, modeling, unifying and activating data.

Customer 360 Use Case: Sales

Sales teams often need more than CRM opportunity information.

A unified profile can potentially combine:

• Account information
• Contact information
• Opportunity history
• Purchase history
• Marketing engagement
• Service history
• Product usage
• Customer value

This can help sales teams understand account context before engaging with a customer.

Example

A sales representative opens an account.

Instead of seeing only:

Open Opportunity: $250,000

the broader context might include:

• Existing customer
• $1.2M lifetime revenue
• Two unresolved service issues
• High website engagement
• Recently downloaded product documentation
• Renewal approaching

That changes the conversation.

Customer 360 Use Case: Customer Service

Customer service is one of the strongest use cases for unified customer data.

A service agent may need:

• Customer identity
• Products owned
• Orders
• Previous cases
• Contract
• Entitlements
• Payments
• Recent interactions

Without integration, the agent may need to switch between several applications.

With a connected customer context, the service workflow can become much more efficient.

Customer 360 Use Case: Marketing

Marketing can use Customer 360 to create more relevant audiences.

For example:

Customers → High lifetime value → Purchased Product A → No purchase in 90 days → High website engagement → Retention Segment → Marketing Journey

Instead of building the audience from one system, the organization can use information from multiple sources.

Customer 360 Use Case: Personalization

Personalization becomes more useful when the platform understands customer context.

Consider an online store.

The customer:

• Previously purchased a laptop
• Viewed accessories
• Opened a promotional email
• Has a premium membership
• Recently contacted support

A personalization engine can use this broader context to determine what experience should be presented.

Data 360 can provide the underlying customer data foundation for such experiences.

Customer 360 Use Case: Commerce

Commerce organizations can combine:

• Customer profile
• Purchase history
• Browsing behavior
• Product preferences
• Loyalty
• Marketing engagement
• Service history

This can support:

• Product recommendations
• Personalized promotions
• Loyalty experiences
• Cross-sell
• Upsell
• Cart recovery

Customer 360 Use Case: Customer Retention

Retention programs can use multiple signals.

For example:

Customer has

• Declining product usage
• Lower engagement
• Recent support issue
• Renewal approaching

Customer Health Score → Retention Segment → Sales / Service Action → Personalized Offer

The key advantage is combining signals rather than relying on one system.

Customer 360 and Real-Time Data

Customer 360 becomes significantly more powerful when customer information is available with low latency.

Salesforce's current Data 360 strategy documentation describes real-time capabilities supporting synchronized customer data and sub-second processing across supported customer interactions.

For example:

Customer purchases product → Event received → Customer profile updated → Lifetime value recalculated → Segment changes → Personalized experience

The entire process can happen rapidly enough to influence the current interaction.

Customer 360 and Zero Copy

Not every dataset needs to be copied into Data 360.

Salesforce's architecture supports zero-copy federation with external data platforms such as:

• Snowflake
• Databricks
• BigQuery
• Redshift

This allows organizations to access supported external data without necessarily duplicating it.

This can be important for enterprises that already have significant investments in cloud data platforms.

Customer 360 and Data Warehouses

A common enterprise architecture is:

Enterprise Data Warehouse → Customer and behavioral data

↕

Data 360 → Salesforce applications

The goal is not necessarily to replace the existing warehouse.

Instead, Data 360 can provide an operational layer that makes relevant data actionable within customer-facing processes.

This distinction matters.

A data warehouse primarily answers:

"What happened?"

Customer 360 also needs to answer:

"What should we do next?"

Customer 360 and Agentforce

AI agents need context.

An agent that knows only the current support case has limited context.

An agent that can access:

• Customer profile
• Orders
• Product usage
• Service history
• Account value
• Customer preferences
• Relevant policies

can make much more informed decisions.

Salesforce's current architecture positions Data 360 as a data foundation for AI and agentic applications, including Agentforce.

A simplified architecture is:

Enterprise Data → Data 360 → Unified Customer Context → Agentforce → Reasoning → Action

Customer 360 and Agent Memory

AI agents increasingly need both current context and historical context.

For example:

A customer says:

"I'm having the same issue again."

The agent needs to understand:

• What issue?
• When did it happen?
• What solution was attempted?
• Was the customer satisfied?
• What product is involved?

Data 360's current architecture includes real-time data, unstructured data processing and profile/context services designed to support AI and agentic applications.

This makes Customer 360 increasingly relevant to AI architecture rather than only CRM reporting.

Customer 360 for B2B Organizations

B2B Customer 360 is more complex than individual consumer profiles.

Organizations may need to understand:

• Account
• Parent company
• Subsidiaries
• Contacts
• Buying committees
• Opportunities
• Contracts
• Products
• Orders
• Support relationships

The data model therefore needs to support relationships between entities.

For example:

Global Parent → Regional Account → Business Unit → Contacts → Opportunities → Products

This is especially important for enterprise account management.

Customer 360 for B2C Organizations

B2C environments can involve millions of individual profiles.

Common data sources include:

• E-commerce
• Mobile applications
• Websites
• Loyalty
• Marketing
• Customer service
• Payments

Identity resolution becomes particularly important because the same individual may interact through multiple devices and channels.

Customer 360 for Financial Services

Financial services organizations can combine:

• Customer profile
• Accounts
• Transactions
• Products
• Service interactions
• Digital engagement
• Relationship manager activity

This can support:

• Next-best action
• Customer segmentation
• Relationship intelligence
• Personalization
• Service
• AI-assisted interactions

Data governance and privacy requirements are particularly important in this environment.

Customer 360 for Healthcare

Healthcare organizations may need to connect information across:

• Patient
• Provider
• Appointment
• Service
• Engagement
• Communication

The architecture must be designed around applicable privacy, security and regulatory requirements.

The value of Customer 360 is not simply collecting more information.

It is making the right information available to the right process under the right controls.

Customer 360 for Retail

Retail organizations can combine:

• Store purchases
• E-commerce
• Loyalty
• Website behavior
• Mobile engagement
• Customer service

This supports:

• Personalized offers
• Product recommendations
• Customer segmentation
• Loyalty
• Retention
• Cross-sell

Customer 360 for Manufacturing

Manufacturing organizations may need a broader account view involving:

• Customers
• Distributors
• Products
• Orders
• Service
• Assets
• Contracts
• Demand

A unified account context can help sales, service and account management teams work from a shared understanding of the customer relationship.

Customer 360 for Education

Education organizations may need to connect:

• Student
• Applicant
• Parent
• Program
• Enrollment
• Engagement
• Service interactions

Customer 360 concepts can therefore extend beyond traditional commercial customer relationships.

Customer 360 Data Quality

A unified profile is only as useful as the data behind it.

Common data-quality problems include:

• Duplicate records
• Invalid email addresses
• Missing phone numbers
• Inconsistent names
• Different country formats
• Inconsistent account IDs
• Missing transaction identifiers

Before implementing identity resolution, organizations should understand the quality of source data.

Data Quality Framework

Evaluate each source across:

Completeness

Are required fields populated?

Accuracy

Is the information correct?

Consistency

Do systems use compatible formats?

Timeliness

How current is the information?

Uniqueness

Are duplicates present?

Validity

Does the data conform to expected formats?

Customer 360 Governance

Customer 360 requires more than technology.

Organizations need governance around:

• Data ownership
• Data classification
• Access
• Consent
• Privacy
• Retention
• Residency
• Data quality
• Identity rules
• Source-system authority

Salesforce's current Data 360 architecture includes governance and security capabilities across the platform, including lineage, data masking, residency and zero-trust security considerations.

Customer 360 Security Model

A mature implementation should define:

Who Can Access Data?

Users and applications should have appropriate permissions.

What Data Can They Access?

Sensitive data may require additional controls.

Where Is Data Stored?

Data residency can influence architecture.

How Is Data Shared?

External integrations should follow security requirements.

How Is Data Used?

Organizations should define acceptable business purposes.

Customer 360 Implementation Roadmap

A practical implementation can follow these stages.

Phase 1: Business Strategy

Define:

• Business goals
• Priority use cases
• KPIs
• Stakeholders

Phase 2: Data Discovery

Inventory:

• Systems
• Sources
• Data entities
• Identifiers
• Data owners

Phase 3: Architecture

Define:

• Data 360 org strategy
• Integration patterns
• Data model
• Security
• Governance

Salesforce recommends planning organizational architecture, data strategy and data model concepts before implementation.

Phase 4: Data Integration

Connect priority systems.

Start with high-value sources rather than attempting to connect everything simultaneously.

Phase 5: Data Modeling

Map source data to the Customer 360 Data Model.

Phase 6: Identity Resolution

Configure:

• Match rules
• Reconciliation
• Identity keys

Phase 7: Unified Profiles

Validate whether records are being linked correctly.

Phase 8: Insights

Create:

• Calculated insights
• Customer scores
• Behavioral signals
• Business metrics

Phase 9: Activation

Connect customer context to:

• Marketing
• Sales
• Service
• Commerce
• AI

Phase 10: Optimization

Continuously monitor:

• Data quality
• Identity accuracy
• Usage
• Business outcomes
• Integration health

Salesforce Data 360 Customer 360 KPIs

Data KPIs

• Profile completeness
• Data freshness
• Duplicate rate
• Match rate
• Unmatched record rate

Customer KPIs

• Customer engagement
• Retention
• Lifetime value
• Conversion
• Cross-sell
• Upsell

Sales KPIs

• Pipeline conversion
• Sales cycle
• Account engagement
• Revenue per account

Service KPIs

• First-contact resolution
• Average handling time
• Customer satisfaction
• Case escalation

Marketing KPIs

• Campaign conversion
• Segment engagement
• Journey conversion
• Customer retention

AI KPIs

• Agent resolution rate
• AI-assisted productivity
• Escalation rate
• Response accuracy
• Customer satisfaction

Common Salesforce Customer 360 Challenges

1. Treating Data 360 as a Data Dump

Connecting every system without a strategy creates complexity.

Better approach: start with business use cases.

2. Poor Identity Rules

Overly broad matching can merge different customers.

Overly strict matching can leave duplicates.

Better approach: test match rules against real data.

3. Confusing Identity Resolution With MDM

Data 360 unified profiles are not automatically golden records.

Better approach: clearly define source-system ownership and reconciliation requirements.

4. Ignoring Data Quality

Identity resolution cannot compensate for fundamentally poor source data.

Better approach: improve data quality upstream and during transformation.

5. Building Everything in Real Time

Not every customer attribute requires immediate processing.

Better approach: classify workloads as batch, streaming, near-real-time or real-time.

6. Ignoring Existing Data Platforms

Enterprises may already have significant investments in Snowflake, Databricks or other platforms.

Better approach: evaluate zero-copy and interoperability before duplicating data.

7. No Activation Strategy

A unified profile has limited business value if nobody uses it.

Better approach: define activation use cases before implementation.

Salesforce Customer 360 Best Practices

1. Start With Business Outcomes

Do not begin with technology.

Begin with:

What customer problem are we solving?

2. Prioritize Data Sources

Start with the systems required for the first business use case.

3. Design Identity Resolution Carefully

Test rules against real-world edge cases.

4. Establish Source Ownership

Know which system owns which attribute.

5. Use the Standard Data Model Where Possible

Avoid unnecessary custom structures.

6. Separate Data Unification From Data Activation

First determine what the customer relationship looks like.

Then determine where that information needs to go.

7. Consider Zero Copy

Do not automatically duplicate large external datasets.

8. Design for AI Early

If Agentforce is part of the roadmap, design the data foundation accordingly.

9. Monitor Profile Quality

A high profile count does not necessarily mean a high-quality Customer 360.

10. Measure Business Outcomes

Customer 360 should ultimately improve a measurable business process.

Salesforce Customer 360 vs Traditional CRM

The key difference is that Data 360 expands the customer view beyond the CRM itself.

Salesforce Customer 360 vs CDP

The terms CDP and Customer 360 are often used interchangeably, but they are not exactly the same.

A traditional Customer Data Platform generally focuses on:

• Customer data
• Identity resolution
• Profiles
• Segmentation
• Activation

Salesforce Data 360 extends this concept into a broader enterprise data and AI architecture.

It can work with:

• CRM
• ERP
• Data warehouses
• Data lakes
• Unstructured data
• Real-time events
• AI applications
• Salesforce applications

Salesforce's current architecture positions Data 360 as a broader data platform rather than simply a marketing-focused customer database.

Customer 360 and Salesforce Data Cloud: Are They the Same?

Salesforce Data Cloud was rebranded as Data 360 on October 14, 2025.

Salesforce states that the functionality and content remained unchanged as part of the name transition.

Therefore, older resources may still refer to:

Salesforce Data Cloud

while current Salesforce documentation uses:

Salesforce Data 360

This is important when researching implementation guidance because both terms may appear in search results.

MoreYeahs for Salesforce Customer 360

MoreYeahs' Salesforce practice focuses on implementation, integration, data migration, automation and ongoing Salesforce optimization.

Its current Salesforce services page highlights:

• Salesforce implementation
• Data migration and validation
• Custom object and workflow design
• Salesforce integrations
• Managed services
• Org health monitoring
• User support
• Release management

The company also states that it has built integrations with SAP, NetSuite, Dynamics 365 and custom systems using real-time API, near-real-time middleware and batch patterns.

These capabilities are relevant to Customer 360 because a unified customer view depends on the quality of the surrounding enterprise integrations.

MoreYeahs' stated five-stage Salesforce delivery process is:

Discovery → Configuration → Integration → Training → Optimisation

This can provide a practical framework for Customer 360 programs:

Discovery

Identify customer journeys, data sources and business outcomes.

Configuration

Set up the required Salesforce and Data 360 structures.

Integration

Connect CRM, ERP, marketing, commerce and other systems.

Training

Help teams understand how to use unified customer context.

Optimisation

Improve data quality, identity resolution, activation and business outcomes.

MoreYeahs currently reports 200+ projects and 94% client satisfaction on its Salesforce services page. These are company-reported figures and should not be treated as guaranteed project outcomes.

Salesforce Customer 360 Implementation Checklist

Strategy

• Define Customer 360 objectives
• Identify priority customer journeys
• Define KPIs
• Identify stakeholders

Data

• Inventory data sources
• Identify customer identifiers
• Assess data quality
• Define data ownership
• Identify sensitive data

Architecture

• Define Data 360 org strategy
• Define Customer 360 Data Model
• Define integration patterns
• Evaluate zero copy
• Define security architecture

Identity

• Define match rules
• Define reconciliation rules
• Test duplicate scenarios
• Test false-match scenarios
• Validate unified profiles

Activation

• Define sales use cases
• Define service use cases
• Define marketing use cases
• Define commerce use cases
• Define AI use cases

Governance

• Define data access
• Define privacy controls
• Define retention
• Define residency requirements
• Define monitoring

Optimization

• Monitor data quality
• Monitor profile quality
• Monitor integration health
• Monitor activation
• Measure business outcomes

Final Takeaway

Salesforce Data 360 Customer 360 is not simply about putting customer records into one database.

It is about creating connected, trusted and actionable customer context across the enterprise.

A strong architecture combines:

Enterprise Data → Integration → Data Modeling → Identity Resolution → Unified Profiles → Insights → Segmentation → Activation → Customer Experience

And increasingly: → AI and Agentforce

The most important architectural distinction is that a unified profile is not automatically a golden record. Data 360 identity resolution connects source records so organizations can understand which data belongs to the same customer while retaining the underlying source-system information.

For enterprises, the real value of Customer 360 comes when that unified context changes what the business does.

A sales representative sees the right account context.

A service agent understands the customer's history.

Marketing creates more relevant audiences.

Commerce personalizes experiences.

AI agents receive the context they need to act.

That is the difference between having customer data and operationalizing customer intelligence.