Difference between revisions of "ATC/Current/AdminGuide/Trigger"
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
DannaShirley (talk | contribs) (Published) |
||
Line 5: | Line 5: | ||
|Context=Learn how to define the condition that causes {{MINTYDOCSPRODUCT}} to offer an action map to a particular user. | |Context=Learn how to define the condition that causes {{MINTYDOCSPRODUCT}} to offer an action map to a particular user. | ||
|ComingSoon=No | |ComingSoon=No | ||
− | |Platform=GenesysEngage-cloud | + | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud |
|Prereq='''Prerequisites''' | |Prereq='''Prerequisites''' | ||
Line 11: | Line 11: | ||
**'''Journey '''>''' Action Map '''>''' Add''', '''Delete''', '''Edit''', and '''View''' (to create action maps) | **'''Journey '''>''' Action Map '''>''' Add''', '''Delete''', '''Edit''', and '''View''' (to create action maps) | ||
**'''Journey '''>''' Action Target '''> '''View''' (to select a team to handle interactions from the action map) | **'''Journey '''>''' Action Target '''> '''View''' (to select a team to handle interactions from the action map) | ||
− | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=Deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website you want to track. This enables you to trigger the action map based on | + | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=Deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website you want to track. This enables you to trigger the action map based on event conditions. |
*To trigger an action map based on other events, use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about events you want to track. | *To trigger an action map based on other events, use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about events you want to track. | ||
*{{#mintydocs_link:topic=Segments|anchor=CreateSegment|link text=Create segments}}. | *{{#mintydocs_link:topic=Segments|anchor=CreateSegment|link text=Create segments}}. | ||
Line 19: | Line 19: | ||
|anchor=AboutTriggers | |anchor=AboutTriggers | ||
|alignment=Vertical | |alignment=Vertical | ||
− | |||
− | |||
|structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|anchor=Create|display text=create an action map}}, you specify the conditions, or triggers, that will make it {{GlossaryTooltip|term=qualified}} for a user. Possible triggers include: | |structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|anchor=Create|display text=create an action map}}, you specify the conditions, or triggers, that will make it {{GlossaryTooltip|term=qualified}} for a user. Possible triggers include: | ||
Line 26: | Line 24: | ||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#VisitorActivity|display text=When the user does something specific on your website}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#VisitorActivity|display text=When the user does something specific on your website}} | ||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Outcome_probabilities|anchor=TriggerOnlyOutcomeProbability|display text=The probability that the user will achieve a given business outcome}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Outcome_probabilities|anchor=TriggerOnlyOutcomeProbability|display text=The probability that the user will achieve a given business outcome}} | ||
− | + | ||
− | + | If multiple action maps are qualified, the priority of each action map determines which one is offered to the user. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Prioritize}} and {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_actions_and_action_maps}}. | |
− | + | ||
− | + | A customer cannot qualify for the same action map multiple times in a single {{GlossaryTooltip|term=session}}. | |
+ | |||
+ | <br /> | ||
|FAQHeading=Can a user qualify for an action map more than once within a single session? | |FAQHeading=Can a user qualify for an action map more than once within a single session? | ||
|Status=No | |Status=No | ||
Line 38: | Line 38: | ||
|Media=Image | |Media=Image | ||
|image=SegmentMatch2.gif | |image=SegmentMatch2.gif | ||
− | |structuredtext= | + | |structuredtext=If you select multiple segments, then the action map triggers when a customer matches any of them. |
+ | |||
+ | If you want to trigger an action map based one or more segments, you may also trigger it based on an outcome probability, but you cannot trigger it based on a user's activity. | ||
#Under '''Select trigger''', click '''Segment match'''. | #Under '''Select trigger''', click '''Segment match'''. | ||
Line 44: | Line 46: | ||
#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. | + | #Select as many segments as you need. |
#Click '''Done'''. | #Click '''Done'''. | ||
− | |||
− | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
Line 53: | Line 53: | ||
|anchor=VisitorActivity | |anchor=VisitorActivity | ||
|alignment=Vertical | |alignment=Vertical | ||
− | + | |structuredtext=To trigger an action map based on a user's activity, you can select one or more visitor journey attributes, which represent the specific events that occur. | |
− | |||
− | |structuredtext= | ||
− | |||
− | |||
− | |||
− | To trigger the action map based on | + | To do this, you must first {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website you want to track. This allows you to track standard {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_sessions|anchor=WebSessionEvents|display text=web events}}. To trigger an action map based on other events, use {{Link-SomewhereInThisVersion|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about events you want to track. |
+ | |||
+ | If you specify multiple visitor journey attributes, then the action map triggers when a customer matches '''all''' of them. {{MINTYDOCSPRODUCT}} evaluates the attributes in the order in which you define them. | ||
+ | |||
+ | If you want to trigger an action map based on a visitor journey attribute, you cannot trigger the action map based on a segment or an outcome probability. | ||
#Under '''Select trigger,''' click '''User activity'''. | #Under '''Select trigger,''' click '''User activity'''. | ||
Line 66: | Line 65: | ||
#Under '''Visitor journey''', Web is automatically selected as the session type. | #Under '''Visitor journey''', Web is automatically selected as the session type. | ||
#In the '''Event details''' list, select the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attribute}} you want, and then click '''add details''' to complete the attribute definition using one of the supported {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}. | #In the '''Event details''' list, select the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attribute}} you want, and then click '''add details''' to complete the attribute definition using one of the supported {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}. | ||
− | | | + | |Status=No |
− | | | + | }}{{Section |
+ | |sectionHeading=Trigger based on outcome probability | ||
+ | |anchor=OutcomeProbability | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=You can trigger an action map based on the probability that a user will achieve a given business outcome, based on the behavior of users who have previously achieved that outcome. | ||
+ | |||
+ | If you want to trigger an action map based on an outcome probability, you may also trigger it based on a user's segment/s, but you cannot trigger it based on a user's activity (event condition). | ||
+ | |||
+ | For information on how to define outcome probabilities, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes}}. | ||
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} |
Revision as of 10:45, September 8, 2020
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 Genesys Cloud:
- Journey > Action Map > Add, Delete, Edit, and View (to create action maps)
- Journey > Action Target > View (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 event conditions.
- 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 outcome
If 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|]].
A customer cannot qualify for the same action map multiple times in a singleNo results.
Trigger based on segment match
If you select multiple segments, then the action map triggers when a customer matches any of them.
If you want to trigger an action map based one or more segments, you may also trigger it based on an outcome probability, but you cannot trigger it based on a user's activity.
- 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.
- Click Done.
Trigger based on user activity
To trigger an action map based on a user's activity, you can select one or more visitor journey attributes, which represent the specific events that occur.
To do this, you must first deploy the Genesys Predictive Engagement tracking snippet on the website you want to track. This allows you to track standard web 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.
If you specify multiple visitor journey 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.
If you want to trigger an action map based on a visitor journey attribute, you cannot trigger the action map based on a segment or an outcome probability.
- 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.
Trigger based on outcome probability
You can trigger an action map based on the probability that a user will achieve a given business outcome, based on the behavior of users who have previously achieved that outcome.
If you want to trigger an action map based on an outcome probability, you may also trigger it based on a user's segment/s, but you cannot trigger it based on a user's activity (event condition).
For information on how to define outcome probabilities, see About outcome predictions and probabilities.