CDP vs DMP: a UK guide to the trade-offs

What to take away

A CDP builds persistent profiles from records you collect yourself; a DMP packages borrowed segments for advertising.
Third-party identifiers are less reliable and harder to justify than they were a decade ago, so the DMP case has narrowed.
Both platforms process personal data, and the UK GDPR plus the Data Protection Act 2018 apply to each.
Decide on governance and ownership first, features second.

The difference, stated plainly

A data management platform (DMP) collects pseudonymous identifiers, mostly cookie and device IDs, and sorts them into segments for programmatic advertising. Those segments are typically rented for a campaign rather than kept as customer records.

When the identifier expires, the audience expires with it. Nothing returns to your CRM, and nothing survives a change of browser or device.

A customer data platform (CDP) starts from records you already hold: purchases, email engagement, service contacts, app events. It resolves them into profiles that persist between campaigns, then activates them in email, paid media or service tools.

Most implementations succeed or fail on match quality rather than features. Before accepting a demo, agree how identity resolution should work in your UK CDP.

What changed for UK marketers

The UK left the EU in 2020 but kept the data protection rules in domestic law. Processing personal data is governed by the UK GDPR and by the Data Protection Act 2018, which applies across England, Scotland, Wales and Northern Ireland.

Advertising identifiers count as personal data when they can single out a person or a device. The ICO's UK GDPR guidance and resources place the burden on you to name a lawful basis before collection, not after.

Browsers have restricted third-party cookies for years, and consent banners have reduced what anyone can buy. A DMP built on those identifiers now works with a thinner pool.

None of this makes DMPs illegal. It makes them narrower: useful where reach matters more than identity, awkward where you must explain how a segment was assembled.

A comparison at a glance

A CDP may be positioned as a DMP alternative, but the two answer different questions. Read this as a set of trade-offs rather than a scorecard.

CDP vs DMP trade-offs

CDP

Core data: First-party records
Typical output: Persistent profile
Identity matching: Deterministic
Where it sits: Beside CRM
Retention: Your own policy
Main UK risk: Over-collection

DMP

Core data: Pseudonymous partner IDs
Typical output: Campaign segment
Identity matching: Probabilistic
Where it sits: Inside ad stack
Retention: Cookie lifetime
Main UK risk: Shared consent

CDP

Core data: First-party records you collected
Typical output: Persistent customer profile
Identity matching: Deterministic links across owned sources
Where it sits: Beside your CRM, warehouse or service desk
Retention: Set field by field in your own policy
Main UK risk: Collecting more than you can justify
Usual owner: Marketing, data or customer teams

DMP

Core data: Pseudonymous identifiers from partners
Typical output: Campaign audience segment
Identity matching: Probabilistic matching across external data
Where it sits: Inside the advertising stack
Retention: Usually tied to the cookie lifetime
Main UK risk: Explaining consent for shared identifiers
Usual owner: Media buying

Where a DMP still earns its place

Keep a DMP in the mix for prospecting, where you need reach beyond your own file and you are not trying to identify anyone. It can also suit media teams buying across many publishers in one campaign.

The catch is evidential. If a partner supplies a segment, you still need a record of how consent was obtained and what your contract permits.

A decision sequence of five steps

Write the decision in one sentence and name its owner. "Which lapsed customers would return" is a decision; "improve personalisation" is not.
List the fields you already hold, with the lawful basis and retention period for each. Anything you cannot name is not ready to activate.
Test whether your warehouse or CRM can answer the question today. If it can, read CDP vs data warehouse before you sign anything.
Ask each vendor to show the deletion path for one record, end to end, in writing.
Set a review date and a stop condition, so the decision stays reversible.

Common questions

Is a DMP still lawful in the UK?

Yes, where the identifiers are collected and shared with a valid lawful basis and people have been told what happens to their data. The difficulty is evidential rather than legal: you must be able to show how each segment was built.

Can a CDP replace a DMP?

For retention and service messaging, usually yes. For prospecting to people who have never heard of you, no, because a CDP holds no records for them.

Which costs less to run?

There is no reliable category-wide answer: headline licence fees do not capture identity matching, quality checks and deletion work. Compare costs per field and per record, not per seat, using the cost guide.

Do we need both?

Only if prospecting and retention are genuinely separate programmes with separate owners. Otherwise start with the CDP, and treat a DMP as a campaign expense rather than a platform.