Audience in Condition Activities in Journeys - AJO | Community
Skip to main content
LuisCardenas
LuisCardenas
Level 2
November 7, 2025
Question

Audience in Condition Activities in Journeys - AJO

  • November 7, 2025
  • 1 reply
  • 151 views

Hi all!

 

I'm aware I can use audiences in condition activities inside journeys, but my question is:

 

If I use multiple audiences as part of the same condition node with 'OR', is the performance of the journey lowered? - currently we have a journey started by a unitary event and would like to take out profiles who don't match certain conditions.

 

Appreciate any help, thanks!

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
November 7, 2025

@luiscardenas

The expectation is that the journey's performance should be better, as checking audience membership for each profile should not be a lengthy process.

The primary concern, however, is not the runtime performance but rather data consistency and evaluation freshness. Specifically, if a journey is triggered by an event, and audience membership conditions are evaluated immediately following that event, it is crucial to ensure that the audience data has been updated appropriately to handle the inclusion or exclusion of the profile.

Thanks, Sathees
    LuisCardenas
    LuisCardenasAuthor
    Level 2
    November 11, 2025

    Thanks for the answer. How would you suggest to ensure that or tackle this scenario?

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity Advisor
    Community Advisor
    November 11, 2025

    @luiscardenas 

    • Global Exit Criteria: If the exit criteria apply to the entire journey, use the global exit criteria option. This allows you to remove profiles that no longer meet specific conditions, based on events or audience membership.
    • Streaming Audience Approach: Alternatively, you can incorporate the "don't match" criteria directly into a streaming audience. This audience can then be used within the journey conditions using an "OR" logical operator.
    Thanks, Sathees
    Terms & ConditionsAccessibility statement

    Loading footer...