Salesforce Data Cloud (Data 360): What It Is + How to Use It
The short answer
Salesforce Data Cloud (rebranded to Data 360 as of October 14, 2025) is Salesforce’s platform for ingesting, harmonizing, unifying, and analyzing streaming + batch data, and then using that data to power experiences across Salesforce apps and connected destinations.
Who this cloud is for
Most teams don’t have a “data problem”, they have a fragmentation problem: different systems hold partial, conflicting versions of the customer. Data Cloud is designed to unify that data into profiles and make it usable for marketing, sales, service, commerce, analytics, and automation.
If your customer data lives across CRM + web/app + commerce + support + data lake/warehouse → you need a way to bring it together consistently.
If you can’t reliably tell whether two records are the same person/business → you need identity resolution with matching + reconciliation rules.
If you want that unified data to drive outcomes (campaigns, journeys, ads, personalization, workflows) → you need segmentation + activation patterns.
What Salesforce Data Cloud is
Salesforce positions Data Cloud (Data 360) as a way to consolidate and process large volumes of data from various sources, connect it with Salesforce CRM data, and create insights at scale, including working with very large record volumes.
Key capabilities at a glance
Data Cloud is commonly explained as a flow:
Ingest data (streams/connectors; can be streaming, scheduled, and “zero-copy” access for some external platforms)
Map/harmonize data into a consistent model (so “Contact/Customer/Guest” can map to a common “Individual” concept)
Unify identities into profiles via identity resolution (matching + reconciliation)
Generate insights & segments (calculated insights, streaming insights, segmentation)
Take action (activations, data actions, enrichments, automation, analytics)
How Data Cloud structures data (so teams can actually use it)
Salesforce’s own breakdown highlights the objects and stages used to move from raw data to unified, actionable data:
Data Source Objects (DSOs): containers for initial raw data brought in.
Data Lake Objects (DLOs): created as data is ingested; can be augmented with transforms/formulas.
Data Model Objects (DMOs): the standardized/common structure (standard + custom) used for consistent downstream use cases.
Calculated Insights (and other insight types): derived metrics used to analyze behavior and improve segmentation.
Practical implication: When your team debates “which system is the source of truth,” Data Cloud’s model encourages you to map sources into a common structure and then define how identities and field values should be unified.
Identity resolution: how profiles get unified
Salesforce describes identity resolution as the capability that connects records across systems into a single profile when there isn’t a universal identifier.
How to think about matching (simple mental model)
Match rules define who should unify (criteria + match methods like exact, fuzzy, normalized exact).
Identity resolution can run as scheduled or real-time, depending on your needs.
Reconciliation rules help decide which value wins on the unified profile (Salesforce describes approaches such as “last updated,” “most frequent,” and “source priority”).
Learn more: Identity resolution: how to think about profiles & matching
Segmentation and activation: turning unified data into outcomes
Salesforce describes segmentation as a way to break down data into useful groups and publish them on a schedule or as needed.
Salesforce also outlines multiple creation paths:
No-code segment building in the UI Segment Builder
Programmatic approaches (example: dbt created via API)
And once you have segments, Salesforce describes “out-of-the-box” ways to activate segments to destinations such as marketing services, data lakes, or SFTP.
The decision logic for activation
If the destination is a Salesforce execution surface (CRM, Marketing, Commerce) → use activation patterns that publish segments/attributes into that environment.
If the destination is an external platform (storage/ad/partners) → use activation targets/data shares/APIs depending on the integration pattern.
Learn more: Data Cloud activation: 10 use cases that drive ROI
Implementation: the steps most teams follow
Salesforce’s Data Cloud materials consistently imply a build sequence that looks like:
Identify sources + use cases (start with outcomes, not ingestion)
Connect/ingest data (streams, connectors, schedules/real-time; some “zero-copy” patterns exist)
Map to the model (create consistent objects/fields for downstream teams)
Configure identity resolution (match + reconciliation rulesets; test and iterate)
Create segments + insights (calculated insights and other insight types)
Activate and operationalize (journeys, audiences, workflows, analytics)
Add governance + monitoring (consent, access controls, retention/compliance)
Learn more: Data Cloud implementation steps
Governance: consent, access, retention
If you’re centralizing customer data, governance stops being optional.
Consent (practical framing)
Salesforce Privacy Center positioning includes the ability to store consent in Data 360 to help honor consent related to data you feed into marketing tools like Marketing Cloud.
Retention + compliance artifacts
Salesforce’s compliance site provides service-level documentation references for Data Cloud (including Security/Privacy/Architecture documentation and audit/certification resources).
Learn more: Data Cloud governance: consent, access, retention
Measuring success: KPIs that map to the Data Cloud lifecycle
A useful KPI set aligns to the “ingest → unify → activate” flow:
Time-to-insight: how quickly you can answer a question with unified data (often improves as mapping and standardization mature).
Match rates / profile quality: how well identity resolution is unifying records (improves as match rules and data quality improve).
Activation lift: whether segments and triggered actions improve downstream outcomes (engagement, conversion, retention).
Learn More: Data Cloud KPIs: time-to-insight, match rates, lift
Where Data Cloud fits (and how to evaluate alternatives)
When teams evaluate a CDP or “data cloud” approach, the key fit questions usually aren’t feature checklists, they’re about:
Whether the product can unify identities reliably,
Whether segments/insights are easy to operationalize,
Whether governance/compliance requirements can be met in your environment.
Learn More: Data Cloud vs CDP Alternatives: How to Evaluate Fit (Salesforce Data 360)
Data Cloud + Marketing Cloud: when “just segmentation” isn’t enough
A common failure mode is treating segmentation as a one-off list pull instead of a living system that updates as behavior changes.
Salesforce describes dynamic segmentation and the ability to update segments as customer behaviors or attributes change (to keep them relevant). And Salesforce Trailhead guidance shows Data Cloud segments being available inside Marketing Cloud Engagement flows (example: selecting a Data Cloud segment in Journey Builder).
Learn more: Data Cloud + Marketing Cloud vs Segmentation Only: Decision Guide
Frequently Asked Questions
Is Salesforce Data Cloud the same as Data 360?
Salesforce states that Data Cloud was rebranded to Data 360 on October 14, 2025, and during the transition you may see both names in the product and documentation.
What does Data Cloud actually do?
Salesforce describes it as a platform to ingest, harmonize, unify, and analyze data (streaming + batch), then use that data to unlock experiences across channels.
What are segments and activations?
Salesforce describes segments as groups you build from your data model and publish on a schedule or as needed. It also describes activation as publishing segments to activation platforms, with out-of-the-box ways to send segments to destinations (including file-based and other platforms).
Talk to a Salesforce Data Cloud expert
If you’re evaluating Salesforce Data Cloud (Data 360), planning an implementation, or trying to unlock real activation value, not just unified profiles, our team can help.
We work with Salesforce teams to:
Clarify which Data Cloud use cases actually matter for your business
Design identity resolution strategies that balance match quality and scale
Translate unified data into segments, journeys, and measurable outcomes
Avoid common pitfalls around governance, consent, and activation
If you want to sanity-check your approach or see how Data Cloud fits into your existing Salesforce stack, book time with us.