Adobe Experience Platform union schemas combine profile definitions into a shared view, bringing overlapping customer attributes from different data sources together. This structure helps teams understand interactions across touchpoints and shape more relevant personalization, without losing sight of how each data source contributes.

Multiple Choice

In Adobe Experience Platform, what functionality allows combining different profile definitions into a single schema?

The functionality that allows the combination of different profile definitions into a single schema in Adobe Experience Platform is known as Union Schema. This approach allows organizations to create a unified view of customer data by merging various profile definitions that may contain overlapping attributes or information. Union Schema facilitates a holistic understanding of customer interactions and behaviors by integrating diverse data sources into a singular, coherent schema. This enables more effective analysis and targeted marketing strategies. By using Union Schema, businesses can ensure that they are leveraging comprehensive data insights across all customer touchpoints, improving customer engagement and personalization efforts. As a result, this functionality is essential for organizations looking to optimize their customer data management in Adobe Experience Platform.

How Union Schemas Bring Customer Data Together in Adobe RTCDP

A customer rarely leaves a neat, complete trail behind. A purchase may sit in one system, an email interaction in another, and a support conversation somewhere else entirely. Adobe Real-Time Customer Data Platform (RTCDP) helps organizations bring these signals together. One important part of that picture is the union schema: a shared view of the fields used by compatible profile schemas in Adobe Experience Platform.

The name can sound technical, but the idea is straightforward. Think of several teams describing customers through different data sets. One tracks email addresses and loyalty status; another records app activity; a third stores purchase details. A union schema shows the combined set of fields available across the relevant schemas. It gives teams a broader map of customer data without requiring every source to use an identical schema.

A schema is the shape of the data

Before looking at union schemas, it helps to define a schema. In Adobe Experience Platform, a schema describes the structure and meaning of data. It sets out which fields can appear, what types of values they hold, and how they relate to a standard model.

For example, a customer profile schema might include a person’s name, email address, and loyalty tier. An experience event schema might describe a web visit, app action, or purchase. Adobe uses the Experience Data Model (XDM) to provide a common framework for these definitions. XDM gives data teams shared building blocks, which makes information from different systems easier to interpret.

That shared structure matters. If one system calls a field emailAddress and another calls it email, those names alone don’t tell a platform whether the fields mean the same thing. A thoughtfully designed schema helps make the meaning clear.

So, what does a union schema do?

A union schema is a combined view of the fields found in schemas that share the same underlying XDM class and are enabled for Real-Time Customer Profile. It brings their field definitions together for inspection and use in Profile-related workflows.

Imagine a company has two profile schemas. One stores contact details and consent preferences. Another includes loyalty information and customer service attributes. If both are based on the same XDM class and are enabled for Profile, Adobe Experience Platform can represent their combined field set through a union schema.

The result is not a new source file, nor is it a magic tool that rewrites every incoming record. It’s a view of the available schema fields. That distinction is easy to miss, but it’s important: a union schema combines schema structure; it doesn’t, by itself, merge all customer records into one finished profile.

The customer view needs more than a field list

RTCDP’s broader goal is to build useful, connected customer profiles from data gathered across touchpoints. A union schema supports that work by showing which fields are available to Profile. But the platform also needs the actual records, identity information, and rules that determine how those records relate.

For instance, a person might appear in a store system under a loyalty ID and in a mobile app under an email address. Identity namespaces and identity relationships help Adobe Experience Platform recognize links between those identifiers. When profile fragments are associated with the same person, merge policies determine how data is combined and which values take precedence when fields conflict.

So there are several connected pieces:

  • Schemas describe data structure and meaning.

  • Union schemas provide a combined view of fields from Profile-enabled schemas of the same class.

  • Identity services help connect records that refer to the same person.

  • Merge policies govern how profile fragments are assembled into a usable profile.

They work together, but they aren’t interchangeable. A union schema is more like a catalogue of available profile fields than a finished customer record.

Why does this matter for RTCDP?

A clear view of profile fields can help teams understand the data they can draw on for segmentation, personalization, and analysis. If marketers want to build an audience based on loyalty status and recent engagement, they need to know whether those attributes are part of the Profile data available to them. The union schema helps reveal that structure.

It also supports better coordination between technical and marketing teams. Data engineers can see how profile-enabled schemas contribute to the overall field set. Marketing teams can better understand what information may be available for audience definitions and customer experiences. That shared view can cut down on guesswork—especially when a business has many sources and several teams working with customer data.

There’s a practical benefit, too: a union schema can make it easier to spot gaps or overlaps. If two schemas contain similar fields, the team can review whether the definitions are consistent. If a key attribute is missing, that may point to a source-data issue or a schema design decision that needs attention.

A few limits worth keeping in mind

A union schema doesn’t mean that every field from every dataset appears in one universal structure. The schemas need to share the same XDM class, and they must be enabled for Real-Time Customer Profile to contribute to the relevant union. A schema used only for data storage or analysis may not be part of a Profile union.

Nor does the combined view guarantee that each customer has a value for every field. One profile might have a loyalty tier but no recent web activity. Another might have app events but no recorded purchase. The union schema describes the possible fields; the profile data itself determines which values are present for an individual.

This is where good data governance earns its keep. Clear naming, sensible field definitions, and careful identity design make customer data easier to interpret. Without those habits, a broad field list can become a crowded cupboard: technically full, but hard to use.

A simple way to think about it

Picture a set of labeled folders, each holding a different kind of customer information. The schemas define the labels and what belongs in each folder. The union schema gives you a combined index of the profile-related labels across compatible folders. Identity services help determine which folders belong to the same person, while merge policies guide how their contents come together.

That mental model keeps the roles distinct. The union schema is not the whole customer-data strategy, but it is a useful part of the foundation. In Adobe RTCDP, it provides a consolidated view of fields across Profile-enabled schemas that share an XDM class—helping teams understand the shape of their available customer data and build more coherent experiences from it.