Salesforce Data 360
Quickstart

The Data 360 Quickstart is a fixed-scope engagement that puts one Data 360 use case into production, such as a marketing segment, a unified service view or customer context for an Agentforce agent. We agree the use case, sources, deliverables, duration and price in a scoping call and fix them in writing before work begins.

We don't publish a standard duration or price, because both depend on your sources and the use case you pick. What is fixed is the shape: one use case, a short list of sources, one ruleset, the insights and segments that use case needs, and one activation that someone in your business uses.

A first use case covers the full Data 360 path once: data streams from a small set of sources, mapping to data model objects, an identity resolution ruleset, the calculated insights and segments the outcome needs, and one activation to a target system. Running every step end to end shows where your data needs work before you scale.

• Data streams. Connections to the sources the use case needs, usually your Salesforce org through the CRM connectors plus one or two others. Each stream lands in a data lake object, and transforms clean it on the way in.
• Mapping. Data lake object fields mapped to standard or custom data model objects, including the custom fields the use case depends on.
• Identity resolution. One ruleset with match rules (exact, fuzzy or normalized) and reconciliation rules, tested against a sample of your real records.
• Calculated insights and segments. The SQL metrics and audiences the use case relies on, with written definitions your team signs off.
• Activation. One activation target, such as Marketing Cloud or Data 360 itself, with the segment published to it. Where the use case is agent context, this step is a search index and retriever used by one prompt template.

Typical first use cases are a re-engagement or high-value segment for Marketing Cloud, a unified customer view for service agents, or Data 360 grounding for one Agentforce agent. We help you pick the one with clear value and data that is ready enough.

You get one working use case in your org and the documents to run and extend it: a source inventory, the data model mapping, the identity resolution rules and their test results, insight and segment definitions, a live activation, a usage review against Salesforce's consumption model, and a plan for what to build next.

Before the build starts you need Data 360 provisioned in your org, admin access for our team, access to the sources in scope, a named business owner for the use case, and your current consent records. Salesforce says its customers can provision Data 360 for free with a limited amount of storage and consumption credits.

1. Data 360 provisioned. In the Salesforce org the use case will run in, with the licenses or credits you plan to use beyond the free allocation.
2. Access. Admin access to the org and credentials or a contact for each source system in scope.
3. A business owner. One person who decides what the segment or view must contain and signs off the definitions.
4. Consent data. Where the use case contacts customers, the current opt-in and opt-out records by channel. Trailhead notes consent in Data 360 is tied to each contact point, such as an email address.
5. A target system. The Marketing Cloud account, commerce site or Agentforce agent the activation goes to, already set up.

The Quickstart leaves out anything that turns one use case into a program: more than the agreed sources, custom integrations to systems without a connector, migration of historical data beyond what the use case needs, multiple data spaces, enterprise governance design, and building the Marketing Cloud journeys or Agentforce agents that consume the activation.

• Sources beyond the agreed list, and custom MuleSoft or API feeds for systems without a ready connector.
• Clean-up of source systems themselves; we document data quality issues and fix only what the use case needs inside Data 360.
• More than one identity resolution ruleset, or data spaces for several brands or regions.
• Enterprise-wide governance design, tagging and policy frameworks.
• Journeys, campaigns, agent design and testing in the systems that use the activation.
• Ongoing support after handover, which can be arranged separately.

Items outside scope are not lost: they go into the next-step plan with the reason they matter. Feeds from systems without connectors are usually built by our MuleSoft team.

A Quickstart extends by reusing what it built. The data streams, mapping and identity rules stay in place, and the next phase adds sources, use cases and activations on the same foundation. Teams often move next to Agentforce grounding, more Marketing Cloud segments, or zero-copy access to an existing Snowflake, Databricks, Redshift or BigQuery warehouse.

• More sources and use cases through a full Data 360 implementation.
• AI agents grounded in unified profiles through Agentforce implementation.
• Systems without connectors through Salesforce integration services and MuleSoft.

To agree a first use case, book a scoping call.