Best Practices

CDP vs data warehouse: There's no debate; warehouses win | Census

Nicole Mitich
Nicole Mitich June 05, 2023

Nicole Mitich is the content marketing manager @ Census. She's carried a love for reading and writing since childhood, but her particular focus is on streamlining technical communication through writing. She loves seeing (and helping) technical folks share their wisdom. San Diego, California, United States

Ah, the mighty customer data platform (CDP), the ultimate tool for organizing and managing customer data – or is it? 

A decade ago adopting a Customer Data Platform (CDP) made sense: Your business was collecting more data about your customers than ever before, yet your teams weren't able to access and activate it. CDPs were touted as the silver bullet for teams looking to create a unified view of their customer base. 

Today, you’re still collecting more customer data than ever before, but the landscape for managing that data has changed dramatically.

If you’re already storing all your customer data in a data warehouse, like Google BigQuery or Snowflake, and using tools, like dbt, to transform it, what’s the point of a CDP versus a data warehouse? 🤔 A warehouse doesn’t offer the same potential for data activation that a CDP does, at least, not by default. But that doesn’t mean that it can’t. With an alternative solution like data activation powered by reverse ETL, a data warehouse can function even better than a CDP.

Let’s compare some of the problems that CDPs aim (and fail) to solve and why activating data from your modern data warehouse with reverse ETL is a better way to unlock its potential.

The problems with CDPs

While CDPs have been hailed as the magic bullet for marketing teams, promising to unify all customer data into one accessible platform, they have their share of limitations and challenges (to put it lightly). So, we’re pulling back the curtain on some of the less-discussed issues with CDPs.

A CDP isn’t always a CDP

The goal of CDPs was to offer unified customer profiles, based on trusted customer data, without engineering. In practice, however, CDPs often specialize in different aspects of data management and activation. 

Many CDP vendors use definitions unique to them and emphasize specific features of their platforms, making them heavy on hype and buzzwords and light on clarity and customization. Some products that position themselves as CDPs are really only offering an additional resource for data analysis, rather than an all-in-one solution. Others share overlapping functionalities with marketing and data management tools, like Data Management Platforms (DMPs), Customer Relationship Management (CRM) systems, and marketing automation platforms.

In reality, buying a CDP today means buying a set of vaguely related customer data tools. It can be hard to know exactly what you’re getting. 🤷

CDPs don’t really provide a single source of truth

Though many CDPs claim to provide a single source of truth, that’s often not the case. Most don’t offer the same functionality that a suite of business intelligence tools can, so many businesses find they still need to use those tools in conjunction with a data warehouse or data lake alongside their CDP. 

There’s another source of truth right off the bat. 🙄

A data warehouse, on the other hand, can be used in conjunction with a Data Activation platform like Census to generate reports that are easily composable and digestible and that reveal insights from ALL of your customer data, across all sources within your organization. In other words, something much closer to that “single source of truth” that many CDPs claim to offer. 

CDPs don’t provide much flexibility

We’ve written before that CDPs require a significant initial investment of engineering time and resources to set up. And when you’re buying a legacy CDP, you’re also forced to evaluate everything upfront because you’re locked into a single platform.

But to use a CDP, you may also need to force your customer data to conform to a rigid structure. This might appear efficient at first, but businesses come in all shapes and sizes, meaning they require much more flexibility than what these CDPs can offer.

With most CDPs, it’s their way or the highway. If a CDP doesn’t offer the features you need, and you can’t find a way to integrate tools that do, you might find yourself looking for a workaround that doesn’t exist.

Turn your existing data warehouse into a CDP 

Your data warehouse already has many of the features an off-the-shelf CDP would provide, including data collection, data management, data transformation, and data governance. It’s also the one place that can rightfully claim to be the “single source of truth” for customer data.

All you need is a way to move data from your warehouse and make it accessible to all teams across your company, so they can activate and operationalize it across all their channels.

Data Activation platforms like Census enable teams to unlock data directly from the warehouse – without needing to know SQL — while still empowering data teams to maintain governance throughout your data stack rather than relying on a third-party CDP to ensure compliance.

In the battle of CDPs vs data warehouses for unifying and activating customer data, the data warehouse has won. 🏆 When combined with a Data Activation platform powered by reverse ETL, your data warehouse acts as the source of truth for customer data, and a place from which to activate that data across your business.

💡To find out more about building your own CDP with Census, get in touch or schedule a demo. We’ll talk you through the whole process.

Related articles

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps:

Best Practices
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue

Remember when the days of "Dear [First Name]" emails felt like cutting-edge personalization?

Product News
Why Census Embedded?
Why Census Embedded?

Last November, we shipped a new product: Census Embedded. It's a massive expansion of our footprint in the world of data. As I'll lay out here, it's a natural evolution of our platform in service of our mission and it's poised to help a lot of people get access to more great quality data.