Best Practices

Don’t Let Your CDP's Data Model Be Your Downfall | Census

Nicole Mitich
Nicole Mitich June 29, 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

Think of your data as tiny puzzle pieces. Like a jigsaw puzzle enthusiast assembling thousands of pieces into a single, coherent picture, a customer data platform (CDP) pieces together disparate data points into a unified image of customer behavior. 🧩

And exactly how all this data is organized and stored is dictated by the CDP’s data model

Just as the puzzle enthusiast references the puzzle box to understand how each piece contributes to the overall image, the CDP’s data model outlines how each data point fits into the grand schema of customer information. 🖼️

Take a look at the following example of a typical CDP data model.

Typical cdp data model

Does any of this look familiar? If your company uses a modern data stack, you probably already store most of this information in your data warehouse.

So, why devote valuable time and resources to building and maintaining a new data model for your CDP when your data warehouse already holds all the data you need?

Pssttt... 👂 There's a more efficient way to leverage the power of CDPs without falling prey to the repetitive cycle of data modeling. 

Data Activation is the answer

You already have a data warehouse that acts as a centralized data hub, consolidating and storing customer data from any source. What's missing is the ability to make the data actionable in all of your marketing and advertising tools.

That’s where a Data Activation platform like Census comes in. Census unlocks and transforms all your raw, disparate data (in your data warehouse or data lake) into actionable insights that inform and enhance your business decisions and customer experiences. 

Data activation platform like Census to consolidate customer data

Census can also help you build a composable CDP using components in your stack to build a CDP on top of your existing data infrastructure. 

So you can engage in a glorified duplication process, wrestling with the complexity and rigidity of the CDP's data model when the very same information is already well-documented in your data warehouse, or you can get started with Census in 3 easy steps:

  1. Connect your data source. This can be a data warehouse like Snowflake, BigQuery, Redshift, or Databricks. Or a database like Postgres, SQL Server, or MySQL. 🔌
  2. Map fields to sync customer data. You can even define custom audience segments within Census Audience Hub to optimize your campaigns and messaging.🗺️
  3. Connect your destination application. We have integrations with 1300+ SaaS tools (and more on the way). 🤯

Book a demo with one of our product specialists to see how we can help you build custom audience segments and sync customer data to all of your marketing and advertising tools, without writing any code. 💪

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

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: