# CDP vs personalization engine vs marketing cloud

> A customer data platform is the data foundation, a personalization engine is the decision layer, and a marketing cloud is a suite that bundles messaging and journeys with both. The three are sold together and converging, so most products now span several layers at once.

_Last updated 2026-11-01. From The Personalization Guide, https://personalization.guide_

A customer data platform (CDP), a personalization engine, and a marketing cloud are three layers of the
same stack: a CDP holds the data, a personalization engine makes the decision, and a marketing cloud
packages many jobs, including both of the others, into one suite. They are routinely sold together,
which is exactly why they get conflated.

The confusion matters because it hides what a product actually does. A tool pitched as "personalization"
might only be a data platform with no decision layer, or a suite whose personalization is a thin add-on.
Naming the layer tells you what you are buying and what you still need.

## The three layers

A **customer data platform** is the data foundation. It collects behavioral events, resolves identity
across devices and channels, and builds the profiles and audiences that everything downstream reads. Its
job is to make a trustworthy, unified view of the person available to other tools. It does not, on its
own, decide what to show anyone. See [the data and identity layer](/data) for how this layer succeeds or
fails.

A **personalization engine** is the decision layer. It takes the data and chooses and renders the
content, recommendations, or offers a given person sees, and it often bundles testing so you can tell
whether the choice helped. This is the part that actually changes an experience. It is only as good as
the data beneath it and the [measurement](/measurement) around it.

A **marketing cloud** is a suite. It bundles messaging and journey orchestration across channels, and
increasingly folds in both a data platform and a decision engine. Its value proposition is breadth:
one contract, one login, many jobs. Its trade-off is that any single layer inside it may be shallower
than a specialist tool.

## The distinguishing test

**Distinguishing test: data, decision, or suite?** When you ask what a product is, ask whether its job
is to hold the data, to make the decision, or to package many jobs into one platform. A CDP holds the
data. A personalization engine makes the decision. A marketing cloud packages both, plus messaging and
journeys. If a product answers "all of the above," it is a suite, and the useful follow-up is which of
its layers is strong and which is a box-ticking add-on.

## Why they are converging

The clean split above is blurring, on purpose. Data platforms are adding decisioning and orchestration.
Marketing clouds are rebuilding their personalization onto shared customer data rather than siloed
stores. And warehouse-native approaches push the whole stack toward deciding on the data where it
already lives, instead of copying it into a separate CDP. The categories still describe three real
jobs, but fewer and fewer products stay inside one of them.

So the honest answer to "which one is this?" is often "several layers at once." That is not a reason to
abandon the distinction. It is the reason to keep it: the only way to compare two products that both
claim to "do personalization" is to ask, layer by layer, which jobs each actually does, how well, and
on whose data. The broader map of these tools by function is on
[the personalization landscape](/ecosystem).