- If your customer data already sits in a warehouse
- Keeping customer records inside your own walls
- One small team running data and campaigns
- When paid media is where the CDP earns its keep
- Personalising the website comes first
- Nine platforms to put on a Zeotap shortlist
- What decides the bill
- A one-hour test with your own records
- Who should pick which type
A warehouse-native or composable CDP is the closest swap for Zeotap when your data team owns a warehouse; a private-cloud CDP fits strict hosting rules, and a CDP bundled with marketing automation suits a small team that runs everything itself.
Zeotap now sells two things under one name: a packaged, AI-powered CDP and a composable version that runs as a Snowflake Native App. It markets itself on privacy and keeps industry pages for retail, telecoms, media and sport. So a team with a data warehouse and a team with three marketers and no engineers can both end up there, and they'll want very different replacements.
Start with the situation that sounds like yours, note the type of tool it points to, and you'll know which names below deserve a demo. If you're still deciding whether you need a CDP at all, start with my wider guide to customer data platforms.
If your customer data already sits in a warehouse
Then I'd start with a composable or warehouse-native CDP. This type of tool works on the warehouse you already run and builds unified customer profiles there. Zeotap's own move to a Snowflake Native App shows how far this has come: building on the warehouse is now a mainstream CDP choice, not an engineer's side project.
The question inside this group is who'll drive it day to day: marketers or your data team. Ask each vendor to show the exact screen that person would use, not the one the sales engineer prefers. If marketers will live in it, check they can build a segment without writing SQL, because that's where these projects stall. If Segment is also on your shortlist, here's my list of Segment alternatives.
One caution. Composable only saves time if the warehouse is already in order. If customer tables are scattered across schemas nobody has documented, you'll spend the first months modelling data, not marketing with it.
Keeping customer records inside your own walls
Zeotap markets itself on privacy, so if that was part of why you chose it, don't accept a step down. There are two ways to keep that posture. The first is a CDP you deploy on-premise or in a private cloud, so profiles stay on infrastructure you control. The second is a privacy-first hosted platform that puts consent management and tag management in the same product as analytics and data activation.
Ask both kinds the same questions, in writing. Where exactly are profiles stored? Who at the vendor can see them? How is a deletion request carried out, and does it reach every destination the data was sent to? Is consent stored per profile and checked on every outbound sync? A vendor that answers all four clearly, without needing another call, is one I'd take seriously.
One small team running data and campaigns
A separate CDP, email tool and analytics product make sense when each has an owner. When three people do everything, the joins between tools become the job. Here I'd look at a hosted product that puts customer data, marketing automation and analytics in one place. You may give up some depth in each part. You'd gain one login, one contract and fewer joins to look after.
The question to press is how deep the data side goes. Ask to see an anonymous website visitor merged into a known contact after they sign up, and ask how custom events from your app or shop get in. If the answer is a spreadsheet upload, you're looking at a marketing tool with a contact list, and that may still be fine, as long as you know it.
When paid media is where the CDP earns its keep
Sometimes the whole business case for a CDP was ad performance: better audiences, fewer wasted impressions, cleaner conversion data. If that's you, a first-party data platform built for advertisers may be all you need. This type of tool sets out to fix tracking gaps, resolve identity across your site, CRM and offline sales, and send cleaner signals back to the ad platforms.
Ask what it covers beyond the ads: on-site personalisation, email orchestration and a single profile for your service team. If nobody inside the business is asking for those, don't pay for them.
Personalising the website comes first
Some retailers and publishers come to a CDP to change what visitors see: product recommendations, search results, content for returning readers. Then look at a personalisation platform that covers customer data, search and marketing automation together. Before you commit, ask how long a typical set-up takes, who does the work, and how many people you'll need to run it afterwards.
There's a middle route too: a hosted CDP built around a real-time profile, feeding the personalisation tools you already own. That's worth weighing if your site stack is settled and you only need the profile to be fresher.
Nine platforms to put on a Zeotap shortlist
Meiro
For organisations that want the CDP inside their own walls, it runs on-premise or in a private cloud, with event routing, reverse ETL and identity resolution.
Piwik PRO
A privacy-first analytics suite that bundles a tag manager and consent manager with data activation, so measurement and audiences live side by side.
CustomerLabs
Built around first-party data for advertisers: it resolves identity and passes cleaner signals back to the ad platforms you already spend with.
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.
Mapp
Marketing teams wanting data unification, analytics and automation from a single supplier will find Mapp pitches exactly that kind of customer experience platform.
Ortto
Customer data, marketing automation and analytics share one product here, which suits a lean team that would rather not stitch three tools together.
BlueConic
A hosted customer data platform whose pitch is the real-time profile, built so it feeds every decision and activation automatically.
Hightouch
Sold to marketers as a customer data and AI platform: a composable CDP on your warehouse, offered alongside AI agents and campaign tools.
RudderStack
This warehouse-native CDP collects event data and builds unified customer profiles inside your own warehouse rather than a separate store.
Bloomreach
When on-site search and personalisation matter as much as the customer data, this platform puts both alongside marketing automation.
What decides the bill
CDP vendors don't charge in one consistent way, so compare the billing unit before you compare any figure. Four units turn up on this shortlist.
- Per event: you pay for the volume of event data you send through each month. RudderStack works this way and shows a free tier on its pricing page.
- Per tier: privacy-first analytics suites sell plans in tiers, so check which tier your traffic and the features you need would put you in.
- Plan plus usage: first-party ad data platforms pair a plan with usage units on top, so ask what counts as a unit.
- Quote only: where a pricing page shows no figure, you'll get a quote after a demo, so ask what it's built on: profiles, data volume, channels, brands or regions.
What makes the bill climb is the same across all four: more events, more profiles, more destinations and more brands or regions. Two costs sit outside the contract. If you go composable, ask your data team what extra warehouse use the audience syncs will create. And every part of a bundle you don't take means another product to buy, connect and maintain. Put both in the comparison before you call one option cheaper.
The category is also consolidating, with CDP vendors buying and being bought. That's worth a line in your due diligence: ask any vendor what happens to your contract, your data and the roadmap if ownership changes.
Do you make customer data platforms or first-party data tools? Tool makers can ask to be considered for a featured place on this list.
A one-hour test with your own records
Every demo runs on tidy sample data. Yours won't be tidy, so ask for a trial or sandbox and try this before anything is signed:
- Load a small export of real customers that you know contains duplicates, such as one person under a work and a personal email.
- Count how many of those the tool merges correctly, and check you can see why each merge happened.
- Have a marketer build one audience they'd want next week, with no engineer helping, and time it.
- Send that audience to one ad platform or email tool and compare the count that arrives with the count that left.
- Delete one test person and confirm they disappear everywhere, destinations included.
If a tool fails the merge step or the deletion step, the rest of the demo doesn't matter.
Who should pick which type
With a warehouse and a data team, start with a composable or warehouse-native CDP. With strict hosting rules, a private-cloud CDP or a privacy-first suite. With a small team doing everything, a CDP bundled with automation. For ad performance alone, a first-party data platform. For on-site revenue, a personalisation platform.
Before you give notice, ask Zeotap how to export your profiles, audience definitions and consent records, and check the files open cleanly on your side. Then write down the Zeotap features your team used in the last few months and ignore the rest. That list, not anyone's brochure, is your real brief. If mParticle is also on your radar, here's my list of mParticle alternatives.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


