The Zeotap Composable CDP is now live as a Snowflake Native App and available on Snowflake marketplace for easy installation. You can find it on the Snowflake Marketplace, install it into your own Snowflake account, and have a working customer data platform sitting next to your data before your next architecture review meeting would have finished.
We want to be precise about what “native” means here, because the word has been doing a lot of unpaid overtime in this industry.
The problem with how CDPs are built
Every CDP has the same awkward opening line: “First, send us your customer data.”
Traditional CDPs copy your data into their cloud and keep it there. You pay to store it twice, you sync it forever, and your security team gets a new vendor to worry about. Composable CDPs improved on this. They query your warehouse instead of copying it. But the application itself, the part that resolves identities, builds audiences, and pushes them to Meta and Braze, still runs on the vendor’s servers. You allowlist their IPs. Their control plane sees your query patterns, your metadata, your audience definitions. The query moved into your warehouse, but the brain did not.
For a retailer running campaigns, this is a tolerable inconvenience. For a bank, an insurer, or a telco, it is six months of vendor risk assessment, data processing agreements, and a residency question that never gets a clean answer.
We kept meeting the same enterprise buyer. They had already bet on Snowflake. Their customer data was there, governed, access-controlled, in the region their regulator cares about. And every CDP conversation started by asking them to punch a hole in that.
What we built instead
The Zeotap Composable CDP runs entirely inside your Snowflake account. Not a connector to it. Not a feature of it. The full platform: agentic AI, identity resolution, profile unification, segmentation, journey orchestration and activation to downstream destinations.
This is possible because of Snowpark Container Services, Snowflake’s infrastructure for running containerised applications inside a customer’s account. Most vendors use the Native App framework to ship a single feature into your account while the product stays home. We used it to ship the product.
The difference in one picture. Everything above the vendor-cloud box on the left is what your security team objects to.
What it looks like to use
No re-platforming project. No six-month implementation. From the user’s side, it goes like this:
- Install from the Marketplace. The Zeotap Composable CDP installs into your Snowflake account like an app onto a phone. Your Snowflake admin approves it. That approval is the deployment.
- Point it at your tables. You grant the app read access to the customer tables you choose, and only those. Snowflake’s own permission model enforces it. There is no separate credential store to audit.
- Unify your customers. The app resolves identities across your tables and builds unified profiles, in place. Nothing is extracted to be stitched somewhere else and sent back.
- Build audiences and journeys. Marketers work in a normal point-and-click interface. Segments, computed traits, journey logic. No SQL required, though your data team can look under the hood any time, because the hood is in their account.
- Activate. Audiences sync from your account to your marketing and advertising destinations. The first external hop your data takes is the one you actually wanted: to the channel.
Your data engineers see a Snowflake app consuming Snowflake compute, visible in the same cost dashboards and query history they already watch. Your marketers see a CDP. Your CISO sees one line item that got shorter.
Why this is different, concretely
There are other CDP names on the Snowflake Marketplace, and some of the apps are genuinely useful. But look at what each one actually ships into your account. In every case we studied, it is one feature: an audience builder here, an AI layer there, a federated query connector somewhere else. The platform, the part that holds your profiles and runs your journeys, stays in the vendor’s cloud. The native app is a doorway to it.
The Zeotap Composable CDP is the only complete CDP that runs inside your Snowflake account. Others ship a feature. We ship the product.
That single architectural fact does a surprising amount of work:
Security review shrinks. There is no new place your customer data lives. The vendor assessment stops being about data transfer and starts being about an app running under Snowflake’s sandbox, with permissions you granted and can revoke.
Residency answers itself. Your Snowflake account is in a region. The app runs in that account. If your regulator asks where processing happens, the answer is the same answer you already gave for the warehouse.
Governance is inherited, not rebuilt. Row access policies, masking, RBAC: whatever you have configured in Snowflake applies to the Zeotap Composable CDP, because it is a tenant of your account, not a guest with a copy of the keys.
No sync tax. There is no pipeline keeping a second copy of your customers fresh in someone else’s cloud, and no bill for it.
One honest note, because we would rather you hear it from us: the app runs on your Snowflake compute, so the processing cost shows up on your Snowflake bill rather than hidden inside a SaaS subscription. We think that is a feature. You can see it, size it, and govern it with the resource monitors you already use. But it is a different shape of bill, and your finance team should know that going in.
Who this is for
If you are a Snowflake customer in a regulated industry, this was built for you specifically. Banking, insurance, telecom, healthcare: anywhere the sentence “the vendor never receives your customer data” changes the length of a procurement cycle from quarters to days.
If you are not in a regulated industry, the pitch is simpler. You already paid to get your data into Snowflake, modelled and governed. A CDP should meet it there instead of asking for a copy.
The Zeotap Composable CDP is available now on the Snowflake Marketplace. If you want a walkthrough with your own data, in your own account, talk to us. The demo environment is your environment. That is rather the point.
