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.

Type
Resource
Topic
Resource
Reading time
4 min
Updated
Author
GeekMidst Team
Reviewed by
Site owner
Talk to an expert
Cover of the GeekMidst Data Cloud Services FAQ (faq), listing sections: How a first Data Cloud phase usually runs, Agree the use case, Profile the sources

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?
Not always. A warehouse is built for analytics and reporting, while Data Cloud is built to resolve identities and act on profiles inside Salesforce. Many organisations use both, and the two can complement each other.
What is a sensible first use case?
One with a clear audience, two or three data sources and an activation target you already use, such as a segment sent to Marketing Cloud Engagement for a single journey. Starting narrow proves the data model before you scale it.
Which data sources can it ingest?
Salesforce clouds through native connectors, cloud storage files, ingestion APIs for streaming and batch data, web and mobile SDKs, and selected external data platforms. Check the current connector list in Salesforce Help, as it changes between releases.
Do we have to copy all our data into Data Cloud?
No. Salesforce supports data federation (zero copy) with selected external platforms, so some data can be queried in place. Whether that suits your case depends on volume, latency needs and how the data is used.
How does identity resolution work?
Match rules decide which source records belong to the same person, for example an exact match on a normalised email, and reconciliation rules decide which value wins for each attribute on the unified profile.
How much data cleansing is needed first?
Enough that your main identifiers are trustworthy. Poor email or phone quality leads to over-merged or under-merged profiles, so we profile key fields before configuring match rules.
How are Data Cloud costs calculated?
Data Cloud uses a usage-based model where activities such as ingestion, processing and activation consume credits. Rates and contract terms vary, so confirm them with your Salesforce account team. We help estimate which design choices drive usage.
Can segments be sent to Marketing Cloud Engagement?
Yes. Segments can be activated to Marketing Cloud Engagement, where they arrive as data extensions that journeys and sends can use. Refresh timing and attribute choices need to be designed carefully.
What are calculated insights?
They are metrics defined with SQL over your data model objects, such as lifetime spend or days since last order, that can be used in segmentation and activation.
How is consent handled?
Consent and contact point data can be ingested and modelled so segments respect it, but the rules must come from your business and legal teams. We design the model and test that suppressions work before any activation.
Does Data Cloud support Agentforce?
Yes. Data Cloud provides the data foundation that Agentforce and other Salesforce AI features use for grounding. Which data is exposed to an agent should be a deliberate, reviewed decision.
How long before we see something useful?
A narrow first use case can reach a working segment much sooner than an enterprise-wide rollout. The biggest variable is usually how quickly source data and access are made available.
What do you need from us to start?
A business owner, access to a Data Cloud org or sandbox, sample extracts or connector access for the first sources, and someone who understands what each source field means.
Can you help after the first use case is live?
Yes. Typical next steps are adding sources, refining match rules, building calculated insights and monitoring job health and refresh schedules.

How a first Data Cloud phase usually runs

  1. 01

    Agree the use case

    Define the audience, the action you want to take and how you will measure it.

  2. 02

    Profile the sources

    Check identifiers, volumes, grain and quality for the first two or three sources.

  3. 03

    Model and map

    Map data streams into data model objects at the correct grain and document every mapping.

  4. 04

    Resolve identities

    Configure and test match and reconciliation rules against known sample customers.

  5. 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.

Talk to a Data Cloud consultant →

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation