Customer 360
Customer 360 is Salesforce product-portfolio and integration vision: a unified customer profile spanning every Salesforce cloud (Sales, Service, Marketing, Commerce, Data Cloud, Agentforce) so every department in the business sees the same data about each customer.
Definition
Customer 360 is Salesforce product-portfolio and integration vision: a unified customer profile spanning every Salesforce cloud (Sales, Service, Marketing, Commerce, Data Cloud, Agentforce) so every department in the business sees the same data about each customer. The concept is delivered through shared data models (the Customer 360 Data Model), identity resolution in Data Cloud, and cross-cloud integration via Marketing Cloud Connect, Salesforce Connect, and the Einstein 1 Platform.
Customer 360 is both the marketing term Salesforce uses to describe its suite and the technical capability that unifies customer data across the products. Salesforce introduced the phrase in 2018 to anchor a multi-year platform-consolidation initiative and continues to use it as the framing for new product launches. The phrase appears in keynotes, press releases, partner solution naming, and product documentation, even when individual products underneath have evolved or rebranded.
What Customer 360 means in practice
The Customer 360 Data Model
The Customer 360 Data Model is the schema that unifies customer data across Salesforce clouds: the same Account, Contact, Lead, Opportunity, Case, and product objects defined consistently in Sales Cloud, Service Cloud, and Marketing Cloud. Data Cloud sits in the middle, normalizing data from each cloud and from external systems into one canonical model.
Data Cloud and identity resolution
Data Cloud is the technical heart of Customer 360. It ingests data from every Salesforce cloud and external sources, applies identity resolution (matching that joe@example.com is the same person as Joseph A on a recent Case), and produces a unified profile. The profile becomes the source of truth that downstream tools read from for personalization and analytics.
Cross-cloud integration patterns
Multiple integration paths connect the clouds: Marketing Cloud Connect for Sales and Service to MCE, Salesforce Connect for surfacing one cloud data in another as virtual objects, the Einstein 1 Platform for shared AI services, MuleSoft for higher-volume custom integrations, and the Data Cloud zero-copy architecture for sharing live data without duplication.
Customer 360 and Agentforce
Agentforce, Salesforce AI agent platform, leans heavily on Customer 360. Every agent action reads from the unified profile and writes back to the same data store. The agent knows about the customer open Cases (from Service Cloud), recent purchases (from Commerce), marketing engagement (from MCE), and pipeline (from Sales) without separate queries. The Customer 360 framework is what makes the agent feel coherent.
The marketing-versus-technical sense of the term
Customer 360 is used two ways. In marketing material and sales conversations, it describes the Salesforce vision: one customer, every Salesforce product, everything connected. In technical documentation, it describes specific products and configurations (Data Cloud, the Customer 360 Data Model, Marketing Cloud Connect). Both senses are used in the same Salesforce documentation, sometimes in the same paragraph.
Customer 360 vs CDP
Customer 360 is broader than Customer Data Platform (CDP). A CDP is one piece of the Customer 360 picture: identity resolution, segmentation, activation across marketing channels. Customer 360 includes the CDP capability (Data Cloud serves as the CDP) plus the Salesforce CRM data, the service interactions, the commerce transactions, and the AI services on top.
Common misconceptions
The biggest one: Customer 360 is not a single product you buy. It is the framework Salesforce uses to position multiple products as one connected system. You buy Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud separately; Customer 360 is the integration story that makes them work together. The second misconception: Customer 360 is not automatic. The integration requires configuration, data hygiene, and (often) MuleSoft or custom Apex to fully realize.
How to plan a Customer 360 implementation
Implementing Customer 360 is a multi-product, multi-quarter program. The framing is simple; the work of unifying data and processes across clouds takes years for large enterprises.
- Define the customer record schema
Agree across Sales, Service, Marketing, and Commerce on what defines a customer (Account vs Person Account, what makes two records the same customer, what fields constitute the unified profile). Documentation precedes configuration.
- Stand up Data Cloud
Provision Data Cloud, configure connectors to each Salesforce cloud and external data source, build the unified profile, and validate identity resolution. This is the heart of the implementation.
- Configure cross-cloud integration
Set up Marketing Cloud Connect, Salesforce Connect external data sources, or MuleSoft flows for the specific cross-cloud data needs. Start with the highest-business-value flows (lead-to-pipeline, service-to-marketing).
- Implement the unified UI
Surface Customer 360 data in each cloud user interface. Salesforce ships Lightning components and templates for many patterns; custom builds extend them for industry-specific needs.
- Build the analytics and AI layer
Connect Tableau, Einstein analytics, or Tableau Pulse to the Data Cloud unified profile. Roll out Agentforce or other AI agents that read from and write to the unified data.
- Govern and iterate
Customer 360 is not done once configured. Data hygiene, identity resolution accuracy, and process alignment require ongoing governance. Build a Customer 360 council with cross-cloud representation.
- Customer 360 cannot be deployed by a single team. Sales, Service, Marketing, and IT must each contribute; without joint sponsorship, the project stalls.
- Identity resolution failures are the most common Customer 360 issue. Different teams maintain Lead and Contact and Account records independently; mismatches propagate everywhere.
- Cloud-to-cloud data sync introduces latency. Real-time UX expectations need to be tempered by the sync timing of the underlying integrations.
- Salesforce rebrands Customer 360 components occasionally. Customer 360 Truth, Customer 360 Data Manager, and Customer 360 Audiences have all been positions for different products at different times; check current Salesforce documentation.
- Customer 360 budgets often underestimate the data engineering cost. Data Cloud itself is expensive, and the human cost of data cleanup before identity resolution can be sizeable.
Trust & references
Straight from the source - Salesforce's reference material on Customer 360.
- Agentforce OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Customer 360?
Q2. Which Salesforce product often serves as the identity resolution layer in Customer 360?
Q3. What's required to deliver on the Customer 360 promise?
Discussion
Loading discussion…