Difference between revisions of "ATC/Current/AdminGuide/Trigger"
From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
Line 41: | Line 41: | ||
#Click '''Select segments.''' | #Click '''Select segments.''' | ||
#Search for segments by name or description. | #Search for segments by name or description. | ||
− | #Select as many segments as you need.{{NoteFormat|If you select multiple segments, then the action map triggers | + | #Select as many segments as you need.{{NoteFormat|If you select multiple segments, then the action map triggers when a customer matches any of them.|}} |
#Click '''Done'''. | #Click '''Done'''. | ||
|structuredtextwide= | |structuredtextwide= |
Revision as of 13:00, June 3, 2020
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Learn how to define the condition that causes Genesys Predictive Engagement to offer an action map to a particular user.
Prerequisites
- Configure the following permissions in PureCloud:
- Journey > Action Map > Add, Delete, Edit, and View permissions (to create action maps)
- Journey > Action Target > View permission (to select a team to handle interactions from the action map)
- Deploy the Genesys Predictive Engagement tracking snippet on the website you want to track. This enables you to trigger the action map based on pageview events.
- To trigger an action map based on other events, use ac('record') to send Genesys Predictive Engagement data about events you want to track.
- Create segments.
- Create outcomes.
About triggering action maps
When you create an action map, you specify the conditions, or triggers, that will make itNo results for a user. Possible triggers include:
- When Genesys Predictive Engagement matches a user to a segment
- When the user does something specific on your website
- The probability that the user will achieve a given business outcomeImportantIf multiple action maps are qualified, the priority of each action map determines which one is offered to the user. For more information, see Prioritize an action map and [[ATC/Current/AdminGuide/About_actions_and_action_maps|]].
Trigger based on segment match
To trigger the action map based on the segment that the customer belongs to:
- Under Select trigger, click Segment match.
- Click Show details.
- Click Select segments.
- Search for segments by name or description.
- Select as many segments as you need.ImportantIf you select multiple segments, then the action map triggers when a customer matches any of them.
- Click Done.
Trigger based on user activity
Important
- In order to select events here, you must first deploy the Genesys Predictive Engagement tracking snippet on the website you want to track. This enables you to trigger the action map based on pageview events.
- To trigger an action map based on other events, use ac('record') to send Altocloud data about events you want to track.
- If you specify multiple attributes, then the action map triggers when a customer matches all of them. Genesys Predictive Engagement evaluates the attributes in the order in which you define them.
To trigger the action map based on what the user does:
- Under Select trigger, click User activity.
- Click Show details.
- Under Visitor journey, Web is automatically selected as the session type.
- In the Event details list, select the visitor journey attribute you want, and then click add details to complete the attribute definition using one of the supported operators.
Comments or questions about this documentation? Contact us for support!