Adobe Real-Time CDP, shipped to live activation.
Stand up Real-Time CDP for B2C, B2B, or B2P. Audiences that activate to the destinations that matter, in real time, with consent honored at the profile layer.
[ GET THE 2026 BENCHMARK → ]What Real-Time CDP is, and what it is not.
Adobe Real-Time CDP is the activation surface of the Adobe Experience Platform. It is where the unified profile becomes useful: segmented into audiences, activated to channels, and updated in real time as the profile changes.
It is not a marketing automation tool. It is not a journey orchestration tool. Real-Time CDP is the pipe that delivers the right audience to the right activation surface, fast. The orchestration belongs in Adobe Journey Optimizer or in your existing journey tool. The decisioning belongs in the layer above.
The most common Real-Time CDP gap we see is treating it as a campaign tool. The activations are configured one per campaign. The audiences are defined one per send. The profile is refreshed once a day. None of this is wrong. All of it is leaving the value of the license on the floor.
B2C, B2B, and B2P editions.
Real-Time CDP comes in three editions. The shape of the implementation differs.
B2C edition
The default. Person profiles, individual identities, real-time event ingestion. The activation surface is the largest. The XDM schema is people-first.
B2B edition
Account, opportunity, and buying group as first-class entities. Person profiles still exist, but they roll up to accounts. The schema is more complex. The audiences are different. The Salesforce and Marketo connectors do most of the heavy lifting.
B2P edition
Business-to-person. Used where the buying decision is made by an individual but inside an organization. Combines the discipline of B2B with the activation surface of B2C. The integration to the rest of your stack is the place most implementations stall.
Audience strategy.
The first audit we run on every existing Real-Time CDP deployment is the audience inventory. We list every audience. We name the owner. We name the use case. We name the activations connected to it. The number of orphaned audiences in a typical deployment is between 30% and 60%.
The second audit is the audience definition itself. We look at how each audience is built: the segmentation logic, the qualification window, the refresh cadence. The most common pattern is audiences built once and never reviewed. The second most common is audiences built with logic that no longer matches the schema underneath.
We treat the audience layer as a product. It has an owner. It has a roadmap. It has retirement criteria. It is reviewed quarterly.
Federated Audience Composition.
Federated Audience Composition is the most under-deployed advanced feature in Real-Time CDP. It allows you to compose audiences over data that lives in Snowflake, Databricks, or BigQuery, without ingesting that data into AEP. The warehouse stays the source of truth. The audience composition happens at query time. The activation flows through the same Real-Time CDP destinations.
The reason this matters: most enterprises have years of behavioral, transactional, and product data in the warehouse that never made it into AEP. Federated audience composition unlocks that data without the months of ingestion work.
We have shipped federated composition for retail, financial services, and B2B software. The typical lift is 4 to 6 weeks. The unlock is permanent.
Activation.
Real-Time CDP ships with a long list of pre-built destinations. We have configured most of them. We have also built custom destinations for the integrations that the catalog does not cover.
The discipline: every destination is a defined contract. Every audience activated to a destination is named, owned, and measured. Every activation has a documented refresh cadence and a documented escalation path when it breaks.
Consent and privacy by design.
Consent in Real-Time CDP is not a checkbox. It is a layer. We implement consent at the data ingestion layer, the profile layer, and the activation layer. The result is a system where the consent decisions made by your customers are honored in every audience that gets built and every destination that gets activated, automatically.
We have shipped this under HIPAA, GDPR, and India DPDP. The pattern generalizes.
How we engage on Real-Time CDP.
A new Real-Time CDP implementation runs 8 to 14 weeks alongside the AEP foundation. An optimization of an existing deployment runs 6 to 10 weeks. A federated audience composition rollout runs 4 to 8 weeks.
Every engagement starts with a 25-minute readout where we tell you what we think the gap is and how we would close it.