Stopping use of Batch Audiences in Journey Audience qualification | Community
Skip to main content
M
marc_stowe_za
Level 3
July 23, 2026
Solved

Stopping use of Batch Audiences in Journey Audience qualification

  • July 23, 2026
  • 2 replies
  • 46 views

Adobe will stop supporting Batch Audiences in the Audience qualification start to a journey, and wants either streaming audiences (so 24 hour period max) or use of the read audience start. That means a read audience can’t determine which are new profiles in the audience and just sends to everyone in the audience, which just doesn’t work, or we need to define the audience in batch with very defined limits and have exclusions of people who have been messaged, which is not practical.

 

Campaigns have an iterative type of read to process only new profiles entering the audience, journeys  dont. And campaigns arent an option for Whatsapp or logic around comms segmentation

 

Are there any work arounds that anyone has put in place to negate the potential issues here? I really feel this is a very ill advised change to something that was working very well.

    Best answer by Pulkit_Jain_

    ​@marc_stowe_za 

    Yes — many customers are raising the same concern. Adobe has acknowledged there are gaps for some use cases: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/aq-batch-audiences-migration 

    The cleanest workaround today is usually : move to Read Audience> enable Incremental Read(processes newly qualified profiles since the last run, gets you closest to the old AQ batch behavior)> add “Trigger after batch audience evaluation”> add suppression/state tracking for re-entry protection where needed

    The bigger issue is timing/snapshot freshness — Read Audience relies on audience export snapshots, so you can try:

    • scheduling segmentation earlier
    • adding buffer time before sends
    • using “Trigger after batch audience evaluation”

    2 replies

    M
    marc_stowe_zaAuthor
    Level 3
    July 23, 2026

    Quick note on this, i added the batch audience into a NEW streaming audience (it literally only has the batch audience in it) and AJO is happy with that. This is just a little silly

    Pulkit_Jain_
    Adobe Employee
    Pulkit_Jain_Adobe Employee
    Adobe Employee
    July 23, 2026

    yes, functionally it can bypass the validation, but architecturally it’s mostly a wrapper around the same batch behavior. AJO is validating the audience type, not whether the underlying qualification path is truly streaming.

    Pulkit_Jain_
    Adobe Employee
    Pulkit_Jain_Adobe EmployeeAccepted solution
    Adobe Employee
    July 23, 2026

    ​@marc_stowe_za 

    Yes — many customers are raising the same concern. Adobe has acknowledged there are gaps for some use cases: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/aq-batch-audiences-migration 

    The cleanest workaround today is usually : move to Read Audience> enable Incremental Read(processes newly qualified profiles since the last run, gets you closest to the old AQ batch behavior)> add “Trigger after batch audience evaluation”> add suppression/state tracking for re-entry protection where needed

    The bigger issue is timing/snapshot freshness — Read Audience relies on audience export snapshots, so you can try:

    • scheduling segmentation earlier
    • adding buffer time before sends
    • using “Trigger after batch audience evaluation”
      DavidKangni
      Community Advisor
      DavidKangniCommunity Advisor
      Community Advisor
      July 23, 2026

      Hi ​@Pulkit_Jain_ 

      Any alternatives on profiles who exited an audience? I was using audience qualification to do a different orchestration depending if the profiles enter or exit.

       

      Thanks,

      David

      David Kangni
      Pulkit_Jain_
      Adobe Employee
      Pulkit_Jain_Adobe Employee
      Adobe Employee
      July 24, 2026

      ​@DavidKangni Not really for batch audiences. Audience Qualification is still the only native way to handle audience enter/exit events. 

      Current workaround is to track previous audience membership yourself and generate a custom “exited audience” event/audience. If you can convert or wrap the audience as streaming, AQ still supports enter/exit orchestration normally.

      Terms & ConditionsAccessibility statement

      Loading footer...