Difference between revisions of "ATC/Current/AdminGuide/About segments"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2")
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
Line 6: Line 6:
 
|Dimension=
 
|Dimension=
 
|UseCase=
 
|UseCase=
|Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud
+
|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
 
|ComingSoon=No
 
|ComingSoon=No
 
|Context=Learn how to identify (segment) users based on their shared characteristics. Later, you design {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps|display text=action maps}} to engage specific segments of users and then {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Visitor_Activity|anchor=FilterSegmentsOutcomes|display text=filter by segments }} to evaluate how well you are engaging them.
 
|Context=Learn how to identify (segment) users based on their shared characteristics. Later, you design {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps|display text=action maps}} to engage specific segments of users and then {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Visitor_Activity|anchor=FilterSegmentsOutcomes|display text=filter by segments }} to evaluate how well you are engaging them.

Revision as of 02:31, July 25, 2020

Learn how to identify (segment) users based on their shared characteristics. Later, you design action maps to engage specific segments of users and then filter by segments to evaluate how well you are engaging them.


Best practices and examples

Segments

Build and maintain segments. Determine when segments are available for use in action maps and reports, and when agents can see them in the Journey gadget.

Attributes and operators

Conditions are the criteria by which Genesys Predictive Engagement assigns users to segments. Every condition must have an operator.

Comments or questions about this documentation? Contact us for support!