Archetype — Salesforce Ecosystem Enterprise Evaluating CDP

Organizational profile

Enterprise (typically >$500M revenue, >100K customer profiles) with Salesforce CRM as the primary CRM layer and Salesforce Data 360 as the incumbent or planned CDP layer. Marketing Cloud Next (GA June 2025) consolidates nine previous Salesforce marketing acquisitions onto Data 360, meaning the full Salesforce marketing stack is: Salesforce CRM → Salesforce Data 360 (identity, segmentation, profile) → Marketing Cloud Next (campaign execution, Agentforce AI orchestration).

IT and Marketing have separate Responsible roles; the Accountable is typically a VP Marketing Operations, Salesforce platform owner, or CDO who made the original Salesforce CRM investment and is evaluating whether to deepen it (add Data 360 and Marketing Cloud Next) or augment it with a composable layer.

A cloud data warehouse (often Snowflake or Databricks, or BigQuery in Google-ecosystem organizations) may already exist, driven by finance, analytics, or data science teams — not marketing. The evaluation trigger is usually whether Data 360 can consume CDW data effectively, or whether the composable path (CDW + Hightouch or Fivetran Activations) is architecturally cleaner.

Market context (as of 2026). Salesforce Data 360 is the sole top Leader in the Gartner CDP Magic Quadrant 2026, the only CDP vendor placed in the upper-right of the Leaders quadrant (MarTech Square, February 2026 independent analysis). The Gartner MQ 2026 language shift — "Decisioning" 35× and "Orchestration" 39× — aligns directly with Data 360's Agentforce positioning and Marketing Cloud Next's orchestration layer. Organizations in this archetype are evaluating at the peak of Salesforce's CDP market positioning; the evaluation question is whether the Data 360 + MCN stack delivers on that positioning within their specific CDW and channel constraints.

Trigger pattern

The evaluation is usually precipitated by one or more of:

• Marketing Cloud Next consolidation: The June 2025 unification of nine Salesforce marketing acquisitions onto Data 360 makes the Salesforce-native stack architecturally coherent for the first time. Organizations that had deferred CDP decisions pending this clarification now have a concrete question: is the unified stack sufficient?
• An existing CDW (Snowflake, Databricks, BigQuery) holding customer data that Data 360 cannot ingest without custom connectors — creating a two-source-of-truth problem.
• ML propensity models or AI scoring that the data science team insists must remain in the CDW but marketing needs for activation.
• Salesforce Data 360 activation limits that surface at scale, analogous to AEP activation ceilings (audience export limits, connector restrictions).
• A desire to activate through channels not natively supported by Marketing Cloud Next (The Trade Desk, non-Meta/Google ad platforms, niche email providers) requiring a composable reverse-ETL layer.

Common presenting symptoms

• "We're going all-in on Salesforce — but our data science team says their models have to stay in Snowflake. How do we connect them?"
• "We just renewed our Salesforce contract. Data 360 is supposed to solve our CDP problem, but we also have BigQuery. Do we still need it?"
• "Marketing Cloud Next looks compelling, but we need to activate to The Trade Desk and Criteo — not just email and SMS."

Recommended direction

concept.composable-cdp: assess whether the CDW already in use can serve as the canonical customer data layer with a composable activation tool (Hightouch or Fivetran Activations) routing segments downstream to both Marketing Cloud Next and other destinations. Data 360 can remain as the Salesforce-ecosystem profile and segmentation layer for Salesforce-native activations; the CDW handles the rest.

The evaluation question is not "Salesforce vs. composable" — it is "where does the canonical profile live and which activation paths need to be served?" Both Data 360 and a CDW-native layer can coexist; the architectural question is governance.

Key tradeoffs

• tradeoff.integration-philosophy: Deep Salesforce integration (Data 360 → Marketing Cloud Next) is turnkey for Salesforce-native campaigns. Composable augmentation (CDW → Hightouch or Fivetran Activations → Marketing Cloud Next + other channels) adds a reverse-ETL operational layer but gains multi-destination flexibility.
• tradeoff.center-of-gravity: If the CDW becomes the canonical profile store, Data 360 becomes a downstream consumer of CDW-assembled audiences — flipping the intended relationship. This is a governance and ownership question that requires alignment between IT, Marketing, and Analytics before an architecture is chosen.
• tradeoff.cost-predictability: Data 360 is seat/record-based pricing; CDW + composable tools are consumption-based. At high segment volumes and frequent refreshes, the cost model comparison is non-trivial.
• tradeoff.data-egress: A composable layer that routes CDW audiences back into Data 360 (for Marketing Cloud Next execution) creates a data-flow loop with potential egress costs across CDW provider boundaries.