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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 4: Line 4:
 
|TocName=Trigger
 
|TocName=Trigger
 
|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.
|Dimension=
 
|UseCase=
 
 
|ComingSoon=No
 
|ComingSoon=No
 
|Platform=PureEngage, PureConnect, PureCloud
 
|Platform=PureEngage, PureConnect, PureCloud
|Role=
 
|Application=
 
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
Line 15: Line 11:
 
**'''Journey '''>''' Action Map '''>''' Add''', '''Delete''', '''Edit''', and '''View''' permissions (to create action maps)
 
**'''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)
 
**'''Journey '''>''' Action Target '''> '''View''' permission (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 pageview events.
 +
*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}}.
 
*{{#mintydocs_link:topic=Outcomes|anchor=CreateOutcome|link text=Create outcomes}}.
 
*{{#mintydocs_link:topic=Outcomes|anchor=CreateOutcome|link text=Create outcomes}}.
Line 54: Line 52:
 
|Media=
 
|Media=
 
|image=
 
|image=
|structuredtext=To trigger the action map based on what the user does:
+
|structuredtext={{NoteFormat|
 +
*In order to select events here, 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 enables you to trigger the action map based on pageview events.
 +
*To trigger an action map based on other events, use {{Link-SomewhereInThisVersion|manual=SDK|topic=Record|display text=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. {{MINTYDOCSPRODUCT}} evaluates the attributes in the order in which you define them. |1}}
 +
 
 +
To trigger the action map based on what the user does:
  
 
#Under '''Select trigger,''' click '''User activity'''.
 
#Under '''Select trigger,''' click '''User activity'''.
 
#Click '''Show details'''.
 
#Click '''Show details'''.
 
#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}}. {{NoteFormat|If you specify multiple 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. |1}}
+
#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}}.
 
|structuredtextwide=
 
|structuredtextwide=
 
|FAQHeading=
 
|FAQHeading=

Revision as of 13:48, May 27, 2020

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

Prerequisites

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:

Trigger based on segment match

To trigger the action map based on the segment that the customer belongs to:

  1. Under Select trigger, click Segment match.
  2. Click Show details.
  3. Click Select segments.
  4. Search for segments by name or description.
  5. Select as many segments as you need.
    Important
    If you select multiple segments, then the action map triggers only when a customer matches ALL of them.
  6. 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:

  1. Under Select trigger, click User activity.
  2. Click Show details.
  3. Under Visitor journey, Web is automatically selected as the session type.
  4. 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.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Trigger (2025-06-19 17:06:08)"
Comments or questions about this documentation? Contact us for support!