Quick answer
A customer data platform (CDP) is software that collects first-party customer data from many sources, merges it into a persistent profile for each person, and makes those profiles and audiences available to other systems such as email, ads and support tools.
What is a customer data platform?
A customer data platform (CDP) is software that pulls customer data from many sources, combines it into one profile per person, keeps that profile over time, and shares it with the other tools you use. The CDP Institute's definition stresses three things: packaged software, a persistent unified customer database, and access for other systems.
The four jobs of a CDP
- Collect events and attributes from websites, apps, servers, CRM, billing and support.
- Unify identities: match the anonymous visitor, the logged-in user, the email in the CRM and the customer id in billing to the same person. This is identity resolution.
- Build audiences: segments such as "trial users who visited pricing twice this week".
- Activate: send profiles and segments to email, ads, in-app messaging and support tools.
CDP vs CRM vs DMP vs analytics
| CDP | CRM | DMP | Product / web analytics | |
|---|---|---|---|---|
| Main data | First-party behaviour + attributes | Records entered by teams | Anonymous, often third-party | First-party events |
| Identity | Known and anonymous, unified | Known contacts | Anonymous cookies / ids | Visitors, devices, users |
| Main job | Unify and activate | Manage relationships | Target ads | Measure and explain behaviour |
| Keeps data | Long term | Long term | Short term | Per retention setting |
The lines blur. Many analytics tools now have user profiles and segments, and many CDPs have reporting.
Packaged vs composable
- Packaged CDP: one vendor stores the data and provides collection, identity, segments and connectors.
- Composable CDP: the data stays in your own warehouse; separate tools handle collection, modelling and "reverse ETL" to send audiences out. More control, more work.
Do you need one?
You probably do if you have several products or brands, customer data spread across many systems, and teams that need the same audiences in many tools. You may not if you have one product, a handful of tools, and an analytics tool with profiles, segments and a way to send segment changes out.
Privacy duties
Joining data from many sources creates a detailed picture of each person. You need a lawful basis for each purpose, a record of consent where required, the ability to find and erase one person's data across systems, and clear data governance. This is general information, not legal advice.
How TapCub overlaps
TapCub is an analytics tool, not a CDP. In identified mode it builds a person profile at login, links devices and visitors to that person, and shows identity links, segments, tags and accounts on the profile. Rule, static, RFM and live segments can emit a webhook when membership changes, which covers simple "send this audience to another tool" cases. Email and phone are hashed before lookup, and data subject requests (access, export, erasure) are handled in the privacy center.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.