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|anchor=Create|display text=create an action map}}, you specify the conditions, or triggers, that make it {{GlossaryTooltip|term=qualified}} for a visitor. Possible triggers include:
+
|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}}. 
  
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#SegmentMatch|display text=When {{MINTYDOCSPRODUCT}} matches a visitor to a segment}}
+
You can trigger action maps based on:
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#VisitorActivity|display text=When the visitor does something specific on your website}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Outcome_probabilities|anchor=TriggerOnlyOutcomeProbability|display text=The probability of the visitor achieving a given business outcome}}
 
  
If multiple action maps are qualified, the priority of each action map determines which one {{MintyDocsProduct}} offers to the visitor. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Prioritize}}.
+
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#SegmentMatch|display text=Segment matches}}
 
+
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger#VisitorActivity|display text=Visitor actions}}
A visitor cannot qualify for the same action map multiple times in a single {{GlossaryTooltip|term=session}}.
+
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Outcome_probabilities|anchor=TriggerOnlyOutcomeProbability|display text=Business outcome probability}}
 
|FAQHeading=Can a visitor qualify for an action map more than once within a single session?
 
|FAQHeading=Can a visitor qualify for an action map more than once within a single session?
 
|Status=No
 
|Status=No
Line 36: Line 34:
 
|Media=Image
 
|Media=Image
 
|image=SegmentMatch2.gif
 
|image=SegmentMatch2.gif
|structuredtext=If you select multiple segments, the action map triggers when a visitor matches any of them.
+
|structuredtext=If you select multiple segments, the action map triggers when a visitor matches any of the segments.{{NoteFormat|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.|}}<br />
 
 
You can trigger an action map based on one or more segments, and you can also trigger it based on an outcome probability. However, you cannot trigger it based on a visitor's activity.
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 44: Line 40:
 
|anchor=VisitorActivity
 
|anchor=VisitorActivity
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext=To trigger an action map based on a visitor's activity, you can select one or more visitor journey attributes, which represent the specific events that occur.
+
|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.
  
First {{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.
+
To trigger an action map based on a visitor's activity, select one or more {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attribute}}, which represent the specific events that occur. Then, complete the attribute definition using one of the supported {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}. If you specify multiple visitor journey attributes, the action map triggers when a visitor matches '''all''' the attributes. {{MINTYDOCSPRODUCT}} evaluates the attributes in the order that you define them. {{NoteFormat|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.|}}
 
 
If you specify multiple visitor journey attributes, the action map triggers when a visitor matches '''all''' the attributes. {{MINTYDOCSPRODUCT}} evaluates the attributes in the order that you define them.
 
 
 
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. Select the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AttributesJourney|display text=visitor journey attribute}} and then complete the attribute definition using one of the supported {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}.
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 58: Line 50:
 
|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.
 
|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.
  
To trigger an action map based on an outcome probability, you can also trigger it based on a visitor's segments, but you cannot trigger it based on a visitor's activity (event condition).
+
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.{{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}}.
 
 
For more information about how to define outcome probabilities, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes}}.
 
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 14:56, 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 make itNo results for a visitor. A visitor cannot qualify for the same action map multiple times in a singleNo results. 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:03)"
Comments or questions about this documentation? Contact us for support!