Difference between revisions of "ATC/Current/AdminGuide/Best practices"
From Genesys Documentation
m (Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2") |
(Published) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
|Standalone=No | |Standalone=No | ||
|DisplayName=Best practices for segments | |DisplayName=Best practices for segments | ||
| − | |TocName= | + | |TocName=Segment best practices |
| − | |Context= | + | |Context=Learn about best practices for improving how you create outcomes. |
| + | |Dimension=Segments | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage- | + | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud |
| − | |||
|Section={{Section | |Section={{Section | ||
|sectionHeading=Best practices | |sectionHeading=Best practices | ||
| − | |||
|alignment=Vertical | |alignment=Vertical | ||
| − | + | |structuredtext={{MINTYDOCSPRODUCT}} tracks activity on your website at a detailed level. To trigger a specific action map, the visitor's behavior must match exactly to the segments defined for the action map. | |
| − | |||
| − | |structuredtext={{MINTYDOCSPRODUCT}} tracks activity on your website at a | ||
{{NoteFormat| | {{NoteFormat| | ||
* Create segment-based conditions with a specific action map in mind: group them logically and define them in the correct sequence. | * Create segment-based conditions with a specific action map in mind: group them logically and define them in the correct sequence. | ||
| − | * | + | * To define a segment, you must specify at least one condition. |
* You can use a combination of segment-based conditions and outcome-based conditions. | * You can use a combination of segment-based conditions and outcome-based conditions. | ||
| − | * The more conditions you define, the fewer number of | + | * The more conditions you define, the fewer number of visitors match the segment. |
* Conditions are not shared across segments and outcomes. | * Conditions are not shared across segments and outcomes. | ||
|1}} | |1}} | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
}} | }} | ||
Latest revision as of 18:33, May 18, 2021
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Learn about best practices for improving how you create outcomes.
Best practices
Genesys Predictive Engagement tracks activity on your website at a detailed level. To trigger a specific action map, the visitor's behavior must match exactly to the segments defined for the action map.
Important
- Create segment-based conditions with a specific action map in mind: group them logically and define them in the correct sequence.
- To define a segment, you must specify at least one condition.
- You can use a combination of segment-based conditions and outcome-based conditions.
- The more conditions you define, the fewer number of visitors match the segment.
- Conditions are not shared across segments and outcomes.
Comments or questions about this documentation? Contact us for support!