What is Salesforce Data Cloud (Data 360)?
The short answer
Salesforce Data Cloud (rebranded to Data 360 on October 14, 2025) is Salesforce’s data platform for bringing in data from many sources, mapping it into a consistent model, unifying identities into profiles, and then building segments/insights you can activate across Salesforce apps and connected destinations.
Who this cloud is for
Most organizations don’t struggle because they lack data, they struggle because their data is spread across systems (CRM, website/app, commerce, support, data lake/warehouse) and can’t be reliably connected to the same person or account. Data Cloud is designed to fix that by making unified customer data usable for real workflows, not just reporting.
If you need a “single view” of customers but records are fragmented across tools → you need a layer to ingest + harmonize + unify data.
If you can’t confidently determine when two records are the same person/business → you need identity resolution (matching + reconciliation rules).
If you want that unified data to drive outcomes (campaigns, journeys, personalization, analytics) → you need segmentation, insights, and activation.
What Data Cloud does
Think of Data Cloud as a pipeline:
Ingest data from Salesforce and non-Salesforce sources (including file/object storage and some “zero-copy” patterns into existing lakes/warehouses).
Harmonize/map the data into a consistent structure (so different source fields can be aligned to a common model).
Unify identities into profiles using identity resolution (match rules + reconciliation rules).
Build segments and insights so teams can actually use the data in tools and workflows.
How Data Cloud organizes your data (the parts you’ll hear in implementations)
Salesforce documentation and architecture guidance commonly refer to a layered approach where ingested data is mapped into standardized model objects, enabling unified profiles, segmentation, and activation.
Here’s the practical takeaway:
Source data comes in messy (different schemas, naming, IDs, formats).
You map it into a consistent model.
Then you can unify identities and use the data for segments, analytics, and activation.
If you’re planning implementation, this is why “mapping” and “identity resolution rulesets” tend to be the critical path—not dashboards.
What is a “unified profile” in Data Cloud?
A unified profile is the result of identity resolution: Data Cloud links together records from multiple sources that refer to the same person or business, using match rules and reconciliation rules.
Matching vs reconciliation (quick mental model)
Match rules determine which records should be unified (based on criteria and match methods).
Reconciliation rules determine which value “wins” when the unified profile can store only one value for a field.
Identity resolution can run in scheduled or real-time modes, using the same reconciliation rules.
Want the deeper version? Read: /data-cloud-identity-resolution-guide/
What are segments and activations?
Data Cloud supports building segments (groups based on attributes/behaviors) and then activating those segments so they can be used in downstream tools and destinations.
Practical examples of activation include:
Sending segments to marketing or ad destinations (Salesforce publishes multiple activation-related capabilities and release notes for destinations).
Using segments and unified data to power customer engagement across Salesforce products.
If you’re focused on outcomes, read: /data-cloud-activation-use-cases/
Where Data Cloud fits in the Salesforce ecosystem
Salesforce positions Data Cloud / Data 360 as a way to connect data to CRM apps and other sources so teams can act on unified data in the tools they already use.
You’ll commonly see it described alongside Salesforce clouds like:
Salesforce CRM products (including Sales Cloud and Service Cloud)
Marketing Cloud Engagement (cross-cloud marketer workflows often reference Data Cloud segments feeding journeys)
Common “is it right for us?” questions
Do we need Data Cloud if we already have a data warehouse?
Some teams use Data Cloud alongside warehouses/lakes, including “zero-copy” patterns for specific platforms so data can be used without duplicating it in the same way you would with traditional ETL. Examples mentioned by Salesforce include Snowflake and Databricks.
Do we need Data Cloud if our CRM data is already in Salesforce?
If your critical customer signals also live outside CRM (web/app behavior, commerce, product usage, support tools, storage systems like Amazon S3 or Google Cloud Storage), Data Cloud is positioned as a way to ingest and unify that data so it can be used across customer experiences.
How should we think about implementation effort?
Salesforce’s own learning and implementation materials emphasize foundations: connecting sources, mapping/harmonization, identity resolution, then segmentation/activation—plus governance and security practices.
Next read: /data-cloud-implementation-steps/
Frequently Asked Questions
Is “Data 360” different from Data Cloud?
Salesforce states Data Cloud was rebranded to Data 360 on October 14, 2025, and the functionality remains the same while references transition across the product and documentation.
What’s the fastest way to get value?
In practice, value tends to come fastest when you start with:
A few high-impact sources
A clear identity strategy (match + reconciliation)
One or two activation use cases you can measure
This lines up with Salesforce’s emphasis on mapping + identity resolution + segmentation/activation as core building blocks.
Book time with our team to talk Data Cloud
If you’re evaluating Salesforce Data Cloud (Data 360) or trying to move from “unified data” to real activation outcomes, we can help you get to a clear plan.
In a short working session, we’ll help you:
Pick the best first use case (not the biggest, the one that proves value fastest)
Pressure-test your identity resolution approach (match rates, profile quality, field priority)
Define what “good” looks like for segments + activation so ROI is measurable