Analytics and Tracking

CDP (Customer Data Platform)

Also called Customer data platform

Software that joins customer records from separate tools into one profile per person and sends audiences back out.

Quick facts: CDP (Customer Data Platform)

Category
Analytics and Tracking
Also called
Customer data platform
Level
Advanced
Affects
Audience targeting, reporting accuracy, personalisation, data governance
Where to see it
Segment, RudderStack, HubSpot, Klaviyo, often paired with BigQuery
In this article4
  1. How a customer data platform works
  2. Why a CDP matters
  3. Common mistakes with a CDP
  4. What to do about it

How a customer data platform works

A CDP sits between the systems that collect information about people and the systems that act on it. Your website sends behaviour, your CRM sends deal stages, your email tool sends opens and clicks, your shop sends orders. The platform takes those streams, matches them to the same person using a shared identifier such as an email address, a phone number or a logged-in user ID, and keeps one stitched profile for each customer.

Two jobs make it different from an ordinary database. The first is identity resolution: deciding that the anonymous visitor from Tuesday and the buyer who signed in on Friday are the same human being. The second is activation: pushing finished audiences back out to the tools that need them — an ad platform, an email platform, a support desk — without anyone exporting a spreadsheet by hand.

Why a CDP matters

Most marketing data is fragmented by accident rather than by design. Ad platforms know clicks, the website knows sessions, the sales team knows revenue, and nobody can join them, so the report that actually matters — which campaign produced paying customers — never gets produced. A CDP is where that join happens once, consistently, instead of being rebuilt by hand for every meeting.

It also matters as browser-level tracking weakens. The data you own outright — logged-in behaviour, orders, enquiries, phone calls — carries more weight than it used to, and a CDP is where first-party data is kept in a usable shape rather than trapped inside whichever tool happened to collect it.

Common mistakes with a CDP

The most expensive mistake is buying one before there is a question it answers. A CDP does not create data quality, it inherits it. If events fire inconsistently, if the CRM holds duplicate contacts and if the email tool uses a different definition of a customer, the platform will unify that mess faithfully and at some cost. Sort out event naming and identifiers first.

The second is treating a CDP and a data warehouse as the same purchase. A warehouse is built for analysis across long history; a CDP is built for resolving identity and sending audiences out quickly. Plenty of businesses need the warehouse and never need the CDP.

The third is consent. A unified profile is exactly the kind of processing that privacy law cares about, so consent state has to travel with the record rather than being checked once at the point of collection and then forgotten.

What to do about it

Start by writing down the decisions you cannot make today and the fields each of them would need. If the gap is reporting, a warehouse with a reporting layer on top is usually cheaper and simpler to run. If the gap is genuinely activation — sending a live, deduplicated audience into ad and email tools every week — then a CDP earns its place.

Whichever route you take, agree on a single identifier as the spine, make sure it is captured everywhere including on offline enquiries and phone leads, and connect systems in order of value rather than all at once. For many smaller businesses a properly planned CRM integration delivers most of the benefit for a fraction of the effort.

Do and do not

Do

  • Name the decisions a unified profile must support first
  • Agree one identifier and capture it everywhere
  • Carry consent state with every stitched profile

Do not

  • Buy a CDP to repair inconsistent event tracking
  • Confuse it with a warehouse built for analysis
  • Connect every system at once without a priority order

Questions people ask about this

Do I need a CDP or is my CRM enough?

A CRM records what your team knows about a contact: enquiries, deals, notes and calls. A CDP adds behaviour from systems your team never touches, such as website events and ad interactions, and then sends audiences back out automatically. If your reporting gaps are about sales pipeline, improve the CRM. If they are about joining anonymous behaviour to known customers, consider a CDP.

Is a CDP the same thing as a data warehouse?

No. A warehouse is a store built for querying large amounts of history, and it happily holds data that has nothing to do with marketing. A CDP is built around people: it resolves identities into single profiles and pushes audiences into other tools. Many teams run both, and many teams only ever need the warehouse.

Will a CDP fix inaccurate tracking?

It will not. A CDP unifies whatever it is fed, so inconsistent event names, missing tags and duplicate contacts survive the move and become harder to spot inside a merged profile. Fix collection first: agree event definitions, deduplicate the contact database and confirm identifiers are captured on every form and offline enquiry.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.