Customer data glossary
Composable customer data platform (CDP)
By Art Kukharenko · Published · Updated
Browse learn glossary resourcesA composable customer data platform (CDP) builds CDP capabilities from separate components, usually a cloud data warehouse as the store plus tools for collection, identity, modelling and activation.
Part of the Learn hub and the customer data glossary.
What it means in practice
The idea is to treat the customer data platform as an architecture rather than a product. The warehouse (Snowflake, BigQuery, Databricks or similar) is the store, and separate tools handle event collection, identity resolution, modelling and reverse ETL. The best-known composable vendors, Hightouch and Census, started in reverse ETL, and Gartner's 2026 Magic Quadrant for CDPs lists Hightouch among its Leaders (as reported by CX Today, January to February 2026).
The advantages: data stays in one governed place, there is no second copy in a vendor's store, and teams reuse the warehouse's existing security and lineage tooling. The disadvantages: assembly and integration work, identity resolution, consent and suppression that you must build as warehouse logic, limits on real-time use, and warehouse compute costs that grow with refresh frequency.
Composable does not mean self-hosted or private. If the warehouse is a SaaS service, customer data sits with that provider, and each extra tool is another processor to assess. A composable design runs on-premise only if the warehouse and every component can.
Example (retail banking): a bank whose risk team has already approved its governed warehouse chooses a composable design to avoid copying customer data to a second platform. Consent and suppression become tested SQL models, and each sync to a destination passes through an approved field list.
Related terms
- Warehouse-native customer data platform (CDP): the single-vendor variant.
- Packaged customer data platform (CDP): the all-in-one alternative.
- Reverse ETL: its activation layer.
- Self-hosted customer data platform (CDP): a different axis, about where it runs.
- Identity resolution: the part you must supply.
Where it matters
- Composable vs packaged vs private customer data platforms: an honest comparison.
- Customer data platform on AWS, Azure and GCP: reference architectures.
Frequently asked questions
What is the difference between composable and warehouse-native?
They overlap. Composable stresses assembling separate tools around a warehouse; warehouse-native stresses one platform running directly on the warehouse without copying data. Vendors use both labels loosely.
Is a composable CDP cheaper?
Not inherently. It moves cost from the vendor's meter to warehouse compute, engineering time and several tool subscriptions. Model all of them over three years.
Can a composable CDP run on-premise?
Only if the warehouse and each tool can. Many components are SaaS-only, so check every one against your residency and ownership requirements.
Back to the customer data glossary or the Learn hub.
Further reading
- Customer Data Glossary: 50 Terms
- CDP on AWS, Azure and GCP
- Learn about CDP
- Composable vs Packaged vs Private CDP
- Identity resolution — definition
Published: · Updated:
Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.