Build vs Buy: Identity Resolution on Snowflake vs a Packaged CDP

Every December, Scott Brinker and Frans Riemersma publish a deeply researched annual report on the state of marketing technology. Their December 2025 edition, Martech for 2026, surveyed over 100 marketing ops and martech leaders to understand where the industry actually stands. The headline finding is familiar to anyone who has lived through a CDP implementation: integration remained a Top 3 challenge for the majority of respondents, even in late 2025. After decades of vendors promising to solve integration, it is still the dominant operational pain of enterprise marketing teams.

The reason is structural. In the 2nd Age of Martech, CDPs were architected as integration hubs pulling data from multiple sources into their own cloud, resolving identities there, and pushing segments back out. The approach made sense when data warehouses were passive analytics systems. It makes far less sense today, when platforms like Snowflake have become the active center of enterprise customer intelligence where data engineering, analytics, ML, and reverse ETL all converge on the same tables.

There’s a name for what’s happening: the warehouse as CDP. Companies are resolving customer identities, building segments, and driving activation directly from Snowflake without shipping data to a separate platform. This is the composable canvas architecture Brinker describes: data stays where it lives, and capabilities plug in around it.

“People sometimes forget about how important campaign data is when talking about Customer Data Platforms. I’m looking at campaigns all the time to figure out which ones we should run, which ones are working, which ones we should kill. If you can unify all your customer and campaign data — I sometimes call it the C-squared Data Platform — you can be smarter in your decisions.”
— Rick Schultz, CMO, Databricks
— from The New Martech “Stack” for the AI Age

Before explaining how to build this on Snowflake, let’s be precise about exactly where packaged CDPs fail because the vendor narrative has obscured the reality for too long.

The Real Problems with Packaged CDPs

1. They Are Not Fast to Deploy

The 60–90 day figure in CDP vendor marketing refers to getting a basic pipeline flowing — not a reliable identity graph. Enterprise CDP implementations such as Salesforce Data Cloud, Adobe Real-Time CDP, Twilio Segment, mParticle consistently take 12 to 24 months from contract to production-quality identity resolution. Data modeling alone is a multi-month project. By the time schema alignment, data quality remediation, connector configuration, and matching model tuning are complete, you’re well into year two.

2. They Are Not Cheap

Enterprise CDP contracts range from $300,000 to over $2 million annually before implementation. Systems integrators add $500,000–$1.5 million in year-one professional services. The Martech for 2026 survey confirmed that integration remained a Top 3 challenge even after organizations had deployed CDPs. CDPs don’t eliminate the integration burden, they shift it from between your internal Snowflake pipelines to between Snowflake and the CDP’s cloud. The friction doesn’t disappear; it moves, with a vendor in the middle.

3. Your Data Has to Leave Snowflake

Every packaged CDP requires your customer data to be replicated to the vendor’s cloud. That means extraction pipelines out of Snowflake, synchronization overhead as schemas evolve, bi-directional sync of resolved identities back, and a new data residency surface in every compliance conversation. The CDP becomes a perpetual derivative of your real data — always fighting to stay synchronized with the warehouse that is your actual source of truth.

4. Matching Is a Black Box

CDP vendors protect their matching algorithms as proprietary intellectual property. You accept their definitions of what constitutes a match, their confidence thresholds, and their merging logic. When a match is wrong and in large datasets some percentage will always be wrong, you cannot audit the decision, retrain the model, or implement domain-specific rules. For KYC/AML, patient identity, and regulated B2B environments, this opacity is a compliance liability.

5. Per-Profile Pricing Penalizes Your Growth

CDP pricing scales directly with profiles, events, and destinations. As your customer base grows, your CDP bill grows proportionally, often non-linearly. A pricing model that structurally penalizes your success. Snowflake compute scales with workload, not customer count.

6. They Create Lock-In at Your Most Critical Layer

“That openness at the storage layer gets rid of the locked-in aspect that’s plagued this industry. We wanted something that was portable and open so that we weren’t locked into a particular cloud.”
— Chris Wissing, Chief Product Officer, Epsilon
— from The New Martech “Stack” for the AI Age

Your customer identity graph is your most strategic data asset. Once it lives in a CDP’s data model — once your merge history, match confidence scores, and identity linkages are in their infrastructure — switching means re-resolving all your identities, remapping all downstream systems, and losing historical linkages that often cannot be reconstructed.

7. They Were Built for B2C — B2B Identity Is a Different Problem

Traditional CDPs were architected for resolving individual consumers across digital channels. B2B identity resolution requires resolving accounts, contacts within those accounts, and hierarchical relationships between subsidiaries, parent entities, and buying groups. A single enterprise account appears across Salesforce, ERP, ZoomInfo, Bombora intent data, and partner feeds under different names, domain variations, and DUNS numbers. Most B2B organizations running CDPs maintain separate account matching processes outside the CDP because the CDP simply cannot handle it.

Zingg on Snowflake: The Solution

Zingg Enterprise on Snowflake closes every one of these gaps. A native Snowpark architecture means the entire identity resolution pipeline — blocking, ML matching, clustering, incremental updates — runs directly within Snowflake’s compute environment. Zingg reads your records and writes a ZINGG_ID — a persistent, unified identity key — back to your Snowflake tables. No extraction. No vendor cloud. No round-trip.

“We want to own the core construct of the data and infrastructure. If we change agencies, all we need to do is flip the activation layer at the top. The foundation stays with us.”
— Kumar Ram
VP/Global Head of Marketing Data Sciences, HP

Your Entire Enterprise Data Estate, In One Place

Zingg on Snowflake draws on your full enterprise data estate, including finance records, ERP customer data, product usage signals, and partner data via Snowflake Data Sharing, rather than relying only on marketing data. The resulting ZINGG_ID connects a much richer identity than any CDP can generate from marketing data alone.

Snowflake Provides Data Quality — Zingg Provides Identity

Snowflake’s native infrastructure — dynamic data masking, row-level security, data sharing governance — combined with your existing dbt pipelines, Monte Carlo observability, or Great Expectations checks — ensures records are clean before Zingg processes them. Zingg adds the ML-based probabilistic matching layer on top.

B2B Account Resolution, Natively

Zingg on Snowflake resolves B2B accounts natively — account hierarchies, subsidiaries, buying groups — powering ABM in Adobe Marketo Engage, Salesforce Account Engagement, and 6sense.

The Production Architecture

Source data flows to Snowflake via standard ELT from Salesforce, HubSpot, e-commerce, and marketing platforms. Zingg runs via Snowpark; ZINGG_ID written back to Snowflake. Activation to Braze, Iterable, Klaviyo, Google Ads, and Meta flows through Hightouch or Census.

Conclusion

The Martech for 2026 survey made clear that integration is still the dominant pain in enterprise marketing technology — even after a decade of CDP adoption. The warehouse-as-CDP pattern exists because practitioners figured out there was a better way: keep the data in Snowflake, plug capabilities in around it, and stop paying the extraction tax. Zingg provides the ML engine. Snowflake provides the scale and governance. Your existing tooling provides clean records. The ZINGG_ID lives in your most trusted data environment — for B2C customers and B2B accounts alike.

The packaged CDP sells comprehensiveness. Zingg on Snowflake delivers ownership. Ownership compounds in your favor every year.

🔗 Zingg for Snowflake  |  Talk to the Team  |  Deployment Guides

📄 The New Martech “Stack” for the AI Age — Scott Brinker & Databricks (March 2026)
📄 Martech for 2026 — Scott Brinker & Frans Riemersma (December 2025)