DocumentationJourney Optimizer B2BJourney Optimizer B2B Edition Documentation

Listen for an event

Last update: June 13, 2026

CREATED FOR:

  • Intermediate
  • User

To move the audience forward to the next step in your journey when an event occurs, add the Listen for an event node. Depending on the journey type, you can use this node to trigger the next node in the journey according to people or account events.

Account journeys account-journeys

NOTE
For an account journey, you cannot add the Listen for an event node type on a split path by people.

  1. Open the account journey canvas.

  2. Click the plus ( + ) icon on a path and choose Listen for an event.

    Add journey node to an account journey - Listen for an event {width="400"}

  3. In the node properties on the right, use the Event type selector to choose between Accounts and People.

  4. Select an event from the list.

    • For the People event type, choose the people event that you want to use for the trigger.

      Journey node - listen for events on people {width="500" modal="regular"}

    • For the Accounts event type, choose the account event that you want to use for the trigger.

      Journey node - listen for events on account {width="500" modal="regular"}

  5. Click Edit event and define details for the event.

    Depending on the selected event type and event, define the event matching criteria.

    You can also include filters for the event.

  6. Click Done.

    The event and filter definitions are displayed in the node and in the node properties.

    Account journey node - Listen to events - Event and filters {width="500"}

People events for account journeys people-events

In an account journey, you can listen for an event based on people when you want to move the account forward in the journey according to events triggered by people activity. You can also filter events according to event history and people attributes.

TIP
Experience events can occur before people enter the journey (such as a prior email click or web interaction). To route people based on these events, use the Event history filter in a Split paths by people node.

Journey Optimizer B2B events events-account-people

Event
Constraints
Assigned to Buying Group

Solution interest (required)

Additional constraints (optional):

  • Role

  • Date of activity

Timeout (optional)

Person profile changes
Attribute (required)
Date of activity (optional)
New value (optional)
Previous value (optional)
Reason (optional)
Source (optional)
Removed from Buying Group
Solution interest (required)
Date of activity (optional)
Timeout (optional)

  1. Set the required value to match for the event.

    If needed, set the operator for the evaluation.

  2. For each optional constraint that you want to include for event match, click Add constraint and select a constraint in the list.

    Edit event dialog for a Journey Optimizer B2B people event in an account journey {width="700" modal="regular"}

  3. (Optional) Select the Filters tab to add filters for the event.

  4. Click Done.

Experience Events experience-events-account-people

PREREQUISITES
Administrators configure Adobe Experience Platform (AEP) Experience Events, which enable marketers to create account and person journeys that react to the events in near real-time.
To make Experience Events available for journeys, a product administrator must first add the event types and fields of interest in Journey Optimizer B2B Edition.

  1. Click Add constraint and choose the field that you want to use for the constraint.

    The available constraints are defined as managed fields for the event configuration.

  2. Complete the condition for the constraint.

    You can use the default is operator to match one or more field values. Or you can use the is not operator to match on all values with the exclusion of one or more specified values.

    Edit event dialog for an Experience Event in an account journey {width="700" modal="regular"}

  3. (Optional) Select the Filters tab to add filters for the event.

  4. Click Done.

Account events account-events

In an account journey, you can listen for an event based on the account when you want to move the account forward in the journey according to events triggered by account activity.

Event
Constraints
Account had interesting moment

Type (Email, Milestone, or Web)
Additional constraints (optional):

  • Description

  • Source

  • Date of activity

Timeout (optional)

Change in Account Data Value

Attribute
Additional constraints (optional):

  • New value

  • Previous value

  • Date of activity

Timeout (optional)

Change in Buying Group Stage

Solution interest
Additional constraints (optional):

  • New stage

  • Previous stage

  • Date of activity

Timeout (optional)

Change in Buying Group Status

Solution interest
Additional constraints (optional):

  • New status

  • Previous status

  • Date of activity

Timeout (optional)

Change in Completeness Score

Solution interest
Additional constraints (optional):

  • New score

  • Previous score

  • Date of activity

Timeout (optional)

Change in Engagement Score

Solution interest
Additional constraints (optional):

  • New score

  • Previous score

  • Date of activity

Timeout (optional)

  1. Set the required constraint to match for the event.

  2. For each optional constraint that you want to include for event match, click Add constraint and select the field.

    Account journey - Listen for an account event {width="700" modal="regular"}

    Set the operator and value for the evaluation.

  3. Click Done.

Person journeys person-journeys

  1. Open the person journey canvas.

  2. Click the plus ( + ) icon on a path and choose Listen for an event.

    Add journey node to a person journey - Listen for an event {width="350"}

  3. In the node properties on the right, click Add event criteria.

    Journey node - Listen to events properties - add event criteria {width="450"}

  4. Add an event and set the constraints that you want to match for the trigger.

    You can use Experience Events and Person profile changes to define the event trigger.

    Drag and drop the event trigger into the builder space and set the definition. Click Add constraint for each constraint that you want to use to refine the event match.

    You can add multiple events to match. The first qualifying event advances the person profile forward in the journey.

  5. (Optional) Select the Filters tab to add filters for the event.

  6. Click Done.

    The event and filter definitions are displayed in the node and in the node properties.

    Journey node - Listen to events - Event and filters {width="450"}

Experience Events for person journeys experience-events-person

PREREQUISITES
Administrators configure Adobe Experience Platform (AEP) Experience Events, which enable marketers to create account and person journeys that react to the events in near real-time.
To make Experience Events available for journeys, a product administrator must first add the event types and fields of interest in Journey Optimizer B2B Edition.

You can use Experience Events to trigger the node in person journeys in the Edit event dialog.

  1. Expand Sapphire AEP events in the Triggers list on the left.

  2. Drag and drop the Experience Event into the event matching builder space.

    You can use the Search field to filter for a keyword in the event name, such as email.

  3. Click Add constraint and choose the field that you want to use to refine the event match.

    The available constraints are defined as managed fields for the event configuration.

    Edit event dialog for an Experience Event in a person journey {width="700" modal="regular"}

  4. Set the operator and values to match for the event field.

  5. (Optional) Add another Experience event or a person profile change.

    When you add multiple events to match. The first qualifying event advances the person profile forward in the journey.

  6. (Optional) Select the Filters tab to add filters for the event.

  7. Click Done.

Person profile changes person-profile-changes

You can use a change in B2B person profile attributes to trigger the node in person journeys in the Edit event dialog.

  1. Drag and drop Person profile changes from the Triggers list into the event matching builder space.

  2. Click Add constraint and select the attribute change that you want to use for the event trigger.

    Set the field value according to the change that you want to match.

    Person journey - Listen for a person profile change event {width="700" modal="regular"}

  3. (Optional) Add another Person profile change attribute that you want to use as an event trigger, or an Experience Event.

    When you add multiple events to match. The first qualifying event advances the person profile forward in the journey.

  4. (Optional) Select the Filters tab to add filters for the event.

  5. Click Done.

Filters for events filters-people-event

When you define a people event in an account journey or an event in a person journey, you can include filtering to limit matching event triggers based on various criteria:

Filters
Description
Event history
Experience events configured by an administrator. See Select Experience Events and fields.
Person Attributes

Attributes from the B2B person profile, including:

  • City

  • Country

  • Date of birth

  • Email address

  • Email invalid

  • Email suspended

  • First name

  • Inferred state region

  • Job title

  • Last name

  • Mobile phone number

  • Person engagement score

  • Phone number

  • Postal code

  • State

  • Unsubscribed

  • Unsubscribed reason

Person attributes
(Person journeys only) Attribute value
Special filters > Member of Buying Group

The person is or is not a buying group member evaluated against one or more of the following criteria:

  • Solution Interest

  • Buying Group status

  • Completeness Score

  • Engagement Score

  • Is Removed

  • Role

  1. After you define the event trigger, select the Filters tab in the Edit event dialog.

    Listen for Event node by people - Select Filters tab for editing the event {width="700" modal="regular"}

  2. To filter matches for the event, add one or more filter criteria.

    • Drag and drop any of the filters from the left navigation and complete the match definition.

      note
      NOTE
      If you have custom person fields defined in the account audience schema in Experience Platform, these fields are also available under Attributes to use as person attributes in filters.

    • Refine your filtering by applying the Filter logic at the top. You can choose to match all filters or any filter.

      Person filters used in an event definition {width="600" modal="regular"}

  3. When the event and filter definitions are complete, click Done.

Add a timeout to an event node timeouts

If needed, define the amount of time the journey waits for the event. The journey ends after a timeout unless you define a timeout path, where you can add other nodes.

Enable the Timeout option in the node properties to specify a timeout for the Listen for event node.

  1. With the options enabled, choose the Type and specify the parameters for the timeout:

    • Duration - Use this type to specify a time period for the event trigger. If the event does not trigger within that period, the person or account does not proceed in the journey.

      Select the duration for which the journey waits for an event to occur before it times out. Specify the number of minutes, hours, days, weeks, or months.

      Listen for event node - Timeout duration {width="500" modal="regular"}

      If you want the time period to end on a specific day of the week, enable the Must end on option. Any day is selected by default, with all of the days selected. Clear the checkbox and then select one or more days for an ending date. Then select the Time and Time zone.

      Listen for event node - Timeout duration - Must end on {width="300"}

    • Date - Use this type to set an expiration date for the node. If the event does not trigger by the specified date/time, the person or account does not proceed in the journey.

      Click the Calendar icon to set the date and time for the timeout.

      Listen for event node - Timeout date {width="500" modal="regular"}

  2. Define the timeout path.

    The Set timeout path option is selected by default. You can use this path to define what happens if the Listen for event node times out. You can add alternative actions and events that apply to person profiles when the event does not occur.

    Journey event node - set timeout path {width="600" modal="regular"}

    If you do not want to define the path, you can clear the Set timeout path check box.

recommendation-more-help
journey-optimizer-b2b-help-user