Start by deciding where your customer data should live. If you want a ready-made platform that holds and activates data for marketers, a packaged CDP fits. If your data already sits in a warehouse, a composable or warehouse-native tool fits better. If personalisation is the main goal, look at a suite built around it.
Customer data platforms used to be one product category. Today they split three ways: packaged platforms that hold your data for you, warehouse-native tools that work on data you already store, and personalisation suites where the data serves the experience. If you're moving away from Treasure Data, knowing which of the three you want will cut a long shortlist down fast.
Here are eight options for marketing and data teams that unify customer data, in no particular order, with the questions that separate them.
Where will your customer data live?
Treasure Data now presents itself as Treasure AI, which its homepage calls an agentic experience platform for winning, keeping and growing customers. That's a broad promise, and most vendors here make one like it. Under the wording, the decisions that matter are more practical.
The first is where the data lives. Some platforms copy it into their own store, others leave it in your warehouse and work on it there. The second is how it reaches your marketing tools: through ready-made connectors, through syncs your team defines, or through the vendor's own channels. The third, and the one teams forget, is who keeps those connections working when a field changes or a tool is swapped out.
Tools in this category split by who they're built for and how much you set up yourself. A packaged platform does more on day one, and a warehouse-native tool gives your data team more control. Run the same real task, such as building one audience and sending it to one channel, through each before you decide.
Packaged, warehouse-native or personalisation-led
Packaged platforms for marketers
mParticle, Tealium, Blueconic, Amperity and Lytics each offer a platform that collects or unifies customer data and makes it usable for marketing. They differ in emphasis: identity resolution, real-time segmentation, data control or marketer self-service.
Warehouse-native and composable
Hightouch and RudderStack work with a data warehouse you already run. They suit teams with data engineers who want one source of truth and don't want a second copy of every record.
Personalisation first
Bloomreach starts from the customer experience, personalising email, web, mobile and search, with the data platform underneath. It's for commerce teams where the main goal is what the shopper sees next.
The eight platforms, A to Z
Alphabetical and in no particular order. Each description reflects what the vendor says about its own platform.
Amperity
Best for: Enterprise brands with messy, duplicated customer records, which the vendor says it resolves into one trusted view for acting in real time.
Bloomreach
Best for: Commerce marketers who want personalisation across email, web, mobile and search, driven by the vendor's own AI, which it calls Loomi.
Blueconic
Best for: Marketing teams who want to unify customer data and act on it themselves, in a platform the vendor says is also trusted by IT.
Hightouch
Best for: Data-savvy marketing teams who'd rather build on their existing data warehouse; the vendor describes a composable CDP with AI marketing agents on top.
Lytics
Best for: Content and marketing teams wanting first-party data unified and segmented for real-time use; the product now sits within Contentstack, per its own site.
mParticle
Best for: Product and growth teams who want customer data turned into audiences and actions, which the vendor frames as a performance CDP.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
RudderStack
Best for: Engineering-led teams who want to collect, unify and govern customer data from a warehouse-native platform; the vendor names a free plan.
Tealium
Best for: Large organisations that need customer data integration, management and orchestration, with the vendor stressing control over where data sits.
How the eight line up
| Tool | Model | Good for |
|---|---|---|
| Amperity | Identity-led CDP | Resolving messy records into one view of each customer |
| Bloomreach | Personalisation platform | Personalising email, web, mobile and search together |
| Blueconic | Marketer-led CDP | Marketers unifying and activating data with IT on board |
| Hightouch | Composable CDP | Marketing on top of the data warehouse you already run |
| Lytics | Real-time data and insights | Segmenting first-party data for real-time activation |
| mParticle | Performance CDP | Turning customer data into audiences and actions |
| RudderStack | Warehouse-native CDP | Collecting and governing data inside your own warehouse |
| Tealium | Customer data infrastructure | Data collection, integration and orchestration at scale |
Advice for data and marketing teams choosing a CDP
Put marketing and data people in the same room before any demo. Marketers will judge a CDP on how fast they can build an audience, and engineers will judge it on where data is copied and how it's governed. If only one side picks, the other side ends up working around the tool.
Ask every vendor to build one real audience from your own data and send it to one real channel during the trial. That single task shows you the connectors, the identity matching and the effort involved. For a wider comparison, see my guide to the best customer data platforms, and if your data already lives in a warehouse, read my round-up of the best reverse ETL tools too.
Rules on collecting and using personal data vary by country, so check with your regulator or a privacy adviser before you move customer records between systems.
Who maintains the pipes after launch
The launch is the easy part. Six months in, someone renames a field, a new email tool arrives, or a consent setting changes, and the connections need updating. Decide now whether that someone is a marketer with a point-and-click screen, a data engineer with code, or the vendor's own services team. The answer should shape your shortlist as much as any feature does.
If nobody on your team will own that job, lean towards a platform that does more for you. If you've got data engineers who'd rather keep control, a warehouse-native tool will suit them better. Either way, write the owner's name down before you sign.
Do you make customer data platforms? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What's the difference between a packaged CDP and a composable CDP?
A packaged CDP stores customer data in its own system and gives marketers tools on top. A composable CDP works on data already in your warehouse, so it relies more on your data team.
Do small businesses need a customer data platform?
Often not. If your customer data sits in one CRM and one email tool, those may be enough. A CDP earns its place when data is scattered across many systems.
How long does it take to switch CDPs?
It depends on how many sources and destinations you connect. Start with one audience and one channel, then add connections in stages rather than moving everything at once.
Is a CDP the same as a data warehouse?
No. A warehouse stores data for analysis, while a CDP focuses on unifying customer records and sending them to marketing tools. Some tools now work on top of a warehouse.
Who should own a customer data platform?
Usually marketing and data share it. Marketing owns audiences and campaigns, and the data team owns sources, identity rules and governance.
