Webclat / Martech Practice
Webclat / Martech Practice  /  martech / cdp

Customer Data Platform Software

A CDP's job is narrower than its marketing suggests: unify customer data from multiple sources into one persistent, addressable profile. Here is what that means in practice, and the two comparisons that cause the most confusion.

Definition

Customer data platform (CDP) software ingests customer data from multiple sources - your product, your website, your CRM, your support tool - and resolves it into a single, persistent profile per customer that other systems (an ESP, a CEP, an ad platform) can then query or activate against. A CDP does not itself send marketing messages; it makes the data usable by the tools that do.

CDP vs CRM

CRMCDP
System of record forSales and account relationships - deals, contacts, ticketsBehavioral and event data across every customer touchpoint
Who typically owns itSales / support teamsMarketing / data teams
Update patternManual entry and workflow-driven updatesHigh-volume, largely automated event ingestion

The two are complementary, not substitutes: a CRM without a CDP has clean account data but a shallow, delayed view of behavior; a CDP without a CRM has rich behavioral data but no sales-relationship context. Where budget or maturity only supports one, the right choice depends on whether the immediate problem is sales visibility or marketing activation - see our do-you-need-a-CDP use case for that decision in more depth.

Composable CDP vs packaged CDP

A packaged CDP is a single vendor product covering ingestion, identity resolution, and activation together. A composable CDP is the same job assembled from separate best-of-breed pieces - a data warehouse for storage, a reverse-ETL tool for activation, an identity-resolution layer in between - wired together rather than bought as one SKU. Neither is objectively better: composable trades a lower licensing cost and more architectural control for real integration engineering overhead, a trade-off worth thinking through on our composable martech page before deciding.

Where Segment and Salesforce CDP fit

Segment is commonly evaluated as either a packaged CDP or the ingestion layer inside a composable stack, depending on how it's configured. Salesforce CDP (Data Cloud) is typically evaluated by organizations already committed to the Salesforce ecosystem, where native integration with Salesforce CRM and Marketing Cloud outweighs the cost of a best-of-breed alternative. Neither is covered here as an endorsement - both are named because they are the two vendors buyers most often compare against a general CDP purchase.

Frequently Asked Questions

What does a customer data platform actually do?

It ingests customer data from multiple sources and resolves it into one persistent, addressable profile per customer, which other systems can then query or activate against. It does not send messages itself - that's the job of a CEP or ESP layered on top.

Do I need a CDP if I already have a CRM?

They solve different problems - a CRM manages sales/account relationships, a CDP unifies behavioral data across touchpoints. Many organizations run both; which to prioritize first depends on whether the immediate gap is sales visibility or marketing activation. See our dedicated use case.

What is a composable CDP?

A composable CDP assembles the same job a packaged CDP does (ingestion, identity resolution, activation) from separate best-of-breed tools wired together, instead of buying one vendor's all-in-one product. It trades licensing cost for integration engineering work - see composable martech.

Not Sure If You Need A CDP, A Better CRM, Or Neither?

We look at your actual data sources and activation needs before recommending a category, let alone a vendor.

Get A CDP Fit Assessment