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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 19: Line 19:
 
|anchor=AboutTriggers
 
|anchor=AboutTriggers
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=create an action map}}, you specify the conditions, or triggers, that make it {{GlossaryTooltip|term=qualified}} for a visitor. A visitor cannot qualify for the same action map multiple times in a single {{GlossaryTooltip|term=session}}. If multiple action maps qualify, the priority of each action map determines which one {{MintyDocsProduct}} offers to the visitor. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Prioritize}}.   
+
|structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=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 {{MintyDocsProduct}} offers to the visitor. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Prioritize}}.   
  
 
You can trigger action maps based on:  
 
You can trigger action maps based on:  

Revision as of 18:18, February 19, 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

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.

To trigger an action map based on a visitor's activity, select one or more visitor journey attribute, which represent the specific events that occur. Then, complete the attribute definition using one of the supported operators. If you specify multiple visitor journey attributes, the action map triggers when a visitor matches all the attributes. Genesys Predictive Engagement evaluates the attributes in the order that you define them.
Important
If you trigger an action map based on a visitor journey attribute, you cannot also trigger it based on a segment or an outcome probability.

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.

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.
Important
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 About outcome predictions and probabilities.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Trigger (2025-06-19 12:35:05)"
Comments or questions about this documentation? Contact us for support!