CDP

What it is

A Customer Data Platform (CDP) is a system that collects customer data from every source a business has, resolves it into a single persistent profile per person, and makes those profiles available to other tools. Unlike a data warehouse (built for analysts) or a CRM (built for sales and manual entry), a CDP is packaged software designed to be owned by business teams and to feed data back out for activation.

The defining trait is identity resolution: matching records that belong to the same person across channels (web, mobile, email, point of sale, support) into one unified, continuously updated profile.

Why it matters

• One version of the customer. Fragmented data across silos leads to inconsistent messaging and bad decisions.
• Actionable, not just stored. A CDP is built to push audiences and traits into downstream tools (ad platforms, email, personalization engines).
• Governance and consent. Centralizing data makes it easier to enforce consent, retention, and privacy rules (GDPR, CCPA).
• Speed for business teams. Marketers can build segments without waiting on engineering.

How it is used in practice

A typical CDP workflow:

• Ingest: pull events and attributes from web SDKs, apps, transactional databases, and SaaS tools.
• Unify: apply identity resolution rules (deterministic on email or user ID, sometimes probabilistic).
• Model: compute traits and audiences (for example, "high value at churn risk").
• Activate: sync segments to destinations for targeting, suppression, or personalization.
• Analyze: measure results and feed them back into the profiles.

Two common patterns exist: packaged CDPs with their own storage, and composable CDPs that run on top of an existing warehouse.

Worked example

A retailer has a website, a loyalty app, and an email tool. Anna browses running shoes on the site (anonymous cookie), later logs into the app with her email, then buys in store using her loyalty card.

• Without a CDP: three disconnected records, and Anna gets an ad for the shoes she already bought.
• With a CDP: the cookie, app login, and loyalty ID resolve to one profile. The CDP computes a trait (`recent_purchase = running_shoes`), builds a suppression audience, and syncs it to the ad platform so Anna is excluded, while adding her to a cross sell segment for socks and apparel.

The result is coherent, consent aware, and measurable engagement across every channel.