
Short answer
Quick answer: pick by where your customer data should live. Warehouse-central teams: Hightouch or RudderStack. Event-collection-first: Segment. Mobile enterprise: mParticle. Want the pipe fused to a use case: Amplitude (analytics) or Bloomreach (commerce). Pricing shapes below as of September 2026 — verify live; this category reprices constantly.
A CDP does four jobs: collect events from your surfaces, resolve identity across devices and channels into one profile, compute traits and audiences, and sync those audiences to the tools that act (email, ads, engagement platforms). What it is not: an engagement tool, an analytics suite, or a substitute for deciding what your events mean — the schema-governance work stays yours forever, on every platform here. Our data-readiness checklist is effectively the list of what a CDP must feed downstream.
| Platform | Model | Best for | Pricing shape |
|---|---|---|---|
| Segment | Collect + store + sync | The mature default, deepest catalog | MTU-based, free tier then steep |
| RudderStack | Warehouse-native pipes | Engineering-led, warehouse-central | Event-based tiers + OSS core |
| mParticle | Enterprise mobile CDP | Mobile-heavy consumer brands | Quoted |
| Hightouch | Reverse ETL / composable | Warehouse IS the source of truth | Tiered by destinations/rows |
| Amplitude CDP | CDP fused with analytics | Teams already on Amplitude | Bundled tiers, quoted growth |
| Bloomreach | CDP + commerce engagement | Retail/e-commerce stacks | Quoted |
| Questera | Consumes the pipe | Acting on the profile, not storing it | Tiered by usage |
Segment is still the name the category means: the integration catalog nobody matches, Protocols for schema enforcement, and MTU pricing that turns painful exactly when you succeed. RudderStack rebuilt the idea warehouse-first with an open-source core — the engineering team's answer, priced on events rather than people, happiest where dbt is already a first-class citizen. mParticle is the mobile-consumer enterprise pick: SDK depth, identity across app ecosystems, procurement-grade everything.
Hightouch made the composable argument mainstream: your warehouse already stores the truth — sync audiences out of it instead of paying a second system to keep a copy. It's the right answer surprisingly often, and its limit is honest: no warehouse discipline, no composable CDP. Amplitude and Bloomreach sell the pipe fused to a destination — analytics and commerce engagement respectively — strongest when you wanted that destination anyway, weakest as neutral infrastructure.
Questera sits deliberately downstream: we consume identities and events from whichever pipe you choose — Segment, RudderStack, Hightouch syncs, or direct API — and run agent-driven lifecycle journeys on top. We're in this list as the reminder that a CDP is plumbing for activation: if the campaigns it should feed don't exist yet, six months of CDP procurement is six months of nothing reaching a customer. Same standard as always — run the whole stack through the evaluation brief, us included.
Ask each vendor: "Walk me through what happens when the same person shows up with three identifiers — anonymous web visitor, app login, and a support email — including the merge that turns out to be wrong." Identity resolution is the product; everything else is pipes and dashboards. Vendors differ enormously on merge rules, retroactivity, and — the part almost nobody demos — un-merging a bad join. Our identity merge decision log turns the answers into a comparable artifact across demos.
What is the best customer data platform?
Segment (default/catalog), RudderStack (warehouse-engineering), mParticle (mobile enterprise), Hightouch (composable/reverse ETL), Amplitude or Bloomreach (pipe fused to a use case). Decide where the truth lives first; the platform follows.
Do I need a CDP if I have a warehouse?
You need the jobs — identity, traits, audience sync. Whether they run composably on the warehouse or in a stored-copy CDP depends on your real-time needs and warehouse discipline.
How much does a CDP cost?
Free-to-hundreds monthly at entry, five-to-six figures at enterprise (September 2026; verify live). Budget the schema-governance engineering separately — every platform assumes it and none includes it.
See it in action

