Salesforce Data 360 Foundation Setup

Start with One Defined Data and Activation Use Case

We begin by confirming which customer or account data should be unified, which source systems are in scope, what downstream Salesforce process should use the result, who owns data quality, and how success will be measured. Salesforce Data 360 is then configured around one approved foundation use case so source connection, modeling, identity resolution, profile validation, segmentation, activation, access, and governance follow one shared plan rather than an open-ended data-platform program.

Prepare One Data 360 Environment

One client-provided Salesforce org with active Data 360 licensing is reviewed and prepared for the included use case. The setup includes provisioning and feature-readiness confirmation, one primary data space using the default data space unless another licensed structure is approved, foundational naming conventions, and focused administrative settings. Additional Salesforce orgs, multiple data spaces, business-unit separation, cross-org architecture, development-environment strategy, and enterprise platform governance remain separate.

Define the Source and Ownership Plan

One source-system and data-readiness workshop documents the approved profile entity, source ownership, identifiers, update expectations, required fields, consent or preference considerations supplied by the client, and downstream activation goal. Up to three source systems can be assessed for the foundation plan, while implementation includes Salesforce CRM and up to one additional supported source when credentials, connector availability, permissions, and technically usable data are provided by the client.

Connect Focused Data Streams

Up to six approved data streams can be configured across the included sources using supported native ingestion or connection methods. The scope covers connection setup, object or table selection, refresh settings where supported, and an initial ingestion review. Custom APIs, middleware development, unsupported connectors, high-frequency streaming architecture, event pipelines, historical backfills beyond available connector behavior, and troubleshooting defective source systems are outside the fixed scope.

Map Raw Data into the Customer 360 Model

Up to eight included Data Lake Objects can be reviewed and mapped to up to eight standard or approved custom Data Model Objects using the Customer 360 Data Model. Up to 60 approved source attributes can be mapped across the included model, subject to compatible data types, required identifiers, relationships, and source quality. Large custom data models, industry data-model programs, complex relationship redesign, semantic-layer implementation, and enterprise canonical-model development remain separate.

Apply Focused Data Preparation

Up to two straightforward batch or streaming data transforms can be configured where supported to normalize, combine, derive, or prepare fields required by the approved model. The included work can address focused formatting, value standardization, field derivation, or source alignment identified during implementation. Large-scale cleansing, survivorship engineering, address standardization, third-party enrichment, reference-data management, custom code, and master data management are not included.

Create One Identity Resolution Foundation

One identity-resolution ruleset is configured for either individuals or accounts using up to five approved match rules and up to three straightforward reconciliation rules. The rules use available identifiers and contact points supplied by the client to link source records into unified profiles. Identity resolution provides a system of reference for connected source profiles; it does not replace the source systems or create a traditional master-data-management golden record.

Validate Unified Profiles and Match Quality

One focused profile-validation cycle reviews unified-profile output, source links, contact points, match behavior, and obvious overmatch or undermatch patterns using up to 20 agreed test profiles or scenarios. One fixed-scope refinement round can adjust the included identity rules when the approved requirements remain unchanged. Production match quality depends on source completeness, identifier stability, duplicate patterns, consent controls, and the client’s ongoing data stewardship.

Create Initial Insights and Segments

Up to three straightforward calculated insights can be configured where supported using the included mapped data, together with up to three approved standard segments for the foundation use case. Examples can include profile counts, recent activity, customer value supplied by source records, engagement recency, account status, or another agreed measure supported by the available relationships. Real-time insights, complex SQL, predictive models, large insight libraries, nested segmentation, and multi-brand audience strategy remain separate.

Prepare One Controlled Activation Path

One supported activation target and up to two approved segment activations can be configured for one available Salesforce or external destination included in the client’s licenses and connector access. The setup covers target authentication, selected membership, approved attributes, schedule settings where supported, and one validation cycle. Additional destinations, advertising-platform strategy, bidirectional integration, activation-triggered custom flows, MuleSoft, webhooks, data actions, and real-time orchestration remain separate.

Align Access and Foundational Governance

Standard Data 360 permission sets and basic access are aligned for up to 10 named users across approved administrator, data, segmentation, or activation responsibilities. One foundational role-based access review is included for the selected data space and included objects. Up to 12 approved business or sensitivity tags can be documented or applied where the client’s licensed governance capabilities support them. Advanced role-based or attribute-based access policies, multiple data spaces, automated classification, privacy automation, consent architecture, policy engines, clean rooms, data sharing, and enterprise governance programs remain separate.

Test, Document, Train, and Hand Off

We run one controlled test cycle across up to 25 agreed scenarios covering source connection, ingestion, mapping, transforms, identity resolution, unified profiles, calculated insights, segments, activation, permissions, and the approved governance controls. One fixed-scope correction round is included when the original requirements remain unchanged. The client receives a Data 360 source-and-model map, configuration summary, basic consumption-awareness guidance, future AI-readiness recommendations, two 60-minute handoff sessions, and 21 calendar days of launch support. Data 360 licenses and consumption credits, additional storage or processing, Zero Copy, additional sources or destinations, real-time data, unstructured data, Data Graphs, Tableau, Marketing Cloud, MuleSoft, Data Cloud One, Data Spaces add-ons, advanced governance, consent management, Data Cloud encryption, Agentforce or AI configuration, predictive models, data migration, custom development, integrations, and third-party fees are separate.