Best Practices

CDP Use Cases: 6 Clever Ways to Maximize ROI of Customer Data

Nicole Mitich
Nicole Mitich March 02, 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

Imagine walking into your favorite store and being greeted by name, shown products you've been eyeing online, and offered a special promotion ✨ just for you. ✨ Sounds pretty sweet, right? 

This is the kind of personalized, seamless experience that businesses can create with a customer data platform (CDP). A CDP is like a digital memory bank for your business, collecting and organizing data on your customers' behavior, preferences, and interactions. With this information at your fingertips, you can create more targeted marketing campaigns, optimize pricing strategies, and more.

The problem? CDPs were intended to be a repository of customer information, but by trying to give fast data access to marketing teams, the CDP created yet another silo of data. So, how can you reap the benefits of a CDP without fighting against multiple data silos? Enter: The composable CDP. 😮

In this post, we'll dive into six ways businesses are using a traditional CDP to satisfy their use cases, and how you can fulfill those same use cases more effectively using something you probably already have: A data warehouse.

⚠️ Believe the CDP hype, but don't believe you need to go out and buy one ⚠️

As a concept, CDPs are great, but as another silo for your data, buying a CDP should be a hard pass. 🚫 You likely already have many of the components of a CDP inside your company's data platform.

Why not leverage these building blocks to build your own composable CDP? You already collect and transform data, so all that you need is a way to activate that data to make it accessible across your company. This is where a reverse ETL tool like Census comes in. 

If you’d like to learn more about how Census can help you build your own CDP solution out of your existing data infrastructure, read The best CDP is already in your data warehouse.

Use Case #1: Identity resolution

Do you understand your customers? Are you sure? If each tool in your stack has data about your customers, none have the full picture. While CDPs claim they can help create a unified, 360° view of a customer by identifying all the data points that are related to that customer and consolidating them into a single profile – they can’t. 

Sure, they are storing increasing amounts of customer data, but they don’t have the full picture of the customer because marketing automation and support systems are still disconnected and have limited activation capabilities. 🚫 

But here’s the good news: Your data team already maintains a central nervous system for storing information – your data warehouse. So, instead of forcing customer data to conform to a rigid structure to store in a CDP, build a composable CDP on top of your data warehouse and use reverse ETL to do “continuous” syncs between your tools and your warehouse. This flexibility allows you to have complete control over how you unify customer identity rather than the one size fits all approach associated with traditional CDPs.

Now…

✅ The support team gets to resolve issues more quickly.

✉️ The marketing team gets to send more personalized messaging.

⏱️ The sales team gets to reiterate product value at just the right time.

What's not to love? 

Use Case #2: Personalization

Personalization is one of the key benefits of a CDP. By gathering data on customer behavior and preferences to create detailed customer profiles, businesses can build more targeted and relevant marketing campaigns, product recommendations, and customer service interactions. 🎯

For example, if a customer frequently purchases running shoes, they may be more likely to be interested in promotions for running gear or events. 👟Personalized product recommendations that resonate with customers keeps them coming back.

In theory, customer service interactions could be improved too. Unfortunately, with a traditional CDP, customer service reps can only access the silo of customer data that the CDP has collected – instead of the fresh data in your warehouse.

That means that when they try to access a customer's purchase history, previous interactions, and any notes or flags, they may not be getting the most up-to-date data available. Alternatively, when you create your own composable CDP using a data warehouse, you’re not at the mercy of what a legacy tool can or cannot access.

Use Case #3: Segmentation

A CDP can be used to gather data on customer demographics, behavior, and purchase history, and then segment customers based on that data. 

By segmenting customers based on their purchase history and demographics, businesses can identify high-value audiences and offer them exclusive promotions, or conversely, identify customers who are sensitive to price and offer them discounts to encourage them to make a purchase. 🫰

You can also create targeted marketing campaigns that are tailored to specific segments. For example, a bank can create a campaign targeting older customers with a focus on retirement savings products, while a different campaign targets younger customers with a focus on student loan consolidation products.

But CDPs don’t have the full picture of the customer and are costly and slow to implement for segmentation. Using a warehouse-native data activation platform in its place, however, gives marketing teams access to 360° customer data for segmentation. Marketers can create targeted audiences that are more likely to convert with a complete view of customer attributes and interactions. 

Use Case #4: Omnichannel marketing

CDPs can be a powerful tool for organizations looking to implement an omnichannel marketing strategy. With their claims of unifying customer data, they promised that you could engage customers across multiple touchpoints and channels with consistent and targeted messaging, driving higher loyalty and conversion rates. 📈

Yet CDPs haven’t delivered on the expectations that many teams have of them. Often the CDP doesn't offer the same functionality that a suite of business intelligence tools can, so many businesses find that they still need to use said tools in conjunction with a data warehouse or data lake alongside their CDP. The CDP then just becomes yet another silo of data.

Instead, using your data warehouse as part of a composable CDP, you could create your own CDP solution that does everything you need it to. The best part? Previously siloed data that was only available after going to 5 different marketing tools now stays in sync and makes your marketing more scalable and automated.

Use Case #5: Predictive modeling

Predictive modeling is another powerful use case that folks often turn to a CDP for. A CDP can be used to gather data on customer behavior and purchase history, which can then be used to create predictive models.

A predictive model can be used to identify customers who are at risk of churning so that the business can take steps to retain them. Other predictive models can be used to estimate customer lifetime value, identify which customers are most likely to respond to a specific marketing campaign, or which customers are most likely to need assistance from customer service.

But a composable CDP can be used for this same application. In fact, it works even better since you know your customer data is fresh and accurate. 🧼

Since data scientists typically deploy their predictive models within the data warehouse, instead of waiting for the output of those models to sync to a traditional CDP, with a composable CDP the output is available in real-time for use in marketing automation tools.

Use Case #6: Data governance

Data governance and compliance is another common use case for a CDP. 

Compliance with data protection regulations such as General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA) is crucial for businesses. These regulations set strict guidelines for how personal data can be collected, stored, and used – and non-compliance can result in costly fines and reputational damage. 👎

Unlike a data warehouse which provides a single, central location for storing customer data, a CDP only has access to a partial view of customer data. And syncing all the available data into your downstream tools not only drives up costs – since many downstream tools like Braze charge to store data – it also simultaneously creates multiple copies of the data with no governance. 

So, how would you know if you’re really in compliance with the regulations? 😨 That's exactly why warehouse-native data activation is so important

Warehouse-native data activation tools are purpose-built to sync data from the warehouse to downstream tools at scale. They have robust support for bulk APIs and give you more control over what data gets synced, both ensuring data quality and data governance.

Bottom line: If you want to increase customer engagement and drive growth, a traditional CDP will fail you.

Give your company the advantage of fast access to data, but don’t fall for buying an expensive CDP solution that has rigid data models, long onboarding times, and redundancies across analytics and marketing tools.

A CDP provides a lot of overlapping functionality to that of your company's existing data platform, so just turn your existing data platform into a composable CDP. The rise of the data warehouse as the single source of truth paired with warehouse-activation tools like Census takes away the need for organizations to invest in expensive all-in-one CDP solutions that don’t provide time-to-value. 

With data activation and reverse ETL democratizing access, the data warehouse is best positioned to become the system of customer record that powers not just your marketing technology, but the entire business operations of the company.

👐 If you’d like to learn more about how Census can help you, schedule a demo, and we’ll talk you through it.

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: