Salesforce Customer 360 is Salesforce's name for its full suite of connected apps, for sales, service, marketing, commerce, IT and industries, which run on one platform and share one view of each customer. It is not a single product or licence: you buy the individual clouds, and together they form Customer 360. Data 360, formerly Data Cloud, is the part that unifies customer data from every source.
This guide was first published in 2020 as "Salesforce customer 360: Overview and Features". It has been rewritten for 2026, when Customer 360 sits alongside Agentforce and Data 360.
What is Salesforce Customer 360?
Salesforce's Customer 360 page defines it as "a suite of deeply unified products that provides a complete view of customers across all touchpoints and interactions". It says the suite brings together Salesforce's apps for sales, service, marketing, commerce, IT, operations, industries and partners, on the same platform, so data does not have to be stitched together between separate tools. The same page calls Customer 360 the application layer of Salesforce's agentic enterprise architecture, says Agentforce now powers every Customer 360 app, and counts Slack as part of it.
The name is used in two ways, which is why people find it confusing:
- The portfolio: every Salesforce app working together.
- The outcome: a "360-degree view" of a customer, meaning everything your company knows about them in one place.
Is Customer 360 a product you can buy?
No, not as one licence. You buy the parts: Sales Cloud, Service Cloud, Marketing Cloud, Data 360 and so on, or a bundled suite such as Starter or Pro for smaller companies; existing customers can also start with Salesforce Foundations, which the Customer 360 page offers as "Activate Foundations". Each one you add becomes part of your Customer 360. So when a salesperson says "Customer 360", ask which specific products and editions they mean, and compare them using our editions guide.
Where Customer 360 came from
Customer 360 began in 2018 as a way to connect Salesforce apps around one customer ID and has grown into the name for the whole suite. Salesforce announced Customer 360 at Dreamforce on 25 September 2018. The press release introduced it as "a new way for companies to connect Salesforce apps" with three ideas: an admin interface to connect orgs and map data across clouds "with clicks, not code", a single customer ID recognised across Salesforce apps, and pre-built packages for Service, Marketing and Commerce clouds. It was in pilot then, with general availability planned for 2019. Since then the data side has grown into a full data platform, now called Data 360.
What does Customer 360 include?
Customer 360 includes every Salesforce cloud you license, plus the data, AI, collaboration and integration products that connect them.
| Area | Main products | What it adds to the customer view |
|---|---|---|
| Sales | Sales Cloud | Accounts, contacts, opportunities, activity history |
| Service | Service Cloud, Field Service | Cases, conversations, service visits |
| Marketing | Marketing Cloud | Campaign engagement, consent, preferences |
| Commerce | Commerce Cloud | Orders, carts, browsing |
| Partners and portals | Experience Cloud | Self-service and partner activity |
| Industries | Health, Financial Services, Manufacturing and other industry clouds | Sector-specific records such as policies, patients or assets |
| Data | Data 360 | Unifies all of the above with data from outside Salesforce |
| AI | Agentforce | Agents that act on the unified view |
| Collaboration and analytics | Slack, Tableau | Teams and dashboards working from the same data |
| Integration | MuleSoft | Connects ERP, billing and legacy systems |
Customer 360 vs Data 360: what is the difference?
Customer 360 is the suite; Data 360 is its data engine. Salesforce's Data 360 page confirms that Data 360 is the new name for Data Cloud and says it unifies data into a single, trusted Customer 360 profile. The Data 360 architecture guide describes how it works:
- Ingest: data arrives from Salesforce apps through native connectors and from other systems, or is read in place through zero-copy federation without being moved.
- Harmonise: raw fields are mapped to data model objects in the standard Customer 360 Data Model, so an email address means the same thing whatever system it came from. Giving data from every source the same structure is what lets support tickets, orders and web visits sit on one profile.
- Resolve identity: matching and reconciliation rules link records for the same person into a unified profile. Identity resolution does not overwrite the source values; the unified profile works as a set of keys back to the source data.
- Act: segments, calculated insights and Agentforce agents use the unified profiles to personalise campaigns, service and sales.
On cost, the Data 360 page says, as of November 2026, that its pricing is consumption-based, so you pay for the services you use, and that existing Data Cloud agreements are honoured until the end of their current term. Model usage on real data volumes before you commit.
How to build a single customer view
Find every source of customer data, connect it, clean and match it, use it, and train people. Salesforce's guide to the 360-degree customer view sets out five steps, which match what works in practice:
- Find every system that holds customer data: CRM, ERP, billing, support, ecommerce, partner and third-party sources.
- Integrate it, by zero copy or ETL, into one place.
- Clean and deduplicate it with identity resolution, and apply security and governance.
- Act on it with analytics, AI models or agents.
- Train people and manage the change, so teams actually use the new view.
Steps 1 to 3 are where most projects stall. Before buying anything, map your Salesforce data model, clean duplicate contacts, and plan the integrations you need; our data migration strategies cover moving legacy data in, and Salesforce objects explains the records involved.
Do you need Data 360 for a 360-degree view?
Not always: if most customer data already lives in one clean Salesforce org, good data design may be enough; Data 360 earns its place when data is spread across many systems.
| Your situation | Likely approach |
|---|---|
| Most customer data already lives in one Salesforce org | Clean data model, deduplication and a few integrations; Data 360 optional |
| Several Salesforce orgs | Consider org consolidation or Data 360 to unify them |
| Customer data spread across ERP, ecommerce, apps and data warehouses | Data 360, with zero copy for warehouse data |
| Real-time personalisation or AI agents that need full customer context | Data 360 with Agentforce |
Common mistakes
Most Customer 360 projects stumble on data quality and ownership, not technology.
- Buying the label, not the outcome. Define which decisions the customer view must support, then pick products.
- Skipping data quality. Unifying dirty data gives you a unified mess; fix duplicates and required fields first.
- Treating it as an IT project. Sales, service and marketing must agree on what a customer record means.
- Ignoring consent. A complete view must still respect what each customer agreed to; see our security guide.
Getting help
For the AI side, see Salesforce AI vs traditional CRM. A real single customer view needs the right products, a clean data model and integrations that hold up. Techila is a Salesforce Summit Partner; our Data Cloud (Data 360) services team plans and implements unified customer data on Salesforce. Talk to us about what a Customer 360 would look like for your business.
Frequently asked questions
What is Salesforce Customer 360?
It is Salesforce's name for its suite of unified apps, for sales, service, marketing, commerce, IT, industries and partners, that share one platform and one view of each customer. Salesforce describes it as the application layer of its agentic enterprise architecture, with Agentforce built into every app.
Is Customer 360 a product you can buy?
Not as one licence. You buy the individual products, such as Sales Cloud, Service Cloud or Data 360, or a suite such as Starter or Pro. Together they make up Customer 360. The phrase also describes the goal: a single, complete view of each customer.
What is the difference between Customer 360 and Data 360?
Customer 360 is the whole suite of apps. Data 360, formerly Data Cloud, is the data engine within it that brings customer data from Salesforce and other systems together, resolves duplicates into unified profiles, and makes that data available to apps, analytics and AI agents.
When did Salesforce launch Customer 360?
Salesforce announced Customer 360 at Dreamforce on 25 September 2018, as a way to connect Salesforce apps and create one customer ID across them. It was in pilot then, with general availability planned for 2019.
Do I need Data 360 to get a 360-degree customer view?
Not always. If most of your customer data already lives in one Salesforce org, a clean data model and good integrations give a strong single view. Data 360 earns its place when data is spread across many systems, when you need identity resolution across them, or when you want real-time segments and AI grounded in all of it.