Using Attributes in Lookup Schema for Audience Segmentation in RTCDP | Community
Skip to main content
Z
ZacharyTa1
Level 2
August 13, 2025
Solved

Using Attributes in Lookup Schema for Audience Segmentation in RTCDP

  • August 13, 2025
  • 2 replies
  • 601 views

Hi AEP Community,

 

I'm facing an issue while building audience segments in RTCDP using a lookup schema. Here's the context:

 

Setup
I have two schemas configured:

  1. Schema #1: Event Class Schema
    • Event Type
    • Coupon Id
    • Coupon Master Id
  2. Schema #2: Custom Coupon Master Class
    • Coupon Master Id (Primary ID)
    • Coupon Name
    • Coupon Category

Issue
When creating a segment to target profiles who have used a specific coupon, I get the following results:

  • Segmentation Rule: Event Type = "Voucher Used" AND Coupon Name = "Free Coffee Voucher"
    Result: 0 profiles returned.

  • Segmentation Rule: Event Type = "Voucher Used" AND Coupon Master Id = "RM001"
    Result: Expected profile count returned.

  • Segmentation Rule: Coupon Name = "Free Coffee Voucher"
    Result: Expected profile count returned.

Question
Can anyone share insights on how to properly use the Coupon Name attribute from the Custom Coupon Master Class in segmentation?

 

Any advice, examples, or documentation references would be greatly appreciated. Thanks for your help!

 

Regards,

Zac

Best answer by Asheesh_Pandey

@zacharyta1 In Adobe Experience Platform, lookup schema attributes (like Coupon Name in your case) are not automatically available for event-based segmentation. You should ensure

  • Make sure the dataset is enabled for profile.
  • The join key (Coupon Master Id) is mapped as an identity in both schemas and shares the same namespace.
  • Ensure your active merge policy includes both the event dataset and lookup dataset.
  • Test with Query Service
    • Example Query Service test:
SELECT eventType, couponMasterId, couponName FROM your_event_dataset WHERE eventType = 'Voucher Used'
  • If couponName returns null, the join isn’t happening yet.
  • After enrichment, try rebuild the Segment

Ref: https://experienceleague.adobe.com/en/docs/platform-learn/tutorials/schemas/configure-relationships-between-schemas

2 replies

Asheesh_Pandey
Community Advisor
Asheesh_PandeyCommunity AdvisorAccepted solution
Community Advisor
August 15, 2025

@zacharyta1 In Adobe Experience Platform, lookup schema attributes (like Coupon Name in your case) are not automatically available for event-based segmentation. You should ensure

  • Make sure the dataset is enabled for profile.
  • The join key (Coupon Master Id) is mapped as an identity in both schemas and shares the same namespace.
  • Ensure your active merge policy includes both the event dataset and lookup dataset.
  • Test with Query Service
    • Example Query Service test:
SELECT eventType, couponMasterId, couponName FROM your_event_dataset WHERE eventType = 'Voucher Used'
  • If couponName returns null, the join isn’t happening yet.
  • After enrichment, try rebuild the Segment

Ref: https://experienceleague.adobe.com/en/docs/platform-learn/tutorials/schemas/configure-relationships-between-schemas

- Asheesh
    Michael_Soprano
    Michael_Soprano
    Level 10
    August 26, 2025

    Ensure your active merge policy includes both the event dataset and lookup dataset.

    Lookup dataset should not be enabled for Profile therefore not visible in Merge Policy creation?

    K
    Adobe Employee
    KevinFosterDXAdobe Employee
    Adobe Employee
    August 26, 2025

    I'm going to assume that you are using the all-datasets, timestamp-based merge policy.

     

    If you define a relationship between the event schema and your look up schema for that Coupon Master ID, and you've marked both schemas and their corresponding datasets for Profile before ingesting data, then the look up should work for batch audiences.

     

    Note that this functionality is not available in streaming nor edge audiences, only batch.

     

    The AI Assistant gives a good overview of this process when asked
    "how do I define a relationship between schemas?".

    Terms & ConditionsAccessibility statement

    Loading footer...