Data integration from two schemas in one email content

[ShivikaBa1]

I have an AJO journey use case where i need to send an email to a customer based on number of products they have shown in which came back in stock (max. 5 products). I have two different schemas A and B. In schema A, i have an attribute called sku (String datatype and an array). Schema A is Event schema and has email id as primary identity. In schema B, I have an attribute called product_number (primary identity) which is same as SKU, but the only difference is sku holds product numbers of the products that a particular user has shown interest in and are now back in stock, whereas product_number is a string datatype(not an array) and holds product numbers of all the products. Schema B is a lookup custom class schema.

In email, i need to call back in stock block (already have HTML code for it). An email can have maximum of 5 back in stock blocks. If a person shows interest in 1 product, 1 back in stock block will be present, if he shows interest in 2 products, 2 back in stock blocks will be present. How can I map SKU from schema A to product_number from Schema B. I need to search SKU in product_number and fetch product_image_URL from schema B in email editor. Can I do that without making a derived dataset with calculated attribute or making any changes in the existing schema? If not, what is the best practice to have least CDP modifications.

Thanks!

[Abie]

Hi @ShivikaBa1 ,

I think this post might help you-

https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/possible-to-access-look...

Thanks!

[Mayank_Gandhi]

@ShivikaBa1 

You cannot do this purely with schema A (event) and schema B (lookup class) as currently modeled and still keep everything inside the email template. You will need either:

1. A proper relationship + dataset lookup pattern (recommended, minimal change), or
2. To denormalize product attributes into the event itself (most robust, especially at scale).
   
   
   

   AJO supports relationships from an Experience Event to a lookup table using:

   • A simple attribute (string → lookup key), or
   • An array of IDs (array → lookup key array) for conditions, custom actions _and message personalization.

   See Personalization – Arrays and linked tables for this pattern, especially the “array of IDs” from event to product lookup table.[^arrays]

   Also, AJO has dataset lookup personalization ({{datasetLookup …}}) which:

   • Looks up into a record (non‑profile) dataset enabled for Entity Lookup Service,
   • Accepts a single key or a field value (including event fields) as the lookup key, and
   • Is available in email templates.[^datasetlookup]

   You do not need to build a computed attribute or heavy CDP changes if you design the relationship and lookup correctly.