2.1 Audience-Based Entry with Read Audience & Audience Qualification
Key Takeaways
Audience Qualification reacts to membership changes and is appropriate when qualifying or exiting an audience should start an individual journey.
Read Audience imports members at a scheduled time or recurrence and is the standard entry for batch audience execution.
Incremental Read Audience first admits all eligible members and later admits only newly qualified members within the documented lookback behavior.
Trigger after batch audience evaluation improves coordination between a batch audience refresh and the journey read.
Streaming, batch, and externally sourced audiences have different latency and incremental-entry characteristics.
2.1 Audience-Based Entry with Read Audience and Audience Qualification
Audience entry is not one generic mechanism. The exam expects you to choose between Audience Qualification, which reacts to a membership transition, and Read Audience, which imports an audience on a schedule. The audience evaluation method and source determine how quickly membership can change; the journey activity determines how entry occurs.
Audience Qualification
Use Audience Qualification when an individual should enter because their membership changes. Configure an AEP audience and choose the relevant behavior, such as qualification or exit. The entry is individual: each qualifying membership event can start a journey execution, subject to journey reentrance controls and the selected identity namespace.
This pattern is well suited to a streaming audience whose supported rules are evaluated as qualifying data arrives. “Streaming” means ongoing evaluation, but it is safer to describe the result as near real time than to promise an exact sub-second latency. Ingestion, Profile processing, rule eligibility, and journey processing all contribute.
Examples include:
- a person crosses the threshold for a high-value audience;
- a customer enters an abandonment audience after supported streaming signals;
- a member exits a risk audience and should receive a recovery message.
Audience Qualification is not a scheduled bulk read. It also cannot be combined with the Business Event entry pattern in the same journey.
Read Audience
Use Read Audience when the journey should admit the members of an existing audience at a defined time. The activity can run once or according to a recurrence. It is appropriate for daily lifecycle programs, recurring reminders, scheduled audiences, uploaded lists, and other bulk-entry cases.
The practitioner configures:
- the audience;
- the identity namespace used by the journey;
- the schedule and time zone;
- whether eligible incremental behavior should be used;
- throughput and journey-level reentrance implications.
Read Audience exports membership, so entry has processing time and throughput considerations. A schedule should leave enough time after upstream ingestion and audience evaluation. If the read occurs before a batch audience completes, the journey can consume older membership.
Coordinate with batch evaluation
For a batch audience, enable Trigger after batch audience evaluation when the goal is to start the read after the daily segmentation job completes. The system then coordinates the journey trigger with that evaluation rather than relying solely on a guessed clock time. Adobe still recommends considering a buffer because audience evaluation and export are separate processing stages.
If that feature is not applicable, schedule with explicit knowledge of the upstream batch window. “Run at midnight because the file arrives around midnight” is not a robust dependency.
Incremental Read Audience
Incremental read changes which members a recurring execution admits:
- The first execution reads all current qualified members.
- Later executions focus on people newly qualified since the relevant prior evaluation window.
- The normal lookback is based on the last audience evaluation, with a maximum 24-hour lookback.
- When Trigger after batch audience evaluation is used, coordination follows the completed batch evaluation.
Incremental behavior is intended for audiences whose membership changes through supported AEP evaluation. Externally generated or uploaded audiences do not gain true incremental qualification semantics merely because the journey recurrence is enabled. For such sources, validate the documented source behavior and use the appropriate full-read or file orchestration design.
Identity and readiness checks
The audience can contain identities that the journey cannot use. Confirm that the chosen namespace exists in membership and matches channel needs. Email delivery, for example, requires an address available to the channel configuration, even if the journey identity is a CRM ID.
Before activating:
- preview or estimate audience membership;
- verify the latest evaluation completed;
- inspect representative profiles for membership and contactability;
- confirm the namespace chosen on the journey;
- verify consent and suppression;
- check that the expected volume fits entry and action throughput;
- make sure recurrence and reentrance will not create duplicates.
Troubleshooting
If no one enters, work in order. Confirm that the audience has members, that its evaluation completed, that the journey schedule actually fired, and that identities are present in the selected namespace. Then inspect journey errors and discards. If fewer people enter than expected, check incremental logic, reentrance, caps, consent, and profiles already active in the journey.
A “membership count” is not the same as “deliverable recipients.” Audience membership can include profiles lacking a channel address, opted out, suppressed, blocked by governance, capped, or already active.
Tip
Translate the scenario verb: becomes a member suggests Audience Qualification; read everyone at a scheduled time suggests Read Audience.
A practitioner wants profiles to enter individually when they newly qualify for a supported streaming audience. Which entry is appropriate?
Read Audience scheduled monthly
Audience Qualification
Business Event
A fixed Wait
Why use Trigger after batch audience evaluation with a Read Audience journey?
To turn every batch audience into an edge audience
To bypass identity namespaces
To coordinate the journey read with completion of the batch segmentation job
To send messages before membership is calculated
Which statement about incremental Read Audience is most accurate?
Every recurrence always reads every current member.
It dynamically converts any uploaded CSV into streaming segmentation.
The first run reads nobody and later runs read all members.
The first run reads current members; later runs target newly qualified members under supported evaluation and lookback behavior.
Sections you finish are checked off in the contents.