Exporting Profile attributes when segmenting on a Reference Schema (Hotels/Loyalty example) | Community
Skip to main content
M
MuriloGu
Level 2
March 16, 2026
Question

Exporting Profile attributes when segmenting on a Reference Schema (Hotels/Loyalty example)

  • March 16, 2026
  • 1 reply
  • 38 views

Hello everyone,

I am currently trying to understand how schema relationships work in Adobe Experience Platform. Specifically, I am looking at the example involving Loyalty Members (Profile class) and Hotels (Reference schema).

My Scenario:

  1. I have established a relationship where the "Loyalty Members" schema (Source) points to the "Hotels" schema (Reference) via a preferredHotel field.

  2. Both schemas are enabled for Profile.

  3. I want to create an audience to segment all hotels where petsAllowed is True.

My Question: When I export this audience to a Destination, can I export the attributes of the Loyalty Member profiles (likepersonalEmail.address or name) that are linked to those qualified hotels?

If this is possible, how should I configure the Mapping in the Destination to ensure the Profile data is sent even though the segment criteria are based on the Reference Schema?

References:

Thank you for the help!

1 reply

SG14_97
SG14_97
Level 3
March 17, 2026

Hi ​@MuriloGu ,

From the above situation it looks like - Loyalty Members is a XDM:Individual Profile class member while Hotels is a custom lookup schema. 

Customer Segmentation rules are evaluated across individual profile, experience event and look up schema however the end goal is to create a list of qualifying customers for targeting purposes hence the output or the audience which gets created/updated is at profile level only (individual profile). 

So if you try to export this audience you can only reference attributes which are available at the XDM:Individual Profile level only and not the lookup data, so for your question you can share profile attributes however not the hotel level details (if they only exist as a lookup information).

Also there are other ways you can export this information out of Adobe using data distiller or using dataset export via destination service, so it really depends on your need and which destination and attributes you want to export downstream.

 

Regards,

Sayantan

M
MuriloGuAuthor
Level 2
March 17, 2026

Thanks for the clear explanation, Sayantan! It helps a lot to understand that the output is strictly at the individual profile level.

I'd like to dive a bit deeper into a different scenario: What if both schemas are enabled for Profile?

Consider this use case:

I have a Main Profile (Parent) and a Dependent Profile (Child). Both use the XDM:Individual Profile class, and they are linked via a Relationship field (e.g., parent_customer_id in the Dependent schema pointing to the Main schema's identity).

If I create a segment based on an attribute of the Dependent profile, such as an 'Active' status, is there a way to have the Main Profile qualify for that audience instead of the Dependent entity itself (or both)? I am curious if the audience always consists of the specific record that meets the criteria, or if the relationship allows the qualification to 'bubble up' to the parent.

This leads me to wonder if these relationships can only be fully explored through Query Service or Data Distiller, or if we can leverage this relationship potential within Audiences, and if so, how can we achieve that?

SG14_97
SG14_97
Level 3
March 17, 2026

hi ​@MuriloGu ,

Adobe’s XDM data model works in a different way so at the end of the day if you create two entities (for example in your case - Loyalty and Hotel) and both are at profile level (individual profile) then there is no need of creating a linkage since these fragments would be merged given that there is a matching identity and a namespace which is shared across these entities. The XDM model merges/creates a Union of all entities which belong to the same classes and segmentation service works on top of this unioned view.


So for your question if both are enabled for profile, segmentation service will only look at the unioned view and hence only qualifying fragments will be part of your audience output.

Relationships from Adobe data model perspective are mostly used for Lookup information which would help you with filtration purposes while building your target audience, and now you also have the provision to use lookup data in your journeys within AJO.

However to your ask if you want to export/analyze or activate towards external systems then you can do so via dataset export and create the expected aggregated/flattening/enrichment using data distiller.

Regards,
Sayantan 

Terms & ConditionsAccessibility statement

Loading footer...