Insight

Building Customer 360 with Salesforce Data Cloud — Part 1

Publicis Sapient has more than 10 years of CDP experience. Along the way, we’ve encountered many definitions (and misconceptions) of CDPs framed by thought leaders, consulting firms, analysts and software providers.

A common misconception is that Customer Data Platforms are focused on marketing and, therefore, only for marketers. However, it is probably more accurate to frame CDPs as being about delivering the data, decisions and activations needed to inform an experience. We could even talk about CDPs in the context of risk management. But in any case, it is about bringing the data surrounding a customer together so a business can make a more informed, actionable decision. And marketers have, by default, become the most centralized owners of customer experience.

For us, it is a collection of software with an underlying unified customer database, all working together (as a platform) to drive decisions and activations that inform how we engage with a customer. (Our definition generally aligns with Wikipedia’s.) This is an incredibly important distinction because many software vendors want to drive home that a CDP is just a database and not much more. And while it is a crucial component of the platform — it will not — on its own, magically create the customer experience outcomes you’re hoping for. 

Now that we’ve expanded the idea of CDP — more akin to the idea of Salesforce’s Customer 360 branding — let’s go a little further into the different types of CDPs.

These categorizations fall into three primary buckets.

• Customer MDM:  This is not a CDP — full stop — although it can unify customer data into a golden record, which may be a critical input to a CDP. An MDM is a different category of software altogether.
• Enterprise CDP: Think of that very expensive data lake IT built several years ago that holds a lot of enterprise and customer data. It may have a lot of the data you need. But often, data lakes lack friendly interfaces and the integrations required to actually make use of the data. Unless you consider “friendly” to be a tech ticket and 2-week wait time to retrieve a segment that you forward to another team to activate. Yes, this does happen. Nonetheless, they do serve a purpose, often in analytics and feeding the Marketing CDP. In fact, if your company built this on Snowflake, then Salesforce’s CDP will soon bolt right onto it, taking advantage of previous investments in data engineering, etc.
• Marketing CDP: This is where most of the energy is right now. While an Enterprise CDP may have much of your customer’s profile and transactional data, you would use the Marketing CDP to augment that with behavioral data, which can be more transient. And the interface is simpler for business users to use, providing segment activation points to systems of engagement, like Salesforce’s Marketing Cloud, Personalization (FKA Interaction Studio), and Service Cloud via Data Cloud, which we’ll cover in another article.