Journey Optimizer journeys: event-triggered vs audience-based entry

Why this matters

Choosing the right entry type matters because mixing event and audience starts can lead to errors in targeting and campaign logic. If a journey starts with an event but is designed to serve a broad audience, it may miss the intent—delivering messages to individuals only when they take a specific action, like abandoning a cart. Conversely, using audience entry for a one-time event like a purchase could result in irrelevant messages sent to thousands of people who didn’t take the action.

Without clear entry type selection, teams risk rebuilding journeys multiple times, increasing errors and delays. Re-entrance settings and flow logic may not align with the original intent. This creates confusion, longer development cycles, and inconsistent user experiences. Starting with a clear entry—event for individual actions, Read Audience for scheduled reach—ensures accuracy, reduces rework, and supports better campaign performance.

The key ideas

A journey in Adobe Journey Optimizer starts with an entry point: either an event or an audience. An event-triggered journey begins when a specific action happens for one person—like an abandoned cart—so the journey runs individually for that person. This type of entry is ideal when you want to respond to a moment that matters to a single user.

A Read Audience journey, on the other hand, brings in many people at once from a defined group, such as subscribers on a mailing list. This is best for scheduled campaigns, like a monthly newsletter, where the goal is to reach a broad audience at the same time.

The choice between these entry types matters early on. If you start with an event, the journey responds to individual actions and is suited for real-time, reactive experiences. If you start with a Read Audience, the journey is designed for batched, time-based outreach. Once the entry type is chosen, you can add activities like wait or condition logic to control flow, and action activities to send messages. Re-entrance settings determine if a person can enter the journey again later. Choosing the right entry type from the start avoids the need to rebuild the journey later.

How to apply it

Start by deciding whether the journey should begin with a specific person’s action or a group of people. If the goal is to respond to a moment like an abandoned cart or a page view, use an event-triggered entry. This ensures the journey activates immediately when that action happens, delivering a personalized response to that individual.

If the journey is part of a recurring campaign—like a monthly newsletter or seasonal offer—use a Read Audience entry. This brings in a list of people at once, allowing for broad, scheduled messaging. The choice between event and audience entry sets the foundation for how the journey behaves.

After selecting the entry type, configure re-entrance settings to control whether a person can re-enter the journey. Add wait or condition activities to pause or branch the journey based on data, and include action activities to deliver messages like email or push notifications. Always choose the entry type first to avoid needing to rebuild the journey later. This keeps the flow logical and reduces errors during development.

Mistakes to avoid

• Starting a journey with the wrong entry type can lead to misaligned goals. Using an event entry for a scheduled campaign, like a monthly newsletter, may miss the intent to reach many people at once. Instead, use a Read Audience entry to include the entire audience at scale.

• Forgetting to set re-entrance rules can cause people to enter the journey repeatedly, leading to redundant actions or wasted resources. Always define re-entrance settings early—disable re-entry for event-triggered journeys to avoid looping, and enable it only if the journey is designed for repeat engagement. This ensures clarity and efficiency from the start.

Quick checklist

• Determine whether the journey should start with a specific person’s action (event) or a group of people (Read Audience).
• Choose event entry if the goal is to respond to a one-off action, like an abandoned cart or button click.
• Choose Read Audience entry if the goal is to reach a predefined group, such as subscribers or customers in a specific segment.
• Set re-entrance rules to decide if the same person can enter the journey again after completion.
• Identify whether the journey needs wait or condition activities to delay or branch based on user data.
• Confirm that action activities (like email or push) are properly assigned to the journey flow.
• Review the entry type early to avoid needing to rebuild the journey later.