Listen for an event

Last update: March 7, 2025

Add the Listen for an event node to move your audience forward to the next step in the account journey when an event occurs.

Video Watch the overview video

NOTE
You cannot add this node type on split path by people.

Account events

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.

Events and constraints

EventConstraints
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)

Add an account event

  1. Navigate to the journey editor.

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

  3. In the node properties on the right, choose Accounts for the event type.

    Journey node - listen to events on account

  4. Select an event from the list.

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

People events

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.

Events and constraints

Input typeEventConstraints
Journey Optimizer B2BAssigned to Buying Group

Solution interest

Additional constraints (optional):

  • Role

  • Date of activity

Timeout (optional)

Clicks link in email

Email

Additional constraints (optional):

  • Link

  • Link ID

  • Is mobile device

  • Device

  • Platform

  • Browser

  • Is predictive content

  • Is bot activity

  • Bot activity pattern

  • Browser

  • Date of activity

  • Min. number of times

Timeout (optional)

Clicks link in SMS

Email

Additional constraints (optional):

  • Link

  • Device

  • Platform

  • Date of activity

  • Min. number of times

Timeout (optional)

Data value changes

Person attribute

Additional constraints (optional):

  • New value

  • Previous value

  • Reason

  • Source

  • Date of activity

  • Min. number of times

Timeout (optional)

Opens email

Email

Additional constraints (optional):

  • Link

  • Link ID

  • Is mobile device

  • Device

  • Platform

  • Browser

  • Is predictive content

  • Is bot activity

  • Bot activity pattern

  • Browser

  • Date of activity

  • Min. number of times

Timeout (optional)

Removed from Buying GroupSolution interest
Date of activity (optional)
Timeout (optional)
Score is changed

Score name

Additional constraints (optional):

  • Change

  • New score

  • Urgency

  • Priority

  • Relative score

  • Relative urgency

  • Date of activity

  • Min. number of times

Timeout (optional)

SMS Bounces

SMS message

Additional constraints (optional):

  • Date of activity

  • Min number of times

Timeout (optional)

Marketo EngageVisits Web Page

Web page
Select one or more Marketo Engage pages to match.

Additional constraints (optional):

  • Querystring

  • Client IP address

  • Referrer

  • User Agent

  • Search engine

  • Search query

  • Token

  • Browser

  • Platform

  • Device

  • Date of activity

Fills out form

Form
Select one or more Marketo Engage forms to match.

Additional constraints (optional):

  • Date of activity

  • Querystring

  • Client IP address

  • Referrer

  • User agent

  • Platform

  • Device

Timeout (optional)

Adobe Experience PlatformEvent definition

Event type

Additional constraints (optional):

  • Fields

Additional constraints (not supported):

  • Date of activity

  • Min. number of times

Timeout (optional)

Add a people event

  1. Navigate to the journey editor.

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

  3. In the node properties on the right, choose People for the event type.

    Journey node - listen to events on people

  4. Select an event from the list.

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

Listen for Marketo Engage event

If you have web pages created in your connected Marketo Engage instance, you can trigger an event based on a visit/no visit to Marketo Engage web pages, as well as Marketo Engage forms that were/were not filled.

  1. Select a Listen for an event node in the journey editor.

  2. In the node properties on the right, choose People for the event type.

  3. Click the arrow for the Select people event selector and scroll the menu to the Marketo Engage section.

  4. Select a Market Engage activity type:

    • Visits Web Page.
    • Fills Out Form

    Listen for an experience event

  5. Click Edit event and define one or more web pages to match and any additional constraints for the event.

    • (Required) In the Edit event dialog, define the Web page or Fills out form constraint. Use is (default) to match on one or more selected pages or forms. Use is not to match on all page visits/forms with the exclusion of one or more selected pages/forms. Or, use is any to match on any Marketo Engage web page visit or filled form.

    • (Optional) Click Add constraint and choose the field that you want to use for the constraint. Set the operator and the value for the field.

      Listen for an experience event

      You can repeat this action to include additional field constraints as needed.

    • When the constraints are defined, click Done.

  6. If needed, set the Timeout option to limit the time period to listen for the event (see Add a timeout to an event node).

  7. In the journey editor, add the next node to execute when the event occurs.

Listen for an Experience Event

Administrators can configure Adobe Experience Platform (AEP)-based event definitions, which enable Marketers to create account journeys that react to AEP Experience Events. Using AEP experience events in account journeys is a two-step process:

  1. Create and publish an AEP event definition.

  2. In an account journey, add a Listen for an event node, and select an Experience Platform event definition for a people-based event.

Video Watch the video overview

To include an Experience Event in your journey:

  1. Select a Listen for an event node in the journey editor.

  2. In the node properties on the right, choose People for the event type.

  3. Click the arrow for the Select people event selector and scroll the menu to the Adobe Experience Platform section.

    Listen for an experience event

  4. Select the event.

    The event type is displayed as empty in the node details.

    Edit the event

  5. Click Edit event and define the event types and any additional constraints for the event.

    • (Required) In the Edit event dialog, define the event type. You can use the default is operator to match on one or more selected event types. Or you can use the is not operator to match on all event types with the exclusion of one or more selected event types.

    • (Optional) Click Add constraint and choose the field that you want to use for the constraint. Set the operator and the value for the field.

      Listen for an experience event

      NOTE
      The constraints for date of activity and minimum number of times are not supported.

      You can repeat this action to include additional field constraints as needed.

    • When the constraints are defined, click Done.

  6. If needed, set the Timeout option to limit the time period to listen for the event (see Add a timeout to an event node).

  7. In the journey editor, add the next node to execute when the event occurs.

  8. Complete the remaining nodes for your journey and publish it.

    When the journey is live (published) and reaches the Listen for an event node, it begins listening for AEP Experience Events.