Often these days, I get asked the question by our clients: “How do you pick a good CDP?”. Although it isn’t easy to answer, it’s always a great question to get. While comprehensive answers that fit your exact niche, needs and vertical would take a detailed deep dive by one of our consultants, I’ll attempt to answer a few of the more common points to consider, as I see them.
As the title suggests, this is one of the most common questions, and as a vendor agnostic MarTech consultancy, it is one we are well positioned to be able to respond to. After all, if you are aligned solely to Salesforce, then their proprietary CDP would doubtless seem ideal, equally in the Adobe world, they have the formidable Real Time CDP offering. When your tool is a hammer after all, every problem looks like a nail. In any case, the annoying answer to the question is, as you might have already guessed is, it depends.
That’s a fair point, I’m sure we can dive into that a little, correct a few misconceptions.
The first thing I strongly recommend as a critical dependency is, to define some rock-solid business critical requirements from your ideal CDP. The second thing to do is to DEFINE SOME REQUIREMENTS. I know I said that twice, but it bears reinforcing like you wouldn’t believe. A lot of the time I talk to Marketers who tell me they need a CDP, then can’t convey a solid clear understanding of their business needs from a CDP. With that approach, I guarantee they will be able to find a vendor and implementation partner just fine for any CDP on the planet, but without some specific tangible needs surfaced by the business, not to mention an understanding of what not having them is costing your business, both strategically and materially, the project isn’t going to realise anything like the value you may think.
The next thing I want to recommend is, to work very hard to create a common understanding on what a CDP is and does, and what it will do for your business, not what it could do, or what it should do. Part of the issue with the wide, wide world of CDPs, is that their very flexibility as a toolkit makes it very hard to define as an actual product – it ends up being all things to all people, but without a common understanding, not everyone is going to be happy at the conclusion of a CDP implementation project.
This is one of the many subtle tripping points on the road to getting yourself a future-proofed data unification capability that will stand you in good stead for the years to come.
I could go on all day, but I’ll leave you with this final thought – how do you measure the Return on Investment for a CDP? Often, a well-deployed CDP can be as much about saving money as it is about creating additional revenue – a CDP saves software development time and money by using common third-party integrations supported by that CDP (provided you thought to check the integrations before you purchased!), saving you the cost of building them yourselves. To provide a counterpoint however, due to these custom integrations you will come to depend on, it might be harder to get off a CDP in the future than it was to get on one, so great care must be taken to consider the long term as well as the short and the medium, when choosing a CDP.
If you’d like to talk about how Purple Square could help you with your CDP approach, either from a strategic perspective to help you select the one that’s right for you, or to provide business analysis and technical resource to bridge gaps of understanding and capability within your organisation, we’d love to hear from you.
The Rise of Customer Data Platforms. With all the buzz about Customer Data Platforms (CDPs), I read ...
Big data, is it still relevant? Back in 2015, Gartner coined the term Big Data, a term for data sets...