Listen for an event
Add the Listen for an event node to move your audience forward to the next step in the account journey when an event occurs.
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
Type (Email, Milestone, or Web)
Additional constraints (optional):
-
Description
-
Source
-
Date of activity
Timeout (optional)
Attribute
Additional constraints (optional):
-
New value
-
Previous value
-
Date of activity
Timeout (optional)
Solution interest
Additional constraints (optional):
-
New stage
-
Previous stage
-
Date of activity
Timeout (optional)
Solution interest
Additional constraints (optional):
-
New status
-
Previous status
-
Date of activity
Timeout (optional)
Solution interest
Additional constraints (optional):
-
New score
-
Previous score
-
Date of activity
Timeout (optional)
Solution interest
Additional constraints (optional):
-
New score
-
Previous score
-
Date of activity
Timeout (optional)
Add an account event
-
Navigate to the journey map.
-
Click the plus ( + ) icon on a path and choose Listen for an event.
-
In the node properties on the right, choose Accounts for the event type.
-
Select an event from the list.
-
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. You can also filter events according to people attributes,
Events and constraints
Solution interest
Additional constraints (optional):
-
Role
-
Date of activity
Timeout (optional)
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)
Email
Additional constraints (optional):
-
Link
-
Device
-
Platform
-
Date of activity
-
Min. number of times
Timeout (optional)
Person attribute
Additional constraints (optional):
-
New value
-
Previous value
-
Reason
-
Source
-
Date of activity
-
Min. number of times
Timeout (optional)
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)
Date of activity (optional)
Timeout (optional)
Score name
Additional constraints (optional):
-
Change
-
New score
-
Urgency
-
Priority
-
Relative score
-
Relative urgency
-
Date of activity
-
Min. number of times
Timeout (optional)
SMS message
Additional constraints (optional):
-
Date of activity
-
Min number of times
Timeout (optional)
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
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)
Event type
Additional constraints (optional):
- Fields
Additional constraints (not supported):
-
Date of activity
-
Min. number of times
Timeout (optional)
People event filters
Email activities based on conditions that are evaluated using one or more selected email messages from earlier in the journey:
-
Clicked link in email
-
Opened email
-
Was delivered by email
-
Was sent email
SMS activities based on conditions that are evaluated using one or more selected SMS messages from earlier in the journey:
-
Clicked link in SMS
-
SMS Bounced
For a selected person attribute, a value change occurred. These change types include:
-
New value
-
Previous value
-
Reason
-
Source
-
Date of activity
-
Min. number of times
Interesting moment activity that is defined in the associated Marketo Engage instance. Constraints include:
-
Milestone
-
Email
-
Web
Web page activity that for one or more web pages managed by the associated Marketo Engage instance. Constraints include:
-
Web page (required)
-
Date of activity
-
Client IP address
-
Querystring
-
Referrer
-
User agent
-
Search engine
-
Search query
-
Personalized URL
-
Token
-
Browser
-
Platform
-
Device
-
Min. number of times
Attributes from the 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
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
-
Role
Add a people event
-
Navigate to the journey map.
-
Click the plus ( + ) icon on a path and choose Listen for an event.
-
In the node properties on the right, choose People for the event type.
-
Select an event from the list.
-
Click Edit event and define details for the event.
Listen for a Marketo Engage event
If you have web pages in your connected Marketo Engage instance, you can trigger an event based on a visit/no visit to these web pages, as well as Marketo Engage forms that were/were not filled.
-
Select a Listen for an event node in the journey map.
-
In the node properties on the right, choose People for the event type.
-
Click the arrow for the Select people event selector and scroll the menu to the Marketo Engage section.
-
Select a Market Engage activity type:
- Visits Web Page.
- Fills Out Form
-
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.
You can repeat this action to include additional field constraints as needed.
-
If needed, select the Filters tab to add filters for the event.
-
When the constraints and filters are defined, click Done.
-
-
If needed, set the Timeout option to limit the time period to listen for the event (see Add a timeout to an event node).
-
In the journey map, add the next node to execute when the event occurs.
Listen for an Experience Event
Administrators can configure ÃÛ¶¹ÊÓƵ 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:
-
In an account journey, add a Listen for an event node, and select an Experience Platform event definition for a people-based event.
To include an Experience Event in your journey:
-
Select a Listen for an event node in the journey map.
-
In the node properties on the right, choose People for the event type.
-
Click the arrow for the Select people event selector and scroll the menu to the ÃÛ¶¹ÊÓƵ Experience Platform section.
-
Select the event.
The event type is displayed as empty in the node details.
-
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.
note note 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.
-
If needed, select the Filters tab to add filters for the event.
-
When the constraints and filters are defined, click Done.
-
-
If needed, set the Timeout option to limit the time period to listen for the event (see Add a timeout to an event node).
-
In the journey map, add the next node to execute when the event occurs.
-
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.
Add filters to the people event
-
After you define the event, select the Filters tab in the Edit Event dialog.
-
Add one or more filters to target the people for the event.
-
Drag and drop any of the people filters from the left navigation and complete the match definition.
note 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. -
Fine tune your filtering by applying the Filter logic at the top. You choose to match all filters or any filter.
-
Click Done.
-
Add a timeout to an event node
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.
-
Select the duration for which the journey waits for an event to occur before it times out.
You can choose to end the path here or take a different course of action by setting another path.
-
To create a new path in the journey where you can add actions and events applicable to accounts when the event does not occur, select the Set timeout path check box.
