Customer Data Platform (CDP) vs CRM vs DMP vs MDM vs Data Warehouse

A customer data platform (CDP) unifies behavioral and transactional data into persistent customer profiles that marketing and service tools can use. A CRM manages relationships and workflows, a DMP builds mostly anonymous advertising audiences, master data management (MDM) maintains governed master records, and a data warehouse stores data for analysis. They overlap at the edges but answer different questions, and mature stacks usually run several together.

Who this is for: architects, CTOs and data leads who need to decide which system owns which customer data. Part of the Learn hub; if the basics are new, start with what a customer data platform is.

The short answer: what each system is for

• Customer data platform. Software that creates and maintains a persistent, unified customer record other systems can access 1.
• CRM. The working system for sales, service and marketing teams. It stores contact details, interaction history, purchase history, opportunities and cases 2.
• DMP (data management platform). Built to assemble and reach advertising audiences, and dependent on third-party cookies 3. The category is shrinking: Oracle closed its advertising business in September 2024 34.
• MDM. A discipline and toolset that maintains a "golden record," a single source of truth for core entities such as customers, products, suppliers and locations 5.
• Data warehouse. A store for relational business data, aimed at batch reporting, BI and visualization 6.
• Data lake. A store that accepts structured, semi-structured and unstructured data and applies structure when read, used for machine learning, exploration and streaming 6.

Master comparison table

When you need which

Use these tests in order:

1. Who or what consumes the output? A person following up a case or deal points to a CRM. Another system receiving an audience or profile points to a CDP.
2. Is the data anonymous behavior or governed master data? Pre-login browsing and app events belong in a CDP. Legal entities and verified identities belong in MDM or a system of record.
3. Must the record be authoritative? Contracts, KYC files, clinical charts and billing stay in their systems of record. A CDP holds a working copy.
4. Is the work analytical or operational? Finance, risk and model training belong in the warehouse or lake. Triggering a message within a session belongs in the CDP.
5. Must it run inside your boundary? If regulation or policy limits where customer data may live, deployment model becomes a selection criterion. See composable vs packaged vs private CDP.

How they coexist in one architecture

In a typical stack the CRM and systems of record produce data, MDM supplies a trusted enterprise ID, the warehouse is the analytical home, and the CDP turns it into profiles and audiences for channels. Two patterns dominate. In an own-store design the CDP keeps its own profile store and syncs to the warehouse. In a warehouse-native design the warehouse is the store and the CDP layer sits on top; the CDP Institute lists own-store, warehouse-native and hybrid delivery 1, and Hightouch describes its composable CDP as an activation layer that does not store your data 7. More detail is in customer data platform architecture.

Customer data platform vs CRM

A CRM records what your team knows and does about a customer. A CDP records what customers do across channels, including before they identify themselves. CRM records change as staff work; CDP profiles change as pipelines deliver events. Most organizations run both, each feeding the other.

Customer data platform vs data warehouse

A warehouse stores modeled data for analysis 6. A CDP adds identity resolution, consent handling, audience building and activation connectors. You can build those pieces on a warehouse, which is the composable route, but someone has to own them. CX Today's write-up of the 2026 Gartner quadrant notes that Hightouch's warehouse-native architecture makes data engineering the customer's responsibility 8. Treat "warehouse or CDP" as a build-and-run question, not a data-storage question.

Customer data platform vs DMP

A DMP works on anonymous cookie and device IDs for advertising; a CDP works on first-party data you collect and can tie to a person. Forrester ties DMP decline to third-party cookie loss and notes that Salesforce is sunsetting Audience Studio while Adobe pushes DMP customers to its CDP 3. Definitions of first-, second- and third-party data are in zero-party, first-party and third-party data.

Customer data platform vs MDM

MDM governs the authoritative record of a core entity with stewardship and quality rules 5. A CDP assembles a marketing-ready view that includes behavior. MDM can supply the trusted customer ID; the CDP should not become the place where legal identity is decided. Identity methods are covered in identity resolution explained.

Customer data platform vs data lake

A lake keeps raw data of any type, with structure applied at read time 6. It has no built-in identity graph, consent model or audience delivery. Teams often land events there first, then feed the CDP.

Worked example: a retail bank

Systems. Core banking holds accounts and transactions. The CRM holds relationship-manager notes, leads and service cases. MDM issues the enterprise customer ID and links household and legal-entity records. The warehouse feeds finance, risk and regulatory reporting. The CDP holds digital behavior, consent state and marketing audiences.

Flow. A customer uses the mortgage calculator in the app but holds no mortgage. The CDP matches the app ID to the enterprise ID and builds "mortgage interest, no mortgage, email permitted." The audience goes to the email tool, and a task appears in the CRM for the relationship manager.

Rules that shape the design:

• Suppression must be global. An individual can object to direct marketing at any time, and processing for that purpose must then stop 9. The objection has to reach every channel, which is a CDP job.
• Credit decisions stay out of marketing audiences. AI systems that evaluate creditworthiness or establish a credit score are listed as high-risk in Annex III of the EU AI Act 10, with Annex III obligations now set to apply from 2 December 2027 11. Keep the credit-decision engine separate and review any use of credit-related features in segmentation with legal counsel. See EU AI Act for marketing and customer decisioning.
• Where the CDP runs is a regulatory question. EU financial entities subject to DORA must submit a register of information on their ICT third-party arrangements; in Luxembourg the 2026 deadline for most entities was 31 March 12. A SaaS CDP will typically need an entry in that register; a CDP in the bank's own environment is a different conversation. See DORA and your marketing stack, customer data platforms for banks and the financial services industry page.

Worked example: a healthcare provider

Systems. The EHR is the clinical system of record. A contact center or patient CRM handles calls and outreach. A master patient index (often called an EMPI) keeps one patient identity across clinical systems. The warehouse supports quality reporting. The CDP holds engagement data: website and app activity, communication preferences and consent.

Flow. A patient opts in to text reminders. The CDP sends appointment and follow-up messages using the patient's preferences. Clinical detail stays in the EHR.

Rules that shape the design:

• Marketing needs authorization. HIPAA generally requires authorization for marketing uses of protected health information, with narrow exceptions 13. The definition of marketing excludes some treatment and health care operations communications, except where a third party pays 14. Classify every message type before you automate it.
• A vendor handling PHI needs a business associate agreement. A covered entity may share PHI with a business associate only after obtaining satisfactory written assurance 15. Vendor routes differ: Twilio makes BAAs available on Segment's Business tier 16, Adobe offers a Healthcare Shield add-on for Real-Time CDP 17, and Tealium says it signs a BAA with Private Cloud customers 18.
• Minimum necessary. Covered entities must make reasonable efforts to limit PHI to the minimum necessary 15. Send the CDP identifiers and preferences, not diagnoses.

See HIPAA-compliant customer data platforms, HIPAA marketing rules and Patient 360 vs EHR.

Common mistakes

• Buying a CDP to fix CRM hygiene. Duplicate contacts and broken fields are a data-quality problem. A CDP will spread bad records faster, not repair them.
• Treating the CDP as a system of record. Contracts, KYC files and clinical charts stay at the source.
• Running an unreconciled second store. Two definitions of "active customer" erode trust. Decide which is authoritative.
• Expecting DMP-style reach from first-party data. A CDP reaches people you already know.
• Skipping consent propagation. Test that an opt-out reaches every destination, and survives identity merges.
• Sizing on known customers only. Twilio's pricing page describes its metered unit in terms of visitors 19; anonymous traffic counts.
• Deferring the deployment question. Ask early where data will live and who operates it. Pricing is covered in CDP pricing explained.

---

Not sure which of these systems you actually lack? Take the 12-question "Do you need a CDP?" checklist, then browse related explainers in the Learn hub. For a deployment that keeps profiles inside your own environment, see the PrivyCDP platform overview.