SAP CDP vs CDC: What Each Does and When You Need Both

SAP has two products with confusingly similar names: SAP Customer Data Platform (CDP) and SAP Customer Data Cloud (CDC). They solve different problems, serve different users and sit at different layers of your architecture. Because both carry “customer data” in the name, they get mixed up constantly, and that confusion leads to expensive decisions.

Many conversations we have with prospects start with “we need a CDP” when what they need first is CDC, or the other way round. This guide separates the two.

TL;DR: CDC is the front door: registration, login, single sign-on and consent, the part your customers see. CDP is the engine behind it: it pulls data from CRM, ERP, commerce, marketing and CDC itself into unified profiles for segmentation and activation. Most companies need CDC first, because a CDP that unifies the wrong people is worse than none. You need both once consent captured at the front door must be enforced in five or more downstream systems.

What does SAP CDP do?

SAP Customer Data Platform pulls data from the systems your business runs, such as SAP Sales Cloud V2, SAP Service Cloud, SAP Commerce Cloud, SAP Engagement Cloud (formerly SAP Emarsys), the ERP and non-SAP sources, into one profile per customer. It is a back-end tool. Your customers never see it; marketing, sales and analytics use what it produces.

What CDP does:

• Resolves identities by matching the same person across email, phone, loyalty ID, website cookies and CRM records
• Enriches profiles by adding behavioural data (browsing, purchases, service interactions) to master data
• Builds dynamic segments that update as behaviour changes
• Activates data by pushing profiles and segments to Engagement Cloud, Commerce Cloud, advertising platforms and analytics
• Enforces consent centrally, so every downstream system respects the customer’s current status

SAP sums this up in three principles: Unify, Respect, Activate. Whether you need it at all is a separate question, answered in our guide on when you actually need SAP CDP.

What does SAP CDC do?

SAP Customer Data Cloud is SAP’s customer identity and access management (CIAM) offering, built on the former Gigya technology. It is the front door of your customer experience: registration forms, login screens, consent dialogues and profile pages. SAP Help lists three products under it: Customer Identity, Customer Consent and CIAM for B2B.

What CDC does:

• Registration and authentication with social login, email and password, passwordless (FIDO) login and single sign-on across applications
• Consent management that captures, stores and versions consent under the GDPR, the Swiss nDSG and other privacy laws
• Progressive profiling, which collects data gradually over several interactions instead of demanding everything at sign-up
• Security features such as risk-based authentication and account takeover protection
• B2B identity: organisation hierarchies, delegated administration and role-based access for business customers

Our CDC guide covers each product in more detail.

How do CDP and CDC compare?

How do they work together?

The strongest architecture runs both, with CDC as one of CDP’s sources. CDC captures identity, login events and consent records at the customer-facing layer; CDP combines them with CRM, commerce and service data.

The data flow:

1. The customer registers through CDC (social login, email or passwordless).
2. CDC records consent: which channels, which data, for how long.
3. CDP ingests identity and consent from CDC, plus purchases from Commerce Cloud, service history from Service Cloud and campaign responses from Engagement Cloud.
4. CDP builds one profile from all sources.
5. CDP pushes segments to Engagement Cloud for campaigns, to Commerce Cloud for personalisation and to Service Cloud for context.
6. When the customer changes preferences in CDC, CDP propagates the change to every downstream system.

GDPR and nDSG compliance then becomes a property of the architecture instead of a spreadsheet someone prepares before an audit. The order matters in practice: at Medion we first consolidated 2.8 million accounts from five markets into one CDC identity pool with a single consent schema. Only then could marketing build segments across all five markets.

Which should you implement first?

Not everyone needs both on day one.

Start with CDC when:

• You need compliant registration and consent management under the GDPR and the nDSG
• You are launching a customer portal, webshop or loyalty programme
• The same customer exists in several shops, brands or countries and should not
• You do not yet have five or more data sources to unify

Start with CDP when:

• Customer data already lives in five or more disconnected systems
• Marketing cannot build segments across channels without manual exports
• You manage well over 200,000 profiles that need deduplication
• Identity is already solved (CDC or an equivalent) and activation is the gap

Implement both when:

• You need governance from collection to activation
• Consent captured at the front door must be enforced everywhere downstream
• You are building one customer experience across commerce, marketing and service

Choosing a partner for this layer is its own question; our comparison of SAP CIAM and CDP partners in Switzerland and DACH sets out what to check.

Frequently asked questions

What is the main difference between SAP CDP and CDC?

CDC manages who the customer is: registration, login, single sign-on, consent and preferences, all visible to the customer. CDP manages what the customer does: it unifies data from many systems into profiles and segments for marketing, analytics and personalisation, and the customer never sees it.

Can CDP and CDC work independently?

Yes. CDP was built on the CDC technology foundation, but they are licensed and run as separate products. Many organisations start with CDC alone for identity and consent. CDP can ingest data from CDC and also works with non-SAP identity systems. Together they give the strongest setup: CDC captures identity and consent, CDP unifies and activates the data.

Which one handles GDPR and nDSG compliance?

Both play a role. CDC captures consent directly from the customer, stores it with an audit trail and lets customers view or change their preferences. CDP enforces that consent in every downstream system, so marketing, analytics and personalisation only use what the customer agreed to.

Do I need SAP Commerce Cloud to use CDP or CDC?

No. Both integrate with SAP and non-SAP systems. CDC can manage identity for any web application, app or portal, and CDP can ingest data from any system with an API. The Commerce Cloud integration is well established, but it is not a prerequisite.

How long does implementation take?

A standard B2C CDC rollout with registration, consent and single sign-on typically takes 6 to 10 weeks. The first CDP phase (source integration, identity rules and basic segmentation) typically takes 3 to 6 months. Doing both, implement CDC first so that CDP builds on a clean identity; multi-market programmes take longer because the work is reconciling identities and migrating consent.