How to access event attribute in AJO personalization for the Read Audience or Qualification based journey ?

[Pradeep-Jaiswal]

Lets say if the events are batch based, and attribute required in the personalization is not part of profile schema, but event schema. And those attribute cant be added into profile as there could many such attribute. In such case if journey is built using read audience or qualification, then how to access attributes from event schema for those audience ? computed attribute is not an option here, bcz these cant be stored as profile attribute due to growing nature of event attribute list.

[SatheeskannaK · Accepted solution]

@Pradeep-Jaiswal

It's a known guardrail that experience event data cannot be used for read audience or audience qualification-based journeys. You might consider leveraging the AEP dataset for personalization instead.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalizatio...

Guradrail details:

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journe...

"Experience event field groups can not be used in journeys starting with a Read audience activity, an Audience qualification activity, or a business event activity."

[Pradeep-Jaiswal]

You might consider leveraging the AEP dataset for personalization instead.

What does this mean ? Eventually personalization is from the UPS, but not from dataLake. Am i mis-interpreting this statement ? I am not clear about this suggestion.

[SatheeskannaK]

@Pradeep-Jaiswal You don't necessarily need to keep all the personalization data in the profile store.Take a look at this documentation,

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journe...

[Pradeep-Jaiswal]

dataSetLook up is only relevant for meta data types of thing such as product rating, store inventory etc. It cant store the customer level information, as it would then fall under profile/event dataset.

[SatheeskannaK]

Yes. It's a guardrail and limitation when you're using personalization.