Adobe Real-Time CDP: Editions, Packages and What It Does

Adobe Real-Time CDP (Real-Time Customer Data Platform) is Adobe's customer data platform. It runs on Adobe Experience Platform and joins data from your website, apps, customer relationship management (CRM) system and other tools. The result is one real-time profile for each person or account. It then builds audiences from those profiles and sends them to channels and ad platforms, under governance rules you set. Adobe sells it in three editions: business-to-consumer (B2C), business-to-business (B2B) and business-to-person (B2P). Each comes in a Prime or an Ultimate package.

This guide explains what Real-Time CDP does and how the editions and packages differ. It also covers what drives cost, how implementation works and who actually needs it.

What is Adobe Real-Time CDP, in plain terms?

Real-Time CDP answers one question for every team: who is this customer, right now? It pulls in known data, such as CRM records and orders, and anonymous data, such as website visits. It links the identifiers that belong to the same person and keeps a live profile you can act on.

Adobe's documentation sums it up in four jobs. You get a single view of the customer from data across the enterprise. You manage profiles with governance and privacy controls. You use AI to find and grow audiences. And you deliver personalized experiences across channels and destinations in real time.

What does that look like day to day? A shopper browses as a guest, then logs in. Real-Time CDP merges the guest browsing with her existing account into one profile. She now qualifies for a "likely gift buyer" audience. Within moments, that audience can change what she sees on the site and which ads she gets. That's the core idea: data in, one profile, audiences out.

How does Real-Time CDP relate to Adobe Experience Platform?

Real-Time CDP is an application; Adobe Experience Platform (AEP) is the foundation it runs on. Adobe is explicit that a Real-Time CDP license includes the platform services it depends on, rather than being a separate purchase.

Those platform services do the heavy lifting. Experience Platform handles ingestion, Experience Data Model (XDM) schemas, Identity Service, the Real-Time Customer Profile, segmentation and governance. Real-Time CDP is the marketer-facing layer that turns those services into a workflow for unifying data, building audiences and activating them.

This matters for two reasons. First, it's the same foundation that Adobe Journey Optimizer and Customer Journey Analytics use. An audience you build in Real-Time CDP is available to both without exporting it. Second, Experience Platform now sits under Adobe CX Enterprise, the brand Adobe says replaces Experience Cloud. If you hear either name, it's the same family of apps. Our guide to Adobe omnichannel customer engagement shows how those apps work together.

Which editions and packages does Adobe sell?

Adobe sells three editions, and each one comes in a Prime and an Ultimate package. You choose the edition by the kind of profiles you manage, and the package by how far you need to activate data.

Edition	Built for	License metric
Real-Time CDP B2C Edition	Consumer marketing, person profiles	Per 1,000 Person Profiles
Real-Time CDP B2B Edition	Account-based marketing, people and accounts	Per 1,000 Businessperson Profiles
Real-Time CDP B2P Edition	Both, in one CDP, for the same person across lines of business	Business and consumer audiences, each per 1,000 profiles

The B2B edition adds B2B schemas and identity resolution for people and accounts, with account hierarchies. It also has a purpose-built connector for Adobe Marketo Engage. If you run Marketo, our post on Marketo and Adobe integration covers that link. The B2P edition is for firms that sell to consumers and businesses and want one profile per person across both.

The Prime and Ultimate split works the same way in every edition. Prime includes the standard features. Ultimate adds four things:

• Activation to advanced enterprise destination connectors
• Access to advanced enterprise source connectors
• A Profile API calls entitlement, for reading profiles from your own systems
• The Destination SDK (software development kit), so you can build your own destination connectors

So if you only need Adobe's standard destinations, Prime may be enough. If you need to stream profiles into your own systems or custom endpoints, look hard at Ultimate. Confirm the exact package with your Adobe account team, because guardrails and included capabilities vary by tier.

What are the core capabilities?

Five capabilities do most of the work. Here's what each one does and what to check.

Profiles and identity

Identity Service links identifiers, such as a cookie ID, email address, CRM ID and loyalty ID, into an identity graph. The Real-Time Customer Profile then merges data around that graph. The risk to watch is "graph collapse," Adobe's term for two different people merging into one profile, often through a shared device. Adobe's identity graph linking rules let you mark identifiers such as a CRM ID as unique to prevent it.

Segmentation

Experience Platform evaluates audiences in three ways. Streaming segmentation updates audiences as new data arrives. Batch segmentation runs on all profiles at once, and batch audiences are evaluated automatically every 24 hours. Edge segmentation evaluates on Adobe's Edge Network right away, which enables same-page and next-page personalization.

Destinations

Destinations are pre-built connections that send audiences or datasets to marketing tools, ad platforms and other systems. You choose from a catalog and schedule exports. In Ultimate, the Destination SDK lets you build your own.

Data governance

You apply data usage labels to datasets and fields, then write policies about what each label allows. When someone tries an action that breaks a policy, Real-Time CDP blocks it and explains which policy was violated. Regulated industries should test this part closely in any demo.

AI features

Customer AI, a bundled service, applies pre-built propensity models. Adobe says they predict which customers are most likely to convert, purchase or engage. Look-alike audiences find people similar to an existing consumer audience. Adobe also now lets teams explore and build audiences in natural language with Adobe CX Enterprise Coworker, its AI teammate.

What add-ons and related offerings should you know about?

Real-Time CDP has a long list of add-ons. These are the ones buyers most often need to understand before signing.

• Federated Audience Composition: builds and enriches audiences from data that stays in your warehouse.
• Privacy and Security Shield: automated consent policy enforcement, customer-managed encryption keys and higher dataset expiration limits.
• Healthcare Shield: a package with similar controls for healthcare organizations.
• Extra capacity: additional data volume, sandboxes, computed attributes, batch segmentation, look-alike audience packs and Customer AI insights.
• Real-Time CDP Profile Orchestration: triggered one-to-one journeys based on events you define.
• Real-Time CDP Collaboration: a data clean room for working with advertisers and publishers, which Adobe says is in limited availability by region.
• Real-Time CDP Connections: server-side data collection and forwarding through Adobe's Edge Network.

A practical tip: list the add-ons in your quote line by line and map each one to a use case. If nobody can name the use case, ask why it's there.

How is Real-Time CDP different from other CDPs?

CDPs differ less in what they claim and more in where they keep the profile and who uses it. Here's how Real-Time CDP sits, described as fairly as we can.

Real-Time CDP stores profiles in Adobe's platform and evaluates audiences in real time, including on the edge. That suits same-session web and app personalization. It also shares one profile with Journey Optimizer, Customer Journey Analytics and Target, so much of Adobe's suite runs on it. Its B2B and B2P editions model accounts, opportunities and buying groups in the same profile store.

Other approaches start elsewhere. Warehouse-native or composable CDPs keep the profile in your data warehouse and activate from there. CDPs built into a CRM platform, such as Salesforce's Data 360 (formerly Data Cloud), put the profile next to sales and service records. Real-Time CDP now meets the warehouse approach partway, through Federated Audience Composition. Our Adobe Marketing Cloud vs Salesforce Marketing Cloud comparison sets the two vendors side by side.

Adobe publishes its own comparison page, which says rivals fall short on things like real-time data and B2B support. Treat those as vendor claims. The fair test is a proof of concept on your data, judged on the use cases you'll actually run.

What drives Real-Time CDP cost?

Adobe doesn't publish Real-Time CDP prices. Cost comes from the license metrics and limits in Adobe's product descriptions, plus implementation and running costs. These are the drivers to model:

• Profiles: the edition's licensed profile count, in blocks of 1,000. Adobe notes that going over an entitlement can mean overage fees or buying more capacity.
• Profile richness and data volume: the B2C edition, for example, allows an average of up to 75 kilobytes per profile. Rich event histories use that up fast.
• Package: Ultimate adds advanced connectors, Profile API calls and custom destinations, so confirm you need them before you price it.
• Add-ons: each shield, capacity pack and AI option is a separate line.
• Sandboxes: the base license includes up to five, which can feel tight with several brands or regions.
• People: data engineering, governance and marketing operations time, whether in-house or through a partner.

One cost you control directly is what you ingest. Data that no audience or analysis needs still counts toward richness and volume. So decide what each source is for before you load it.

How do you implement Real-Time CDP, step by step?

Adobe's own summary of getting started is a good outline. You connect data sources, map them to XDM schemas, configure identities and merge policies, and set governance labels and policies. Then you build audiences and connect destinations.

In practice, a first phase usually runs like this:

• Pick use cases first. Choose one or two high-value use cases, such as suppressing recent buyers from ads or recovering abandoned carts.
• Design schemas and identity. Decide which identifiers you trust, set your primary identity and turn on linking rules.
• Label data as you go. Apply governance labels when you design schemas, not after launch.
• Connect a small set of sources. Start with web or app events plus one system of record, such as CRM or orders.
• Build and test audiences. Check audience sizes against what you expect from your source systems.
• Activate and measure. Connect one or two destinations and track a business outcome for each use case.
• Widen in slices. Add sources and use cases one at a time.

Adobe also notes that teams typically pair a data engineer or architect with the marketing owner of each use case. That pairing is worth copying. For how to judge the firms that do this work, read our guide to evaluating Real-Time CDP implementation partners.

Who needs Adobe Real-Time CDP, and who doesn't?

Real-Time CDP earns its cost when real-time activation and governance across many channels are central to your plans. It's a weaker fit when your needs are simpler.

It tends to suit you if:

• You need same-session personalization on web or app, not just next-day audiences.
• You already run, or plan to run, Journey Optimizer, Customer Journey Analytics or Target.
• You manage both consumer and business buyers and want one profile per person.
• You work in a regulated industry and need enforceable data usage policies.

It may be more than you need if:

• Your main goal is building warehouse audiences for a few ad platforms on a daily schedule.
• You have one or two data sources and no plan to add real-time channels.
• You don't have, and can't hire or contract, data engineering capacity to run it.

What should you do next?

Before you talk to Adobe or a partner about Adobe Real-Time CDP, work through this list:

• Write down three use cases, the channels they touch and the outcome you'll measure.
• List your data sources, owners, volumes and identifiers.
• Decide which edition fits: B2C, B2B or B2P.
• Check whether you need Ultimate's custom destinations and Profile API calls.
• List the add-ons you think you need, with a use case next to each.
• Agree who will own schemas, identity and governance after go-live.

Then shortlist firms with documented Real-Time CDP work on our Adobe Real-Time CDP partners page. Our methodology explains how we gather that evidence. Finally, send your shortlist our Real-Time CDP RFP template so their proposals are comparable.