The Question That Decides Your Salesforce CDP Architecture: Where Does the Canonical Customer Profile Live?

Angle

The Salesforce CDP evaluation is routinely framed as a binary choice: go deeper into the Salesforce-native stack (Data 360 + Agentforce) or augment with a composable layer (CDW + Hightouch). But that framing skips the prior question that actually determines which path makes sense: where does the canonical customer profile live, and who governs it? Organizations where the canonical profile is already in Salesforce CRM have a fundamentally different architecture decision than organizations where the canonical profile lives in a cloud data warehouse. The Marketing Cloud Next June 2025 consolidation — nine Salesforce marketing acquisitions onto Data 360 + Agentforce — makes the Salesforce-native path architecturally coherent in a way it wasn't before. That changes the composable evaluation, not by making composable less valid, but by making the Salesforce-native option more structurally complete. The article's editorial contribution is giving readers the canonical-profile governance question before they begin the architecture decision — because organizations that skip this alignment end up building both layers simultaneously, with no clear source of truth for either.

Key decision this helps with

Before evaluating Salesforce Data 360 vs. composable CDW+Hightouch, where does your organization's canonical customer profile currently live — and who has governance authority over it?

Tradeoffs the article will map

• Salesforce-native canonical profile (CRM-resident, Agentforce-ready, deep ecosystem integration, Data 360 as the single profile authority) vs. CDW-native canonical profile (warehouse-resident, data-science-friendly, multi-tool activation surface, independent of Salesforce contract evolution)
• Salesforce Data 360 + Agentforce unified stack (single vendor contract, consolidated governance, AI-native orchestration on Salesforce profile) vs. CDW + Hightouch composable augment (best-of-breed tool substitutability, warehouse-first query patterns, Salesforce used only as an activation destination)
• Deepening Salesforce investment post-Marketing-Cloud-Next consolidation (architectural coherence has improved; June 2025 integration reduces prior fragmentation concerns) vs. hedging Salesforce dependency (composable augmentation maintains optionality if Salesforce consolidation introduces pricing or feature lock-in)

Open questions / uncertainties

• Salesforce Data 360 is Gartner's sole CDP MQ Leader (2026) — but Gartner MQ methodology weights enterprise integration breadth, which may not be the decisive factor for all org types; the MQ Leader status is evidence of market position, not a recommendation for every context
• Marketing Cloud Next June 2025 consolidation was announced; full product integration timelines and BAA scope under Data 360 for regulated-industry buyers are not yet independently verified in the KG
• The canonical-profile governance question has a different answer for organizations mid-implementation than for greenfield evaluators — the article should distinguish whether the question is being asked before or during a deployment

Knowledge-graph nodes this draws from

• recommendation.salesforce-ecosystem-cdp-deepen-or-composable-augment
• archetype.salesforce-ecosystem-enterprise-evaluating-cdp
• vendor.salesforce-data-360
• vendor.hightouch
• org-dim.org-chart-type.matrixed-enterprise