Audience Qualification and Merge Policies

[Silvio6]

Hi, I’ve created two streaming audiences: one using the Default Merge Policy and another with a custom Merge Policy we recently created.

I need a journey that listens for new entries into the audience associated with the custom Merge Policy (not the Default MP). To achieve this, I created a journey that starts with an Audience Qualification trigger using the audience linked to the new Merge Policy. However, AJO isn’t detecting any new entries for this audience.

As a test, I replicated the same journey but used an Audience Qualification trigger with the Default Merge Policy audience instead. This version works as expected and listens for new entries without issue.

Is there a known limitation or blocker related to using custom Merge Policies with Audience Qualification in AJO?

[Mohan_Dugganab · Accepted solution]

Kindly log a support ticket for this in case you don't see any errors in journey step events dataset 

[RavindranathSarma]

Adobe Journey Optimizer uses merge policies while retrieving profile data from Adobe Experience Platform. Depending on the journey type, different merge policies are used:

• In Read audience or audience qualification journeys: the merge policy from the audience is used
• In Unitary event journeys: the default merge policy is used
• In Business event journeys: the merge policy from the targeted audience in the following Read audience activity is used

Source: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journ...