Customer Data Platforms: Building a Single Customer View
Key takeaway
A single customer view stands or falls on identity resolution — reliably deciding that a web visitor, an email subscriber, and an account holder are the same person. Solve that for your two highest-value channels first; buying a platform before you've agreed identity rules just centralises the confusion.
Most organisations hold customer data in five or six systems that each believe they have the complete picture. A customer data platform exists to unify those into one profile that marketing, support, and product can all act on.
How it differs from a CRM or a warehouse
- A CRM records the sales relationship — contacts, deals, activities — and is maintained largely by people.
- A data warehouse is built for analysis, typically batch-loaded and queried by analysts.
- A CDP unifies behavioural and transactional data into a live profile, and pushes segments back out to the tools that act on them.
Identity resolution is the hard part
Deterministic matching — same email, same account id — is reliable and should carry most of the work. Probabilistic matching on device, IP, and behaviour fills gaps and introduces errors, and an error here means showing one customer another's information. Decide your matching rules explicitly, write them down, and hold probabilistic matches to a higher bar for anything customer-visible.
A sequence that gets value early
- Pick one use case with a clear payoff — abandoned-cart recovery, churn-risk alerts, or giving support the full order history.
- Connect only the two or three sources that use case needs.
- Agree the identity rules and a canonical customer id before loading anything.
- Push the resulting segment into the tool that will act on it, and measure the outcome.
- Add sources as later use cases justify them — not because a connector exists.
Governance you have to build in
- Consent must travel with the profile — a suppression in one channel has to be honoured everywhere.
- Deletion requests must cascade to every downstream destination the data was pushed to.
- Keep a record of which source contributed which field; support will ask, and so will auditors.
- Don't centralise data you have no use for. A unified profile is also a unified breach target.