SAP Customer Data Platform: When You Actually Need It

Every SAP CX architecture slide eventually lands on the Customer Data Platform: unified profiles, consent management, real-time segmentation, a perfect circle around every touchpoint. The slide looks convincing. The licence is not cheap.

SAP CDP is a solid product for a specific problem: customer data spread over many systems with no shared identity. Many mid-sized companies do not have that problem yet, and some large ones do not either. Over the past two years we have advised more clients to wait on CDP than to buy it. This guide explains what the product does, how to tell whether you need it, and how to introduce it without betting the budget on a diagram.

TL;DR: SAP CDP unifies customer data from CRM, commerce, marketing, service and ERP into one profile per person, enforces consent across those systems and pushes segments to the channels that act on them. You need it when customer data lives in five or more systems, you run four or more engagement channels and you manage well over 200,000 profiles. Below that, SAP Sales Cloud V2 and SAP Engagement Cloud usually cover the need. Fix data quality first, whichever way you decide.

What does SAP CDP actually do?

SAP Customer Data Platform launched in 2020 and is documented on the SAP Help Portal. It works on three principles: Unify (merge data from many sources into one customer identity), Respect (honour consent and privacy preferences), and Activate (push profiles and segments to the systems that use them). In practice that breaks down into five capabilities.

Identity resolution

CDP matches the same person across email addresses, phone numbers, loyalty IDs, website cookies and CRM records. “john.smith@company.com” from a campaign, “John Smith, account 4521” in the ERP and anonymous visitor “a8f3” on the website become one profile. This is harder than it sounds, especially in B2B, where several buyers sit under the same company account. On some projects we have spent whole sprints on identity rules alone.

Consent and data governance

Every data point carries consent metadata. CDP links consent to purposes and subscriptions and enforces it downstream: when a customer withdraws marketing consent in one channel, every connected system respects it. Under the GDPR and the Swiss revised Data Protection Act (nDSG/FADP) this is what makes consent operational rather than a checkbox. If identity and consent are captured at the front door by SAP Customer Data Cloud, CDP takes them over from there (see SAP CDP vs CDC).

Continuous data ingestion

CDP ingests data continuously: purchases from SAP Commerce Cloud, campaign engagement from SAP Engagement Cloud (formerly SAP Emarsys), cases from SAP Service Cloud, plus any non-SAP source you connect via API. Profiles update within minutes rather than after a nightly export, which matters for a flash sale or a service escalation.

Segmentation and activation

Once profiles are unified and consent is known, you build segments (“bought product A in the last 90 days, opted in for email, no website visit in 30 days”) that update themselves as behaviour changes, and push them to Engagement Cloud, Commerce Cloud, advertising platforms or analytics. This is what separates CDP from a data warehouse: the warehouse stores data for reporting, CDP acts on it.

Monitoring and event mapping

CDP tracks ingestion status, profile completeness and segment health, and stitches events across sources: a website visit, the purchase that followed, the service case after it. That is how you see the customer journey end to end and how you find out whether your personalisation works.

When do you genuinely need CDP?

CDP earns its cost in specific scenarios. Four questions decide it.

Is your customer data in five or more systems?

If customer data lives in SAP Sales Cloud V2, SAP Commerce Cloud, Engagement Cloud, a legacy ERP, a POS system and a separate service tool, you have a fragmentation problem. Sales sees one version of the customer, marketing another, service a third. CDP creates the profile all of them reference.

Threshold: two or three systems that are already well integrated (for example Sales Cloud V2 and Engagement Cloud with the standard integration) usually do not need CDP. Five or more systems with different identifiers and no single source of truth is where it starts to pay.

Do you operate across several channels?

A company that sells online, runs stores, has an app and communicates by email, SMS and social media has interactions scattered across systems that do not talk to each other. A customer who browses in the app, visits the store without buying and then receives the right offer by email only exists as one journey if something connects the dots. CDP does.

Threshold: one channel, such as B2B direct sales through SAP Sales Cloud, rarely justifies CDP. Four or more channels are worth evaluating.

Must consent be coordinated across systems?

If you process customer data in several systems under the GDPR or the nDSG, consent cannot live in one of them alone. CDP propagates a withdrawal from one channel to every connected system; without it, you rely on manual processes and accept the compliance risk.

Threshold: if one system with built-in consent handles your marketing (Engagement Cloud does this well), CDP is not needed for consent alone. Consent that must stay in sync across four or more systems is a different matter.

Do you want personalisation beyond “Hi {first_name}”?

Real personalisation combines several sources: this customer bought industrial coffee machines, has a service contract expiring in 60 days, looked at the accessories page yesterday and should get an offer for the maintenance upgrade. That needs transactional, behavioural, contractual and preference data in one profile.

Threshold: personalisation by purchase history and email behaviour is something Engagement Cloud handles well on its own. Real-time decisions from five or more sources are where CDP becomes the enabler. Loyalty programmes are a typical case; we describe that combination in SAP Loyalty, Engagement Cloud and CDP working together.

When don’t you need CDP?

Saying this as an SAP partner costs us licence revenue, but most companies we talk to do not need CDP yet.

Your customer base is small

With 10,000 customers and one sales channel, CDP over-engineers the problem. Your CRM already knows these customers. CDP pays off when you manage hundreds of thousands of profiles across several channels.

You have one or two data sources

CDP’s core value is unification. If customer data lives in SAP Sales Cloud V2 and Engagement Cloud, which integrate as standard, there is little to unify. Add a commerce platform, POS, an app and a service tool, and the picture changes.

Your business is purely B2B with direct sales

B2B companies with a defined set of accounts and a direct sales model rarely have the touchpoint complexity that justifies CDP. The reps know the customers and the data lives in the CRM. The exception: B2B companies with thousands of SME customers, e-commerce and distribution networks do benefit. The standard “50 key accounts, ten sales reps” setup does not.

Your data quality is not fixed yet

This is the most overlooked point and, in our experience, the main reason CDP projects disappoint. In a 2024 survey by Precisely and Drexel University’s LeBow College of Business, only 12% of organisations said their data was AI-ready (Precisely and Drexel LeBow, 2024). Segmentation and activation run on the same data. CDP unifies data; it does not clean it. Duplicate contacts in the CRM, inconsistent names in the ERP and bounced addresses marked active in marketing become one unified mess.

Fix data quality first. Then consider CDP.

How do you decide? The five-question framework

Question	You don’t need CDP	You should evaluate CDP
How many systems hold customer data?	Fewer than 4	5 or more
How many engagement channels do you operate?	1 to 2	4 or more
How many customer profiles do you manage?	Under 50,000	Over 200,000
Is consent coordinated across systems?	Handled by one system	Needs sync across 4+ systems
Is your data quality solid?	No (fix this first)	Yes, CDP can build on it

Three or more answers in the right-hand column: time to look seriously. One or two: get more out of your existing tools first. Most companies we assess land in the “not yet” category, and that is a perfectly good outcome.

What does a practical rollout look like?

Even when CDP is the right answer, you do not have to introduce everything on day one. A phased approach works best, and the market data supports patience: in Tealium’s 2024 State of the CDP survey, 48% of CDP adopters saw a return within six months and 79% within twelve (Tealium, 2024; Tealium sells a CDP, so read the figures as a vendor survey).

Phase 1: Implement SAP Sales Cloud V2 and/or SAP Engagement Cloud. Get CRM and marketing automation right; that is where most of the immediate value sits. If customers log in anywhere, settle identity and consent now, usually with SAP Customer Data Cloud (what CDC does). At Medion we consolidated 2.8 million accounts across five markets into one identity before cross-market segmentation became possible.

Phase 2: Connect the systems through the standard integrations, check data quality and find the profile gaps. This phase often shows whether you need CDP at all.

Phase 3: Add CDP once the use cases are clear, the data is clean and the business is ready to use unified profiles in daily work.

Each phase proves its value, and the CDP decision is made on experience with your own data rather than on an architecture slide.

Our position

We implement SAP CDP, and we have seen it change customer engagement for companies with real data complexity. We have also advised more clients to wait than to buy. A good CDP project starts with “which problem are we solving?”, not with “the architecture has a box for it”. If you want a partner for the whole identity and data layer, our overview of SAP CIAM and CDP partners in Switzerland and DACH explains what to look for.

If you are evaluating whether CDP fits your situation, let’s talk it through. You get a straight answer, even if it is “not yet”.

Frequently asked questions

How much does SAP CDP cost?

SAP does not publish list prices for CDP; it is licensed by data volume and connected sources. Expect a significant investment, typically more than Engagement Cloud or Sales Cloud V2 on their own. Total cost includes licensing, implementation (typically 3 to 6 months for the first phase) and ongoing data governance, which is why the decision framework above matters.

Can SAP Engagement Cloud replace CDP?

For marketing-focused use cases, often yes. Engagement Cloud covers segmentation, campaign personalisation and basic customer profiles. It does not provide multi-system identity resolution or cross-platform consent management. If your data lives in Engagement Cloud plus one or two other systems, it is likely enough; if you need to unify five or more sources for omnichannel activation, CDP fills the gap.

How long does a CDP implementation take?

The first phase (data source integration, identity resolution rules and basic segmentation) typically takes 3 to 6 months. A full rollout with consent orchestration and real-time activation can take 9 to 12 months. The biggest variable is data quality, not technology: clean source data shortens the timeline considerably.

How is CDP different from a CRM or a data warehouse?

A CRM such as SAP Sales Cloud V2 manages known relationships: contacts, opportunities, activities. A data warehouse stores data for reporting. CDP sits at the data layer between them: it ingests CRM, commerce, marketing, service and anonymous web data, resolves identities into one profile, enforces consent and pushes segments to the systems that act on them.

Do I need CDP for GDPR or nDSG compliance?

Not necessarily. Lawful processing and consent management can be handled by individual systems. CDP becomes valuable when consent must stay synchronised across four or more systems, so that an opt-out in one channel is respected everywhere. For single-system setups, built-in consent tools are sufficient.

Does CDP replace SAP Customer Data Cloud (CDC)?

No, they complement each other. SAP Customer Data Cloud handles identity and consent at the customer-facing layer: registration, login, single sign-on and preference management. CDP takes that data, together with other sources, and builds profiles for activation. Many organisations run both, but each works on its own.