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?
