Best Practices

6 CDP Identity Resolution Mistakes (And How to Stay Clear)

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

Oh, identity resolution… It’s touted as one of the best features of customer data platforms (CDPs) because it transforms a jumble of data points into a coherent customer profile. And CDPs really lean into that sentiment with their marketing copy. They promise that with identity resolution you can:

“Create a 360° view of your customer!” 

“Deliver personalized experiences across all channels!”

“Drive customer engagement like never before!”

That all sounds well and good, but in reality, identity resolution opens up a minefield of potential pitfalls. One misstep and your customer data may blow up into a mess of contradictions and inaccuracies. 💣

But don’t panic! We’ll help you sidestep the six most common errors in managing customer data so you emerge with an accurate, unified view of your customers.

The biggest mistake of all?

It's tempting to think that a shiny, off-the-shelf CDP is the answer to all your prayers. But here's the thing: that's probably your first mistake.

The truth is, you don't need to buy a CDP at all. In fact, you can build your own composable CDP, custom-built to your company’s unique needs and capable of growing and adapting with your business.

The rise of the modern data stack and data activation means that companies now have access to best-in-class solutions for each component of a traditional CDP. Book a demo with one of our product specialists to see how we can help you sync customer data to all your marketing and advertising tools, without any code.

Just follow our lead. We’ll get you where you need to be.

1. Inadequate data management

Proper data management is crucial for creating complete and accurate customer profiles. 

Not collecting enough data or not collecting the right types of data is like trying to paint a portrait with only half the colors on your palette. 🎨 You might end up with something vaguely resembling your subject, but the details, the nuances, the things that make them unique, will be lost.

Then there’s the issue of data quality. Poor data quality is like a scratchy recording of a song. It's there but distorted, marred by static and interference. Inaccurate, outdated, or incomplete data can lead to poor identity resolution, resulting in a complete misunderstanding of the customer and, ultimately, ineffective marketing strategies.

2. Disregard for data privacy

It's easy to overlook or dismiss data privacy as an afterthought, but disregard it at your peril! Not respecting data privacy regulations can lead to legal issues and damage your company’s reputation.

Treat your customers' data with the respect it deserves. After all, it's not just data; it’s a reflection of the individuals behind it.

3. Failure to update customer profiles

Failing to update customer profiles is like playing a piano that's out of tune. 🎹 The keys are all there and the pianist plays skillfully, but no matter how good the pianist is, the music is discordant and jarring. 

Customer behavior and preferences can shift over time, just like the tension of a piano string. If customer profiles aren’t regularly updated, it can lead to outdated information and inaccurate identity resolution.

And without the most recent data, your understanding of your customers is outdated, and your marketing strategies may miss the mark.

4. Over-reliance on third-party data

There's first-party data, collected directly from your customers, and there's third-party data, collected by other entities and purchased for use in your CDP.

First-party data is more likely to be accurate, relevant, and compliant with privacy regulations, and it allows for more unique and personalized customer insights. Third-party data, on the other hand, can be useful for providing additional insights or filling gaps in your own data. But it's not a substitute for first-party data, just a supplement. 

After all, third-party data is available to anyone willing to pay for it, including your competitors.

5. Ignoring offline data

Imagine trying to understand a story when you've only read every other page. 📕 You might get the gist of the narrative, but key plot points will be lost. The same is true for customer data. Without offline data, your understanding of your customers is full of holes.

Offline data (think: in-store purchases, call center interactions, and event attendance) can provide valuable insights into customer behavior that online data alone can't capture.

6. Not testing and validating

Testing and validating is the dress rehearsal before the show. It's the final check, the last opportunity to catch any missteps before the curtain rises. 🎭

Not testing and validating is like skipping the dress rehearsal and going straight to opening night. It's a risky move and can lead to missed cues, forgotten lines, and a performance that falls flat. In the context of CDPs, not testing and validating can result in inaccurate identity resolution,  a poor understanding of your customers, and marketing misfires.

Steer clear of these mistakes, and you’ll be well on your way to effective identity resolution

Identity resolution may feel like a minefield of potential mistakes, but if you've been following along, you're now equipped with a map and a metal detector.

And if you're looking for a way to navigate the complex world of identity resolution with more control, flexibility, and precision, a composable CDP might just be the way to go. 🧭 Unlike an off-the-shelf CDP, with fixed features and capabilities, a composable CDP is custom-built to suit your unique business needs.

🗺️ If you're ready to take the first step on this journey, why not try Census to build clear, unified customer profiles and sync them everywhere? Book a demo now.

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: