Data Cloud Services FAQ
Plain answers to the questions teams ask before a Salesforce Data Cloud project: fit, data sources, identity resolution, activation, consent and where to begin.

Data Cloud (now branded Data 360) brings customer data from Salesforce and external systems into a harmonised model, resolves it into unified profiles, and makes those profiles available for segmentation, insights, activation and AI features such as Agentforce. It is powerful and it is easy to start in the wrong place.
These are the questions we hear most before a Data Cloud engagement. They are grouped roughly from "should we?" to "how does it run?".
Data Cloud services: common questions
Do we need Data Cloud if we already have a data warehouse?
What is a sensible first use case?
Which data sources can it ingest?
Do we have to copy all our data into Data Cloud?
How does identity resolution work?
How much data cleansing is needed first?
How are Data Cloud costs calculated?
Can segments be sent to Marketing Cloud Engagement?
What are calculated insights?
How is consent handled?
Does Data Cloud support Agentforce?
How long before we see something useful?
What do you need from us to start?
Can you help after the first use case is live?
Related reading
- Salesforce Data Cloud consulting: how GeekMidst designs and delivers Data Cloud programmes.
- Data Cloud vs a traditional data warehouse: where each fits and how they coexist.
- How identity resolution match rules work: match and reconciliation rules in detail.
- Activating Data Cloud segments to Marketing Cloud: timing, attributes and validation.
- Data Cloud readiness checklist: what to have in place before you start.
How a first Data Cloud phase usually runs
- 01
Agree the use case
Define the audience, the action you want to take and how you will measure it.
- 02
Profile the sources
Check identifiers, volumes, grain and quality for the first two or three sources.
- 03
Model and map
Map data streams into data model objects at the correct grain and document every mapping.
- 04
Resolve identities
Configure and test match and reconciliation rules against known sample customers.
- 05
Build and activate
Create insights and segments, activate to the target and validate counts end to end.
Considering Data Cloud?
We can help you decide whether it fits, define a first use case worth proving and design a data model you will not have to unpick later.




