Executive Summary
If your warehouse is already the single source of customer truth, a packaged CDP that copies it all into another silo is solving a problem you may have already solved — the real question is activation, not another data store.
Segment, mParticle, Treasure Data, ActionIQ, and the suite-native CDPs from Adobe and Salesforce promise unified customer profiles, audience segmentation, and real-time activation. But the ground is shifting toward warehouse-native and composable CDPs that build profiles and activate directly on the cloud data platform you already run — reframing the decision as buy a packaged CDP that ingests its own copy of the data versus assemble one on the warehouse that already serves as your single source of truth.
This guide provides a vendor-neutral evaluation framework for 10 leading platforms, weighing packaged versus warehouse-native and composable approaches, identity-resolution and data-quality depth, and activation across your marketing stack so you can unify and use customer data without building another disconnected silo.
Why Customer Data Platform (CDP) Matters for Enterprise Strategy
CDP selection increasingly hinges on architecture: a packaged platform that copies data into its own store can duplicate the warehouse you just made your source of truth, while a composable approach activates on that warehouse directly. Beneath that, the make-or-break capability is identity resolution — stitching fragmented identities into reliable profiles — and the consent and governance that keep activation compliant.
Warehouse-native and composable CDPs, zero-copy activation, and tighter ties between martech and the data platform are reshaping a category once defined by packaged data silos. Weigh how each option fits your existing data architecture and governs consent, because a CDP that fragments customer data away from your warehouse recreates exactly the silo problem it was bought to solve.
Architecture & Sourcing Decision
The CDP question is no longer build-vs-buy — almost nobody hand-rolls identity resolution and consent from scratch. It is where the profile lives: a packaged CDP that ingests and stores its own copy of customer data, or a composable, warehouse-native stack that defines profiles in the Snowflake, Databricks, or BigQuery platform you already run and activates them with reverse-ETL. The honest counterpoint to the composable pitch is that building reliable cross-channel identity in SQL or dbt is genuinely hard; teams that underestimate it often ship a worse identity graph than a packaged vendor would have handed them. Frame the decision around your data maturity, who owns the customer record, and how real-time your activation truly needs to be — not the connector count.
| Your Situation | Recommended Path | Rationale |
|---|---|---|
| Mature cloud warehouse already the source of truth, strong data team | Composable / warehouse-native (Hightouch, Census) | If the governed customer record already lives in Snowflake/Databricks/BigQuery, a packaged CDP just copies it into a second silo. Activate on the warehouse and keep one source of truth. |
| Marketing-led, thin data engineering, need value this quarter | Packaged CDP with built-in identity (Segment, Treasure Data, Tealium) | Composable assumes you can model identity and audiences yourself. A packaged platform ships identity resolution, a marketer UI, and connectors out of the box — faster time-to-activation without a data-team dependency. |
| Consumer brand with messy, multi-source identity (loyalty, POS, e-commerce, call center) | Identity-first packaged CDP (Amperity) | Probabilistic + deterministic stitching across dozens of fragmented sources is the whole problem here; a specialist identity engine usually beats both a generic CDP and a DIY graph. |
| Already standardized on Adobe or Salesforce for marketing/CRM | Suite-native CDP (Adobe Real-Time CDP, Salesforce Data Cloud) | Activation into Journey Optimizer/Target or Marketing Cloud is the payoff; zero-copy now lets these read warehouse data without full duplication, narrowing the classic silo objection. |
| Strict data residency / PII cannot leave your boundary | Warehouse-native or zero-copy activation | Keeping PII in your own warehouse and pushing only the minimum to destinations shrinks the compliance surface versus replicating full profiles into a vendor cloud. |
Key Capabilities & Evaluation Criteria
Weight these domains against your data architecture and activation use cases. For most enterprises, identity resolution and real-time activation now outrank the connector counts and dashboard polish that older RFPs over-index on — a CDP with 500 destinations and a weak identity graph still produces fragmented profiles and misfired campaigns.
| Capability Domain | Weight | What to Evaluate |
|---|---|---|
| Identity Resolution & Profile Quality | 25% | Deterministic and probabilistic matching across email, device, cookie, and offline keys; match accuracy on your real (messy) data; household/B2B account stitching; transparency and tunability of the match logic; how the golden record is survived and exposed |
| Data Architecture & Ownership | 20% | Packaged store vs. warehouse-native vs. zero-copy on Snowflake/Databricks/BigQuery; whether PII leaves your boundary; data duplication and reverse-ETL model; who holds the canonical profile; portability and lock-in if you leave |
| Real-Time Activation & Audiences | 20% | Streaming vs. batch profile updates and in-session segmentation; audience builder usability for marketers; breadth and freshness of destination connectors (ad platforms, ESP/MAP, ad-tech, support); reverse-ETL sync latency and reliability |
| Consent, Privacy & Governance | 15% | Consent capture and enforcement at the point of activation; CMP/OneTrust integration; data-subject access and deletion propagation to destinations; PII tagging and field-level governance; regional residency controls |
| Data Collection & Quality | 10% | First-party event collection SDKs (web, mobile, server); schema validation and data-contract enforcement before bad data lands; warehouse and batch ingestion; tracking-plan governance to keep the profile foundation clean |
| Predictive & Generative AI | 10% | Built-in propensity/churn/LTV models; natural-language and agentic audience building; next-best-action and decisioning; whether models run on the warehouse or require export; explainability of AI-generated segments |
Vendor Landscape
The market splits along architecture, not just brand. Suite-native CDPs (Adobe, Salesforce) fold customer data into a broader experience or CRM cloud and win on activation into their own channels. Independent packaged CDPs (Segment, Treasure Data, Tealium) ship identity resolution, collection, and connectors as a standalone platform. A consumer-identity specialist camp (Amperity) treats stitching messy offline-plus-online data as the core problem. And composable, warehouse-native challengers (Hightouch, Census) flip the model entirely — they activate on the Snowflake/Databricks/BigQuery warehouse you already own rather than copying data into their own store. Most shortlists now compare across these camps. Consolidation has thinned the field: mParticle merged into Rokt (announced January 2025, ~$300M), ActionIQ was acquired by Uniphore (December 2024) and folded into its “CDP Agent,” Lytics went to Contentstack, and Census is now part of Fivetran (agreement announced May 2025) — so verify the current owner and roadmap of any vendor on your list.
Strengths: The de facto standard for first-party event collection, with mature web/mobile/server SDKs, a single tracking API, and broad destination coverage (550+) via Connections. Protocols enforces schema and data-contract quality at the source; Unify and Engage add identity and audiences; Generative Audiences (GA in 2025) brings natural-language segment building. Twilio kept Segment after 2024 activist pressure to divest and now runs it in a growth-focused Data & Applications unit. Considerations: MTU-based pricing (every unique user, anonymous visitors included) can escalate fast on high-traffic sites; identity and analytics depth trail dedicated identity engines; the marketer-facing audience UX is lighter than suite CDPs; the post-activist strategic direction is healthier but still worth tracking on renewal.
Strengths: Enterprise CDP on Adobe Experience Platform with distinct B2C, B2B, and B2P editions, strong governance and consent tooling, and real-time edge segmentation that activates straight into Journey Optimizer, Target, and Analytics. Federated Audience Composition and zero-copy patterns let it read warehouse data without always duplicating full profiles. Considerations: Premium, profile-/addressable-audience-based pricing; value is highest when you live in Experience Cloud and thinner outside it; AEP’s data model and implementation carry real complexity and usually need specialist help or an SI.
Strengths: Deep native harmonization with Sales, Service, Marketing, and Commerce Clouds, a unified profile feeding Einstein and Agentforce, and a zero-copy story with Snowflake, Databricks, and BigQuery so warehouse data can be queried without bulk replication. Rebranded to Data 360 at Dreamforce 2025 as the data layer powering Salesforce’s AI agents. Considerations: Value concentrates inside the Salesforce ecosystem; consumption/credit and per-profile economics can climb quickly; the data model and frequent renaming (Audiences → CDP → Genie → Data Cloud → Data 360) add a learning and change-management tax; it is younger than incumbents at pure-play CDP depth.
Strengths: Vendor-neutral, scale-oriented enterprise CDP with strong ingestion of high-volume and offline data, solid identity resolution, predictive scoring, and journey orchestration. Independence from any martech or CRM suite is a genuine differentiator for buyers wary of lock-in; spun out of SoftBank/Arm as a standalone company. Considerations: Less brand pull in mid-market than Segment; activation ecosystem is broad but not as developer-magnetic; like all packaged CDPs it maintains its own profile store, so weigh it against composable options if your warehouse is already canonical.
Strengths: The Customer Data Hub pairs deep tag-management and server-side collection heritage (iQ, EventStream) with AudienceStream for real-time identity stitching and in-session activation, plus 1,300+ connectors. Strongly vendor-neutral, privacy-forward, and well regarded for getting clean, consented data flowing across a heterogeneous stack. Considerations: Predictive/AI and built-in analytics are lighter than Adobe or Salesforce; advanced identity and audience work can lean on professional services; positioning sits between a data-collection layer and a full activation CDP, so scope which job you’re buying it for.
Strengths: Identity resolution is the product: patented probabilistic-plus-deterministic stitching that unifies loyalty, POS, e-commerce, mobile, and call-center data without forcing pre-defined match keys, and increasingly AI-assisted (Identity Resolution Agent, Chuck Data). Recognized as a leader in IDC’s 2025 retail CDP MarketScape and adopted by large consumer brands. Considerations: Purpose-built for B2C/retail/hospitality — a weaker fit for B2B account-based models; an enterprise-tier investment; it is an identity-and-data foundation more than a campaign-execution tool, so it pairs with downstream ESP/MAP and decisioning rather than replacing them.
Strengths: The reference composable, warehouse-native CDP: activates directly from Snowflake, Databricks, BigQuery, and Redshift with no separate data store, combining reverse-ETL to 200+ destinations, a marketer-friendly audience builder (Customer Studio), warehouse-side identity resolution, and AI Decisioning. Keeps the warehouse as the single source of truth and avoids a second profile silo. Considerations: Assumes a reasonably mature cloud warehouse and a data team to model it; identity resolution built in SQL/dbt is powerful but more your responsibility than a packaged engine; rapid repositioning (reverse-ETL → composable CDP → agentic) means tracking which capabilities are GA today.
Strengths: Pioneer of reverse-ETL and operational analytics: syncs governed warehouse data back into 200+ business and marketing tools, keeps data in the customer’s warehouse by default, and offers strong observability and data-contract features. Now part of Fivetran (agreement announced May 2025), giving a single vendor both ingestion into the warehouse and activation back out of it. Considerations: More an activation/data-movement layer than a full marketer-facing CDP — audience management and built-in identity are lighter than Hightouch or packaged CDPs; post-acquisition product integration with Fivetran is still settling; best value assumes the warehouse is already your customer source of truth.
Pricing Models & Cost Structure
CDP pricing is almost always subscription, but the unit of measure differs sharply — monthly tracked users, addressable profiles, consumption credits, ingested volume, or destination/seat count — and that unit, far more than the headline rate, decides what you pay as you grow. The architectural twist: packaged CDPs charge you to store and process a second copy of your data, while composable, warehouse-native tools price the activation layer and leave the (already-budgeted) compute and storage in your own warehouse. Model cost against your real profile counts, event volume, and traffic curve, and watch for the silent escalators — anonymous MTUs, profile growth, and premium AI/identity add-ons.
| Vendor | Pricing Model | Relative Tier | Key Cost Drivers |
|---|---|---|---|
| Segment (Twilio) | Per monthly tracked user (MTU); volume tiers | Moderate–Premium | MTU count incl. anonymous visitors, edition (Connections vs. CDP), Protocols/Unify/Engage add-ons, throughput/API volume |
| Adobe Real-Time CDP | Per addressable profile; B2C/B2B/B2P editions | Premium | Addressable audience size, edition, sandboxes, activation/destination scope, professional services and SI implementation |
| Salesforce Data Cloud (Data 360) | Consumption credits + per-profile | Premium | Credits for ingestion/processing/queries, profile volume, Einstein/Agentforce usage, dependence on existing Salesforce footprint |
| Treasure Data | Platform subscription by profiles/volume | Moderate–Premium | Unified profile count, ingested data volume, retention, predictive/AI modules, professional services |
| Tealium | Subscription by events/profiles | Moderate | Event/visitor volume, connector usage, EventStream vs. AudienceStream scope, predictive add-ons |
| Amperity | Enterprise subscription by records/profiles | Premium | Source record volume, number of unified profiles, identity-resolution scope, AI features, implementation |
| Hightouch | Subscription by destinations/seats (warehouse-native) | Lower–Moderate | Number of destinations and syncs, Customer Studio/identity/AI Decisioning tiers, seats — warehouse compute billed separately by your cloud |
| Census (Fivetran) | Subscription by destinations/fields; Fivetran bundle | Lower–Moderate | Active destinations and synced fields/rows, observability tier, packaging within Fivetran — warehouse compute billed by your cloud |
Implementation & Migration
Sequence the rollout by use case and identity confidence, not by how many sources you can connect. Land one high-value activation against a trustworthy profile before you scale breadth — a CDP that activates the wrong identities at scale is worse than no CDP.
Inventory customer data sources and the identifiers each carries, define the tracking plan and event schema, and stand up consent capture so governance is wired in before data flows — not retrofitted later. Decide explicitly whether the canonical profile lives in a packaged store, the warehouse, or zero-copy across both.
Configure and tune deterministic and probabilistic matching, validate golden records against a hand-labeled sample for false merges and missed matches, and codify the survivorship rules for the unified profile. This is the make-or-break phase; do not rush past it to chase a launch date.
Wire the priority destinations (ad platforms, ESP/MAP, support, analytics), build the first audiences with marketing, and run real campaigns or suppression lists end to end. Confirm consent is enforced at the point of activation and that sync latency meets the use case (real-time vs. batch).
Onboard remaining sources and destinations, layer in predictive/AI segments where they earn their keep, establish data-quality monitoring and deletion propagation, and review cost against the model — especially MTU/profile growth and warehouse compute — tuning before the next renewal.
Selection Checklist & RFP Questions
Use this checklist during evaluation to verify the things that actually decide whether a CDP unifies your customer data or quietly fragments it.