SAP Customer Data Platform: When You Actually Need It

Every SAP CX sales pitch eventually includes the Customer Data Platform. “You need unified customer profiles.” “You need consent management.” “You need real-time segmentation.” And the slide looks impressive — a perfect circle connecting every touchpoint.

The reality is more nuanced. CDP is a powerful product that solves a specific problem. Most mid-sized companies don’t have that problem. Some large enterprises don’t either. Buying a CDP because it appeared on an architecture diagram is one of the more expensive mistakes in the SAP CX portfolio.

Here’s an honest guide to when you actually need SAP CDP — and when you’re better off without it.

TL;DR: Most companies don’t need a CDP yet. You need one when customer data lives in 5+ systems, you operate 4+ engagement channels, and you’re managing 200K+ profiles. A Gartner survey found only 14% of organisations have achieved a true 360-degree customer view — CDP helps close that gap, but only if your data quality is solid first.

What Does SAP CDP Actually Do?

The global CDP market hit $2.4 billion in revenue in 2024 (CDP Institute, 2024), with some analysts projecting growth to $28.2 billion by 2028 (MarketsandMarkets, 2024). That’s a lot of hype. But what does the product actually do?

SAP Customer Data Platform does three things:

1. Unified Customer Profiles

CDP collects customer data from multiple sources — your CRM, commerce platform, marketing tool, service desk, POS system, mobile app — and merges it into a single profile per customer.

This isn’t just putting records in one database. CDP handles identity resolution: matching “john.smith@company.com” from your email campaigns with “John Smith, Account #4521” in your ERP with “anonymous visitor #a8f3” who browsed your website. Different identifiers, same person. And that matters — Gartner found only 14% of organisations have actually achieved a 360-degree customer view, despite 82% aspiring to it (Gartner, 2022).

2. Consent and Data Governance

CDP tracks which data you’re allowed to use, for which purpose, based on the customer’s consent. GDPR, FADP, and other regulations require this — and enforcement is real. GDPR fines totalled EUR 5.88 billion since 2018, with EUR 1.2 billion issued in 2024 alone (DLA Piper, 2025). CDP makes consent operational — every campaign, every personalisation, every data export respects the consent profile.

3. Audience Segmentation and Activation

Once profiles are unified and consent is managed, CDP lets you build segments (e.g., “customers who bought Product A in the last 90 days, opted in for email, and haven’t visited the website in 30 days”) and activate them — pushing those segments to Emarsys, SAP Commerce, Google Ads, or any connected channel.

When Do You Genuinely Need CDP?

Here’s where it gets practical. According to Tealium’s 2024 survey of 1,200+ companies, 89% of CDP adopters met their business goals — compared to just 60% without one (Tealium, 2024). But that stat hides an important detail: the companies that succeeded had the right use case. CDP earns its cost in specific scenarios.

Do You Have Customer Data in 5+ Systems?

The average organisation now uses 897 applications, but only 29% are integrated (MuleSoft/Salesforce, 2024). That’s a staggering integration gap. If your customer data lives in SAP Sales Cloud V2, SAP Commerce Cloud, Emarsys, a legacy ERP, a POS system, and a customer service tool — you have a data fragmentation problem. Sales sees one version of the customer. Marketing sees another. Service sees a third.

CDP solves this by creating the authoritative customer profile that all systems reference. Without it, you’re maintaining duplicate records, and every “personalised” campaign works with incomplete data.

The threshold: If your customer data lives in 2-3 systems that are already well-integrated (e.g., Sales Cloud + Emarsys with native sync), you probably don’t need CDP. Five or more systems with different identifiers and no single source of truth? That’s when CDP starts making sense.

Do You Operate Across Multiple Channels?

A company that sells through a website, runs physical stores, operates a mobile app, and engages via email + SMS + social — that company has customer interactions scattered across systems that don’t talk to each other.

CDP connects these touchpoints. A customer who browses a product on the app, visits the store but doesn’t buy, then receives a targeted email with the right offer — that journey only works if something is connecting the dots. CDP is that something.

The threshold: Selling through a single channel (e.g., B2B direct sales through SAP Sales Cloud)? The touchpoint complexity is low enough that CDP adds limited value. Four or more channels? Worth evaluating.

Is Consent Management Business-Critical?

If you operate in the EU (GDPR), Switzerland (FADP), or any jurisdiction with strict data privacy laws — and you process customer data across multiple systems — consent management isn’t optional. Sixty percent of marketing leaders believe collecting customer data while balancing privacy will become more challenging (Gartner, 2023).

CDP doesn’t just store consent. It enforces it. When a customer withdraws consent for marketing in one channel, CDP propagates that withdrawal across all connected systems. Without CDP, you’re relying on manual processes. That’s a compliance risk — and 91% of CDP users report confidence in their platform’s privacy handling, versus just 57% of non-CDP companies (Tealium, 2024).

The threshold: If you process data in one system with built-in consent management (e.g., Emarsys handles your marketing consent fine), CDP isn’t needed for consent alone. If consent needs coordinating across 4+ systems, CDP becomes practical.

Do You Want Personalisation at Scale?

“Personalisation” in most marketing tools means “Hi {first_name}.” Real personalisation means: this customer bought industrial coffee machines, has a service contract expiring in 60 days, visited the accessories page yesterday, and should receive an email about the premium maintenance upgrade — not a generic newsletter.

McKinsey found that personalisation drives 10-15% revenue lift on average, and faster-growing companies derive 40% more revenue from personalisation than their slower peers (McKinsey, 2021). That level of impact requires a unified profile combining transactional data, behavioural data, contractual data, and communication preferences. CDP builds and maintains that profile.

The threshold: Basic personalisation (segment by purchase history, send relevant emails)? Emarsys handles this well alone. Combining data from 5+ sources for real-time personalisation decisions? CDP is the enabler.

When Don’t You Need CDP?

Here’s where we lose points with SAP’s sales team: most companies we talk to don’t need CDP. At least not yet.

Your Customer Base Is Small

If you have 10,000 customers and a single-channel sales process, a CDP is over-engineering the solution. Your CRM already knows who these customers are. CDP starts delivering measurable ROI when you’re managing hundreds of thousands of profiles across multiple engagement channels.

You Have One or Two Data Sources

CDP’s core value is unification. If your customer data lives in SAP Sales Cloud V2 and Emarsys — two systems with native integration — there’s little for CDP to unify. The data already flows. Add a commerce platform, a POS system, a mobile app, and a customer service tool? Now you have a unification problem worth solving.

Your Business Is Purely B2B With Direct Sales

B2B companies with a defined set of accounts and a direct sales model typically don’t have the touchpoint complexity that justifies CDP. Your sales reps know the customers. The data lives in the CRM.

Exceptions exist — B2B companies with thousands of SME customers, e-commerce channels, and complex distribution networks absolutely benefit from CDP. But the standard “50 enterprise accounts, managed by 10 sales reps” scenario? CRM is enough.

You Haven’t Fixed Your Data Quality

This is the most overlooked point. Only 12% of organisations report data quality sufficient for effective implementation of advanced data platforms (Precisely & Drexel University, 2024). CDP unifies data. It doesn’t clean it. If your CRM has duplicate contacts, your ERP has inconsistent naming, and your marketing tool has bounced emails marked as active — CDP will unify that mess into a unified mess.

Fix data quality first. Then consider CDP.

How Do You Decide? The 5-Question Framework

If you answered “evaluate CDP” on 3+ questions, it’s time to look seriously. If only 1-2, invest in getting more value from your existing tools first.

What Does a Practical Rollout Look Like?

Even when CDP is the right answer, it doesn’t have to be day one. We’ve found a phased approach works best — and the data supports patience: while 48% of CDP adopters see ROI within 6 months, 79% reach it within 12 months (Tealium, 2024). Rushing the rollout rarely helps.

Phase 1: Implement SAP Sales Cloud V2 and/or Emarsys. Get the core CRM and marketing automation right.

Phase 2: Connect the systems natively. Validate data quality. Identify where profile gaps exist.

Phase 3: Add CDP when the use cases are clear, the data is clean, and the business has the maturity to use unified profiles operationally.

This phased approach lets you prove value at each step and make the CDP investment decision based on real experience, not PowerPoint architecture diagrams.

Our Honest Position

We implement SAP CDP. We’ve seen it transform customer engagement for companies with genuine data complexity. But we’ve talked more clients out of CDP than into it.

The best CDP implementation starts with the question “what problem are we solving?” not “the architecture says we need this box.”

If you’re evaluating whether CDP fits your situation, let’s talk through it. We’ll give you an honest answer — even if that answer is “not yet.”

Frequently Asked Questions

How much does SAP CDP cost?

SAP doesn’t publish list prices for CDP — it’s licensed based on data volume and the number of connected sources. Expect a significant investment: CDP typically costs more than Emarsys or Sales Cloud individually. The total cost includes licensing, implementation (typically 3-6 months for Phase 1), and ongoing data governance. That’s precisely why the decision framework above matters — you want to be sure the business case justifies the spend.

Can Emarsys replace CDP?

For marketing-focused use cases, Emarsys handles a lot of what people think they need CDP for: segmentation, campaign personalisation, and basic customer profiles. Where Emarsys falls short is multi-system identity resolution and cross-platform consent management. If your data lives in Emarsys and one or two other systems, Emarsys is likely enough. If you need to unify 5+ data sources for omnichannel activation, CDP fills the gap.

How long does a CDP implementation take?

A typical SAP CDP implementation runs 3-6 months for the initial phase, which covers data source integration, identity resolution setup, and basic segmentation. Full rollout — including advanced use cases, consent orchestration, and real-time activation — can take 9-12 months. The biggest variable isn’t the technology; it’s data quality. Companies that clean their data before starting CDP see significantly faster time-to-value.

What’s the difference between CDP and CRM?

CRM (like SAP Sales Cloud V2) manages known customer relationships — contacts, opportunities, interactions. CDP operates at the data layer: it ingests data from CRM, commerce, marketing, service, and anonymous web behaviour, then resolves identities across all sources to create a unified profile. Think of CRM as the system sales reps use daily; CDP as the data backbone that feeds all customer-facing systems.

Do I need CDP for GDPR compliance?

Not necessarily. GDPR compliance requires lawful data processing and consent management, which individual systems can handle on their own. CDP becomes valuable for compliance when consent must be synchronised across 4+ systems — ensuring that a customer’s opt-out in one channel is immediately respected everywhere. For single-system setups, built-in consent tools are sufficient.