Implementing Customer 360 is a multi-product, multi-quarter program. The framing is simple; the work of unifying data and processes across clouds takes years for large enterprises.
- Define the customer record schema
Agree across Sales, Service, Marketing, and Commerce on what defines a customer (Account vs Person Account, what makes two records the same customer, what fields constitute the unified profile). Documentation precedes configuration.
- Stand up Data Cloud
Provision Data Cloud, configure connectors to each Salesforce cloud and external data source, build the unified profile, and validate identity resolution. This is the heart of the implementation.
- Configure cross-cloud integration
Set up Marketing Cloud Connect, Salesforce Connect external data sources, or MuleSoft flows for the specific cross-cloud data needs. Start with the highest-business-value flows (lead-to-pipeline, service-to-marketing).
- Implement the unified UI
Surface Customer 360 data in each cloud user interface. Salesforce ships Lightning components and templates for many patterns; custom builds extend them for industry-specific needs.
- Build the analytics and AI layer
Connect Tableau, Einstein analytics, or Tableau Pulse to the Data Cloud unified profile. Roll out Agentforce or other AI agents that read from and write to the unified data.
- Govern and iterate
Customer 360 is not done once configured. Data hygiene, identity resolution accuracy, and process alignment require ongoing governance. Build a Customer 360 council with cross-cloud representation.
- Customer 360 cannot be deployed by a single team. Sales, Service, Marketing, and IT must each contribute; without joint sponsorship, the project stalls.
- Identity resolution failures are the most common Customer 360 issue. Different teams maintain Lead and Contact and Account records independently; mismatches propagate everywhere.
- Cloud-to-cloud data sync introduces latency. Real-time UX expectations need to be tempered by the sync timing of the underlying integrations.
- Salesforce rebrands Customer 360 components occasionally. Customer 360 Truth, Customer 360 Data Manager, and Customer 360 Audiences have all been positions for different products at different times; check current Salesforce documentation.
- Customer 360 budgets often underestimate the data engineering cost. Data Cloud itself is expensive, and the human cost of data cleanup before identity resolution can be sizeable.