Possible to access look up schemas data from AJO advanced editor?

[arpan-garg]

Hello,

I have a situation where all the information about products is stored in a lookup system in AEP (Adobe Experience Platform). Now, in my marketing campaign, I need to access these details before sending out an email. The product codes (SKU) are stored in an experience event schema, which is linked one-to-one with the product lookup schema.

In Adobe Journey Optimizer (AJO), I can easily access the product codes from the experience event. However, I'm not sure how to access the detailed product information by utilizing this relationship

@SatheeskannaK @Anuhya-Y 

Thanks,

Arpan

[akshaaga]

@arpan-garg ,

You can access detailed product information from the lookup schema by utilizing a combination of segments, audiences, and personalization in your marketing campaign.

Here's a step-by-step approach:

1. Create a Segment for Product Codes: In AJO, create a segment that includes the product codes (SKUs) you want to target. This segment will represent the group of profiles that match your product criteria.

2. Create an Audience for the Segment

3. Use Personalization in Your Email: In your marketing campaign, when designing your email, use personalization fields to insert the product information. For example, if you're sending product recommendations, set up personalization fields for product name, description, image, etc.

4. Use Real-Time Personalization: In the email, use real-time personalization to fetch the product details for each profile.

5. Content Blocks for Dynamic Data: You can also set up content blocks in your email templates to dynamically insert the product information for each recipient based on the product codes you've defined in your segment and audience.

[arpan-garg]

Hi @akshaaga - In regards to your 3rd point above, what do you mean by personalization fields to insert product data.For product data i have a separate look up schema and while creating my offer i just see attributes from individual profile schema, i don't see the attributes from lookup schema or experience event schema.

[Anuhya-Y · Accepted solution]

@arpan-garg 

I believe, look up schema fields are accessible in segment/Audience builder level but not at journey level in AJO.

However try using audience enrichment with product dataset https://experienceleague.adobe.com/docs/journey-optimizer/using/audiences-profiles-identities/audien..., these product fields would be available under audience enrichment at condition level of journey but not for personalization in email at this point of time.  

[arpan-garg]

Hi @Anuhya-Y  - I tried achieving the same, however i get the following error while creating a composition. 

"The selected attribute does not have any data. Please choose a different attribute."

I have double check the data and it is present in the selected attribute, but not sure why i keep on getting the above error.

Any pointers will be helpful.

[Anuhya-Y]

Is the join key (segmentid ) holding matching data in audience/segment  (high value customer) and dataset  (segment offers custom )?

make sure enrichment must be of record-type (as opposed to event-type), and they cannot be a system dataset, nor be marked for profile. They must be under 1GB.

[arpan-garg]

Yes, the segmentid is holding a match.

I am not sure whats the issue when I tried it after couple of hours it worked.

[Silvio6]

Hi! Maybe both of you can help me as I'm stucked in something like this and seems few people did this.

I want to use the fields from an enriched audience (companyName and companyCount) in AJO journey, but when I select the enriched field the advanced editor from journey looks like this:

#{ExperiencePlatform.ProfileFieldGroup.profile._spnam.audienceEnrichment.entry('put_a_key_here').audienceEnrichmentChildMap.entry('put_a_key_here').companyCount}

Do you know what 'put_a_key_here' means?

[arpan-garg]

Hi @Silvio6 - I see in your enrichment you selected company name as a primary identifier to enrich. I believe you should use companyName here as a put_a_key_here