#F8F8F8

ADOBE REAL-TIME CDP FEATURES

Flexible data connectivity

To deliver timely, personalized experiences, brands need flexible solutions that harmonize zero-, first-, second-, and third-party data into intelligent, actionable profiles without unnecessary duplication or movement. Flexibly connect to a wide variety of data sources for faster adoption, better data governance, and more scalable personalization.

Interface showing Amazon S3 and Facebook Audience connections with 560K profiles.

Composability

With Adobe’s flexible and warehouse-centric approach, enterprises can use Real-Time CDP to activate warehouse data and provide a pathway for marketing to impact real-time experiences without having to move or copy underlying datasets. Balance data strategy and business objectives with the flexibility to federate or ingest as much or as little data as desired, depending on use cases.

  • Focus on composability. Build audiences from warehouse datasets without copying underlying data, then use Adobe for enrichment and activation.
  • Ingest data directly from warehouses. Ingest data directly from enterprise warehouses into Adobe for audience creation and activation that powers low-latency, in-the-moment experiences.

Federated Audience Composition

Allow customers to create audiences directly from their data warehouse and enrich them with attributes from warehouse partners. With this flexible approach, customers can continue to ingest data directly from both internal and external sources.

  • Data integration. Boost flexibility and efficiency with the ability to query relevant pre-built audiences and datasets from your enterprise data warehouse and partners into a single environment to augment Adobe Experience Platform use cases.
  • Enhanced marketing processes. Unlock additional support for segmentation, targeting, and activation use cases with streamlined, adaptable workflows.
  • Efficient data management. Minimize data copy, govern sensitive data usage, and optimize IT investments to complement real-time cross-channel use cases on Adobe Experience Platform.
Connection setup screen showing Snowflake destination, selected audience and attributes, and a toggle indicating the connection is active.
Customer profile view showing details, a 1.47M profiles data-source chart, and counts of sources, datasets, and records ingested.

Data types

Real-Time CDP offers robust support for the full spectrum of data types, including zero-, first-, second-, and third-party data, to provide a well-rounded view of prospects, customers, and accounts, enabling successful engagement at every step of the journey.

  • Zero- and first-party data. Ingest or federate data directly from a variety of sources, from event-level customer-provided data to analytics, survey, commerce, and CRM data to fuel a comprehensive customer view.
  • Second-party data. With Real-Time CDP Collaboration, work with other brands, publishers, or data partners to enrich your existing audiences or discover new high-value audiences.
  • Third-party data. Use cookieless identifiers and hashed PII (personally identifiable information) from third-party data partners to reach net-new customers and reduce third-party cookie dependency.

Learn more about flexible connectivity.

Content as a Service v3 - Learn more about flexible connectivity. - Friday, January 16, 2026 at 13:45

Learn how to use flexible connectivity features.

Find what you need in Experience League, our vast collection of how-to content — including documentation, tutorials, and user guides.

Learn more | Learn more about how to use flexible connectivity features

Questions? We have answers.

Do I have to move all my data into Real-Time CDP, or can I leave it in my warehouse?
You do not have to move everything, because Real-Time CDP is composable: you decide, per dataset, when to ingest data into Experience Platform and when to leave it in your warehouse and query it in place. Enterprises increasingly keep large volumes of customer data in cloud warehouses, but marketing usually needs only a subset of it, and only for specific campaigns. Composability lets you ingest the data that powers low-latency, in-the-moment experiences while federating the rest, so you avoid duplicating data, bloating the profile, and standing up a new pipeline for every one-off audience.
What is the difference between ingesting data and federating it?
Ingesting brings data into Adobe Experience Platform, so it lives on the profile and powers low-latency, real-time experiences; federating queries the data where it already sits in your warehouse, without copying it. Ingest the data you need on the profile for in-the-moment use, such as recent behavior that drives same-session personalization. Federate data that is large, sensitive, historical, or only needed for a single campaign, so it stays in the warehouse as the system of record while still being usable to build an audience. The decision is per use case, not all-or-nothing.
How does Federated Audience Composition let me build audiences from my warehouse?
Federated Audience Composition lets you build and enrich audiences directly from your enterprise data warehouse using a zero-copy query, then use those audiences in Real-Time CDP without importing the underlying data. You connect a supported warehouse (such as Snowflake, Databricks, Google BigQuery, Amazon Redshift, or Azure Synapse), define which tables and columns are exposed, and compose audiences with a marketer-friendly interface, so a request that used to mean an engineering ticket and a multi-week pipeline becomes self-serve. It supports three patterns: creating audiences from warehouse data, enriching existing Experience Platform audiences with warehouse attributes, and enriching individual profiles.
Can I still power real-time experiences if my data stays in the warehouse?
Yes. By selectively ingesting the data that in-the-moment experiences depend on while federating the rest, you can power real-time personalization and same-page experiences without first copying every dataset into the platform. Federated data supports brand-initiated audiences and enrichment, and the smaller set of streaming data you ingest handles the low-latency signals that trigger real-time decisions, so composability does not force you to choose between warehouse ownership and real-time speed.
How does composability help IT and marketing work together without giving up governance?
Composability lets IT keep sensitive data governed inside enterprise systems while marketing self-serves the audiences it needs through a marketer-friendly interface. IT decides which warehouse tables and columns are exposed and keeps the data under its existing controls; marketing composes and activates audiences without waiting on a ticket for every request. Because governance labels and policies travel with the data into Experience Platform, this division of labor does not trade control for speed, it gives each team the part of the workflow it owns.