Difference between revisions of "ATC/Current/AdminGuide/Best practices"
From Genesys Documentation
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
DannaShirley (talk | contribs) (Published) |
||
| Line 5: | Line 5: | ||
|Context=Improve how you build outcomes by reviewing best practices. | |Context=Improve how you build outcomes by reviewing best practices. | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage-cloud | + | |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 customer's behavior must exactly match how you define the segments for the action map. Keep the following points in mind: | |
| − | |||
| − | |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 users | + | * The more conditions you define, the fewer number of users 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 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
}} | }} | ||
Revision as of 14:42, September 10, 2020
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Improve how you build outcomes by reviewing best practices.
Best practices
Genesys Predictive Engagement tracks activity on your website at a detailed level. To trigger a specific action map, the customer's behavior must exactly match how you define the segments for the action map. Keep the following points in mind:
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 users match the segment.
- Conditions are not shared across segments and outcomes.
Comments or questions about this documentation? Contact us for support!