Setting up Data Cloud is a multi-month exercise that touches data sources, identity resolution, data modeling, segmentation, and activation. It is significantly more complex than configuring traditional Sales Cloud or Service Cloud. Plan with an experienced data architect and a phased rollout; trying to ingest everything at once produces overwhelming complexity.
- Define the unified data model and identity strategy
Decide which customer types matter (B2C individuals, B2B contacts, both), which data sources will feed in, and what identity resolution strategy applies. The data model is the foundation; trying to change it after data is loaded is painful.
- Provision Data Cloud and configure the connected org
Setup > Data Cloud > Setup. Connect to the Sales Cloud or Service Cloud orgs that source customer data. Configure data spaces (logical containers, often one per business unit or region).
- Set up data streams from each source
Add data streams for each source: Salesforce CRM, marketing platforms, data warehouses, web analytics, mobile event streams. Configure the schema and refresh frequency for each stream.
- Map data streams to Data Model Objects
Data Cloud ships standard DMOs (Individual, Account, Order, Engagement, Email Engagement). Map fields from your data streams to the appropriate DMOs. Customize DMOs where the standard model does not fit.
- Build identity resolution rules
Setup > Identity Resolution. Define match rules with deterministic and probabilistic logic. Run the resolution job and review the unified profiles. Tune rules iteratively until the merge quality matches expectation.
- Define calculated insights
Setup > Calculated Insights > New. Build the insights that downstream consumers need: LTV, churn probability, segment membership scores. Each insight becomes a queryable attribute on the unified profile.
- Build segments and configure activations
Setup > Segments > New. Define audiences using profile attributes and insights. Configure activations to target destinations: Marketing Cloud, Sales Cloud, ad platforms, custom APIs.
- Connect to Agentforce and Prompt Builder for AI grounding
Expose Data Cloud DMOs as grounding sources in Agentforce and Prompt Builder. AI features can then query unified profiles and insights directly during agent conversations and prompt invocations.
Salesforce CRM, cloud storage, streaming, marketing platforms, custom APIs. Drives what data flows into Data Cloud.
Deterministic and probabilistic match rules that merge customer records across sources into unified profiles.
Where Data Cloud sends segment membership: Marketing Cloud, Sales Cloud, ad platforms, custom APIs.
- Data Cloud is consumption-priced. High data volumes and activations produce significant credit consumption. Monitor usage and plan budget alongside the implementation.
- Identity resolution requires iteration. The first version of match rules rarely produces perfect merges. Plan multiple tuning cycles with real data before declaring identity resolution complete.
- The data model is foundational. Changing the Data Model Object structure after data is loaded triggers reprocessing across millions of records. Get the model right early.
- Data Cloud is operationally separate from base Salesforce. The familiar admin patterns (page layouts, profiles, sharing rules) differ in Data Cloud; learning the platform-specific UX takes time.
- Activations have latency. Real-time activations exist but most ingestion and segmentation runs on minute-to-hour cycles. Plan downstream use cases around the latency profile.