Difference between revisions of "ATC/Current/AdminGuide/Trigger"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 44: Line 44:
 
|structuredtext=If you haven't already, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website to track. This snippet 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 that you want to track.
 
|structuredtext=If you haven't already, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website to track. This snippet 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 that you want to track.
  
Select the session type and then select an event that triggers the action map. To trigger the action map when specific conditions are met, define one or more conditions (attributes). If you specify multiple conditions, the action map triggers when a visitor matches '''all''' the conditions. {{MINTYDOCSPRODUCT}} evaluates conditions in the order that you define them. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attributes}}. {{NoteFormat|If you trigger an action map based on visitor activity, you cannot also trigger it based on a segment or an outcome probability.|}}
+
Select the session type and then select an event that triggers the action map. To trigger the action map when specific conditions are met, define one or more conditions (attributes). If you specify multiple conditions, the action map triggers when a visitor matches '''all''' the conditions. {{MINTYDOCSPRODUCT}} evaluates conditions in the order that you define them. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attributes}}. {{NoteFormat|You can trigger an action map based on visitor activity '''and''' an outcome probability. However, you cannot trigger it based on visitor activity '''and''' visitor segment matches.|}}
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 52: Line 52:
 
|Media=Image
 
|Media=Image
 
|image=ConfigureOutcome.png
 
|image=ConfigureOutcome.png
|structuredtext=You can trigger an action map based on the probability of a visitor achieving a given business outcome, based on the behavior of visitors who achieved that outcome previously.{{NoteFormat|You can trigger an action map based on an outcome probability '''and''' a visitor's segment matches. However, you cannot trigger it based on an outcome probability '''and''' a visitor's activity.|}}For more information about how to define outcome probabilities, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes}}.
+
|structuredtext=You can trigger an action map based on the probability of a visitor achieving a given business outcome, based on the behavior of visitors who achieved that outcome previously.
 +
 
 +
For more information about how to define outcome probabilities, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes}}.
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 17:27, February 22, 2021

Learn how to define a condition that causes Genesys Predictive Engagement to offer an action map to a particular visitor.

Prerequisites

About triggering action maps

When you create an action map, you specify the conditions, or triggers that qualify it for a visitor. A visitor cannot qualify for the same action map multiple times in a single session. If multiple action maps qualify, the priority of each action map determines which one Genesys Predictive Engagement offers to the visitor. For more information, see Prioritize an action map.

You can trigger action maps based on:

Trigger based on segment match

Select one or more segments that trigger the action map when a visitor matches them. If you select multiple segments, the action map triggers when a visitor matches any of the segments.
Important
You can trigger an action map based on segment matches and an outcome probability. However, you cannot trigger it based on a visitor's segment matches and a visitor's activity.

Trigger based on visitor activity

If you haven't already, deploy the Genesys Predictive Engagement tracking snippet on the website to track. This snippet 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 that you want to track.

Select the session type and then select an event that triggers the action map. To trigger the action map when specific conditions are met, define one or more conditions (attributes). If you specify multiple conditions, the action map triggers when a visitor matches all the conditions. Genesys Predictive Engagement evaluates conditions in the order that you define them. For more information, see visitor journey attributes.
Important
You can trigger an action map based on visitor activity and an outcome probability. However, you cannot trigger it based on visitor activity and visitor segment matches.

Trigger based on outcome probability

You can trigger an action map based on the probability of a visitor achieving a given business outcome, based on the behavior of visitors who achieved that outcome previously.

For more information about how to define outcome probabilities, see About outcome predictions and probabilities.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Trigger (2025-06-19 16:57:29)"
Comments or questions about this documentation? Contact us for support!