AJO Journey Orchestration – Excluding V1 Recipients from V2 Audience | Community
Skip to main content
Level 2
August 16, 2026
Question

AJO Journey Orchestration – Excluding V1 Recipients from V2 Audience

  • August 16, 2026
  • 2 replies
  • 12 views

I have the following scenario for AJO Journey Orchestration and would like to understand if there are any recommended approaches for handling this action.

I am aware of the Update Profile option , but I want to explore whether there are other approaches for this use case. This is for a Push Notification scenario where we are not using the AJO native channel; instead, we are using a Custom Action integrated with an external API.

Scenario:

  • Deploy V1 to Audience 1(batch campaign).
  • Stop V1 after it has completed.
  • Deploy V2 to Audience 2(batch campaign) and exclude all recipients who received V1.

What would be the best approach to identify and exclude the profiles who received V1 when V2 is deployed?

2 replies

SatheeskannaK
Community Advisor
Community Advisor
August 17, 2026

Hi ​@AkshithaPo I would suggest to follow this approach outlined here.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/journey-use-cases/custom-action-aep

  • Implement a secondary Custom Action: Since you are already integrating with an external API, configure an additional Custom Action using an HTTP API endpoint.
  • Ingest events into a Profile-Enabled Dataset: Use this new Custom Action to stream the V1 batch campaign execution events back into AEP into a profile-enabled dataset.
  • Build a Batch Audience: Create a batch audience leveraging the ingested event data tied to the Profile.
  • Suppress V1 profiles: Use this audience as an exclusion suppression list in your downstream journey/campaign to exclude profiles that already received the V1 message.
Thanks, Sathees
Level 2
August 17, 2026
 

Thanks for the sharing your thoughts ​@SatheeskannaK . Dataset uploads take about an hour before the records are available and Batch Audience evaluation takes 24 hours. As a result, we cannot use the batch audience for journey exclusion immediately without segment evaluation.

We need a solution that can enable us to trigger the V2 journey within a shorter timeframe.