Zeotap, the customer data platform vendor, has launched its Composable CDP as a Native App on Snowflake Marketplace, according to a GlobeNewswire announcement.

The release extends Zeotap's CDP into Snowflake's data cloud, where the app runs natively against customer tables rather than as a separate SaaS tool that copies data in and out of a vendor environment.

What is a Composable CDP?

A composable CDP executes identity resolution, segmentation, audience building, and activation inside a customer's own data warehouse. Data stays in place; the CDP software runs against it. This contrasts with traditional CDPs, which store customer profiles on vendor infrastructure and require ETL to share data with the warehouse.

Zeotap describes the offering as "end-to-end," signalling coverage from ingestion through channel activation rather than a single capability such as identity or enrichment.

What does "Native App" change for Snowflake customers?

The Native App designation on Snowflake Marketplace means the application uses Snowflake's framework to run inside a customer's account. Practitioners evaluating the app should look at three practical effects:

• Data stays in Snowflake. Audience and identity work happens against customer tables, which removes copy jobs and reverse ETL for many use cases.
• Marketplace procurement. Snowflake handles billing and contract terms through its Marketplace, so adoption can run on existing Snowflake credits.
• Native permissions. The app reads and writes within the customer's Snowflake account using native role-based controls.

What about pricing and integration details?

The GlobeNewswire release confirms availability on Snowflake Marketplace but does not disclose per-row or per-seat pricing, contract minimums, or the full list of supported Snowflake regions. Practitioners should request those specifics from Zeotap or their Snowflake account team before budgeting.

Why does the launch matter for the CDP market?

The move places Zeotap in a growing category of warehouse-native composable CDPs. By packaging the CDP as a Marketplace app, Zeotap reduces the integration overhead that has slowed traditional CDP deployments, where separate vendor environments often duplicate data the warehouse already holds.

For Snowflake customers, the immediate decision is whether to consolidate CDP functions inside their data cloud or continue with a separate CDP vendor that exports to Snowflake. The trade-off typically comes down to where identity resolution runs, which activation channels the app supports, and the total cost across Snowflake consumption and any separate CDP contract.

What should a buyer test?

Teams running a proof-of-concept should verify:

• Identity graph performance against Snowflake tables at production scale
• Coverage of paid media, email, and CRM activation endpoints
• Latency for audience refresh inside the warehouse
• Cost in Snowflake credits versus prior CDP spend

Where does this leave the CDP shortlist?

The launch adds Snowflake-native composable CDPs as a category to compare against warehouse-native offerings such as Hightouch and Census, plus standalone CDPs like Twilio Segment, mParticle, and Adobe Real-Time CDP. Buyers should weigh where identity resolution runs, whether audience outputs stay in Snowflake or get pushed to ad platforms, and the cost model between marketplace credits and traditional CDP contracts.

The Zeotap Composable CDP Native App is listed on Snowflake Marketplace and available to Snowflake customers in supported regions at launch.