Salesforce Data Cloud: What It Is and How It Works (2026)

Salesforce Data Cloud is Salesforce’s real-time customer data platform – the infrastructure layer that ingests data from Salesforce products and external systems, resolves customer identity across data sources, creates unified customer profiles, and activates those profiles to power personalisation and automation across the Salesforce platform. Formerly called Salesforce CDP (Customer Data Platform) and then Genie, rebranded as Data Cloud in 2022, it is now one of Salesforce’s fastest-growing products and the technical foundation of the Customer 360 vision. This guide covers what Data Cloud actually does, how it works technically, what it costs, and the specific problems it solves that standard Salesforce integration does not.

The best guide is the one that shows how data becomes easier to activate.

A practical explanation should help the reader see where the platform fits in a modern stack.

That means the guide should focus on both data connection and practical application.

For many businesses, the value is in making data more usable across sales, service, and marketing.

It should also show why the product matters when a team needs a more complete customer view.

A good guide should explain what Data Cloud does and how it differs from everyday CRM data storage.

That makes it especially relevant for businesses trying to unify data across departments and channels.

Salesforce Data Cloud is useful because it gives teams a way to bring together data from different sources and use it in a more connected way across the platform. It is aimed at organisations that need a broader data layer than a standard CRM record.

How Salesforce Data Cloud Works

1. Data Ingestion

Data Cloud ingests data from multiple sources through native connectors and APIs:

Salesforce products: Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud, and Experience Cloud – data from all Salesforce products flows into Data Cloud natively without separate integration configuration
Web and mobile SDK: JavaScript and mobile SDK tags stream real-time behavioural data (page views, clicks, form submissions, app events) from websites and mobile apps directly into Data Cloud – capturing first-party behavioural data without a third-party analytics platform intermediary
Cloud storage connectors: Ingest data from Amazon S3, Google Cloud Storage, Azure Blob Storage, or Snowflake – batch loading structured data files from data warehouses or data lakes
Pre-built connectors: Native connectors for Google Analytics, Snowflake, MuleSoft-connected systems, and other common enterprise data sources via the AppExchange connector marketplace
Custom API ingestion: REST API endpoints for pushing custom data events directly into Data Cloud from any external system or application

2. Data Mapping and the Data Model

Ingested data is mapped to Data Cloud’s standard data model – a set of standard objects (Individual, Contact Point Email, Contact Point Phone, Sales Order, Engagement Event, etc.) that provide a common schema for customer data regardless of source. Mapping raw source data to these standard objects enables identity resolution across sources – two records from different systems can be compared against the same Individual schema to identify matches.

3. Identity Resolution

Identity Resolution is Data Cloud’s core differentiator – it matches records from different sources that represent the same real-world person and links them to a single Unified Individual record. Configuration options:

Matching rules: Define how records are compared – exact match on email address, fuzzy match on name + company, match on phone number (with normalisation for format variations), or combination rules. Multiple matching rules can be stacked – a record matches if it meets any one of the defined rules
Reconciliation rules: When multiple source records contribute data to the same Unified Individual, reconciliation rules determine which source’s value “wins” for each attribute – e.g., use the most recently updated source for email address, use Salesforce Sales Cloud as the authoritative source for account owner
Graph-based resolution: Data Cloud builds an identity graph – a network of relationships between source records and Unified Individuals – that handles transitive matching (Record A matches Record B by email; Record B matches Record C by phone; therefore A, B, and C are all the same person even if A and C share no direct matching attribute)

4. Unified Profiles and Calculated Insights

Once identity is resolved, each Unified Individual has a profile that aggregates attributes from all connected source systems. Beyond raw attributes, Data Cloud computes Calculated Insights – derived metrics calculated from the unified data:

Lifetime Value: total revenue from all orders attributed to this customer across all Commerce Cloud and ERP order sources
RFM Score: Recency, Frequency, Monetary values calculated from order history
Churn Probability: derived from engagement recency, service case frequency, and usage signals
Product Affinity: which product categories the customer engages with most based on browsing and purchase history
Days Since Last Purchase: derived from the most recent Commerce Cloud order date

These Calculated Insights are available to all connected Salesforce products – Marketing Cloud can use Lifetime Value for campaign segmentation; Service Cloud can surface Churn Probability on the agent console; Sales Cloud can show Product Affinity on the Account record.

5. Segmentation

Data Cloud’s Segment Builder allows marketers and operations teams to define customer segments based on any combination of unified profile attributes, Calculated Insights, and behavioural data – without SQL or technical skills. Segments update in real time or near-real-time as customer data changes:

“High-LTV customers who have not purchased in 90 days” – a win-back segment combining Lifetime Value (Calculated Insight) and Days Since Last Purchase
“Customers who viewed the enterprise pricing page in the last 7 days and have an open Sales Cloud Lead” – a sales signal segment combining web behavioural data and CRM data
“All customers in the ‘At Risk’ churn tier based on Churn Probability score” – a customer success intervention segment

6. Activation

Segments and profile attributes are activated – pushed to connected systems for action:

Marketing Cloud activation: Segments defined in Data Cloud are available as audience sources in Marketing Cloud Journey Builder – customers entering a segment automatically enter the corresponding Marketing Cloud journey
Sales Cloud activation: Data Cloud attributes and Calculated Insights are surfaced on Salesforce Account, Contact, and Lead records – visible to sales reps in the standard CRM interface without a separate data platform login
Advertising activation: Segments are pushed to paid media platforms (Google Ads, Meta Ads, LinkedIn) as Custom Audiences – enabling consistent customer targeting across owned (email, SMS) and paid (advertising) channels based on unified first-party data
Real-time API activation: Segment membership and profile attributes are queryable via Data Cloud’s REST API – enabling any connected application to query customer segment membership in real time for personalised web experiences, in-app recommendations, or offer selection

Data Cloud Pricing

Salesforce Data Cloud is licensed based on data volume – specifically the number of Data Cloud Credits consumed, which are priced based on the volume of data ingested, profiles resolved, and activations performed. Pricing is not publicly listed and is negotiated based on data volume, number of Unified Profiles, and activation destinations. Enterprise deployments typically involve annual contracts in the $50,000-$500,000+ range depending on data scale.

Data Cloud is included in:

Einstein 1 Sales edition (for Sales Cloud use cases)
Einstein 1 Service edition (for Service Cloud use cases)
Marketing Cloud Advanced editions (for Marketing Cloud + Data Cloud bundles)

Data Cloud vs Alternatives

Segment (Twilio): The most widely used standalone CDP – strong for collecting first-party behavioural data via its SDK and routing events to downstream tools. Better for multi-cloud environments; Data Cloud is stronger when Salesforce is the primary CRM and activation target
Adobe Real-Time CDP: Enterprise competitor – comparable identity resolution and real-time activation capabilities, stronger for organisations standardised on Adobe Experience Cloud (Adobe Analytics, Adobe Commerce, Adobe Campaign)
Snowflake + dbt + Hightouch (Composable CDP): The composable CDP approach – use Snowflake as the data warehouse, dbt for transformation, and Hightouch for CRM activation. More technical implementation but more flexible for complex data environments, lower vendor lock-in, and can be cheaper at scale

Salesforce Data Cloud: From Setup to Activation

Fix: Building Identity Resolution Rules for Accurate Profile Unification

Identity resolution-the process of recognizing that “john.smith@company.com” in your CRM and “jsmith@company.com” in your e-commerce platform are the same person-is technically the hardest and most impactful part of Data Cloud implementation. Data Cloud’s Identity Resolution component uses ruleset configurations that chain match rules in priority order: exact email match first, then name plus phone match, then probabilistic fuzzy matching as a fallback. Regularly reviewing the Reconciled Profile count and sampling unified profiles for accuracy is essential for maintaining data quality over time.

Fix: Activating Data Cloud Segments Across Marketing and Service Channels

Data Cloud segments are only valuable when they can trigger personalized experiences in real-time. Data Cloud’s Activation framework connects unified segments directly to Marketing Cloud for email and mobile campaigns, Advertising Studio for paid social targeting, and Einstein Personalization for website personalization. The key activation configuration is the Activation Target and Activation Membership settings, which control how frequently segment membership is recalculated and pushed to downstream systems. Real-time streaming activations trigger within seconds; batch activations can be scheduled hourly or daily based on use case requirements.

What is Salesforce Data Cloud?

Salesforce Data Cloud is a real-time data platform that ingests, unifies, and activates customer data from multiple sources to create a single unified customer profile. It replaces the former CDP (Customer Data Platform) product and represents Salesforce’s foundational data layer for the entire Customer 360 platform. Data Cloud can ingest data from Salesforce products, external databases, data warehouses, cloud storage, and streaming event sources, resolving these disparate records into unified profiles that power personalized experiences across every channel.

How does Salesforce Data Cloud differ from a traditional CDP?

Traditional Customer Data Platforms focus primarily on marketing activation-collecting first-party data for audience segmentation and marketing campaign targeting. Salesforce Data Cloud goes beyond traditional CDPs by extending unified customer data to sales (Sales Cloud), service (Service Cloud), and AI (Einstein) use cases, not just marketing. Data Cloud also includes a zero-copy data sharing architecture through Data Cloud Sharing (formerly called Bring Your Own Lake), which enables organizations to analyze Salesforce data in external tools like Snowflake or Databricks without data replication.

How is Salesforce Data Cloud priced?

Salesforce Data Cloud uses a consumption-based pricing model centered on Data Service Credits (DSCs). Credits are consumed based on data ingestion volume, profile unification processing, and segment activation. Pricing starts with a base allocation of credits included in certain Salesforce editions, with additional credits available for purchase. For organizations with large data volumes-millions of customer profiles and high-frequency streaming data-Data Cloud costs can be significant and should be estimated carefully during the planning phase before deployment.

What Problem Does Salesforce Data Cloud Solve?

The core problem Data Cloud addresses: customer data is fragmented across multiple systems, and that fragmentation prevents personalised customer experiences at scale. In a typical enterprise:

The same customer exists as a Lead in Sales Cloud, a subscriber in Marketing Cloud, a shopper in Commerce Cloud, and a contact in Service Cloud – four separate records with different IDs, potentially different email addresses, and no native connection between them
Customer behaviour data (website visits, mobile app events, product usage) lives in external systems – Google Analytics, Amplitude, Mixpanel, or custom application databases – not in Salesforce at all
Real-time data is unavailable: batch exports and nightly ETL syncs mean that a customer’s action this morning isn’t reflected in the CRM until tonight – too slow for real-time personalisation

Standard Salesforce CRM integration (importing data via Data Loader, Salesforce Connect, or custom API integrations) partially addresses this – but does not provide identity resolution across systems, real-time data streaming at scale, or the calculated insights (derived metrics like lifetime value, churn probability, RFM scores) that enable sophisticated customer intelligence.

The best data-cloud setup is the one that turns scattered information into something useful. If the data is not connected well, the platform cannot do much with it.

Frequently Asked Questions

Challenge: Connecting Real-Time Data Sources for Unified Customer Profiles

Salesforce Data Cloud’s value depends entirely on connecting the right data sources-and most organizations have dozens of systems that contain customer data. The Data Cloud setup process involves creating Data Streams for each source (Salesforce CRM data streams come pre-built; external sources require configuring connectors for S3, cloud databases, or streaming sources). The critical architectural decision is mapping all source fields to the standard Data Model Objects (DMOs) using consistent identity keys like email address, phone number, or customer ID to enable accurate record unification across sources.

Salesforce Data Cloud supports a wide range of data sources through native connectors and the API. Native Salesforce connectors cover Sales Cloud, Service Cloud, Marketing Cloud, and Commerce Cloud. External connectors include Amazon S3, Google Cloud Storage, Azure Blob Storage, Snowflake, and Databricks. Streaming data ingestion supports real-time event streams from web and mobile applications via the Ingestion API. MuleSoft and any REST API source can also be connected through custom connector configurations.

Conclusion

Salesforce Data Cloud is the technical foundation that makes the Salesforce Customer 360 vision real – ingesting data from Salesforce products and external systems, resolving customer identity across fragmented source records, calculating derived insights from unified data, and activating profiles to power personalisation across marketing, sales, service, and advertising. Its value is proportional to data fragmentation: organisations where customer data is spread across three or more Salesforce products, external data sources, and real-time behavioural data streams derive the most from Data Cloud’s identity resolution and real-time activation capabilities. Companies operating primarily within one or two Salesforce products with native integration may not need Data Cloud’s capabilities – the native product integration (MCAE-Sales Cloud sync, Service Cloud-Sales Cloud account sharing) achieves most of the data unification without additional licensing cost.

Sources
Salesforce, Data Cloud Documentation and Product Overview (2026)
Gartner, Magic Quadrant for Customer Data Platforms (2026)
Forrester, The Salesforce Data Cloud Platform Report (2026)
Salesforce, Einstein 1 and Data Cloud Pricing Overview (2026)

Tell us how to reach you