From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
|||
Line 8: | Line 8: | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=Best practices | |sectionHeading=Best practices | ||
− | | | + | |Standalone=No |
+ | |ComingSoon=No | ||
|alignment=Vertical | |alignment=Vertical | ||
− | |||
|structuredtext={{MINTYDOCSPRODUCT}} tracks activity on your website at a very detailed level. In order 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 very detailed level. In order 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: | ||
Revision as of 13:24, January 17, 2020
Difference between revisions of "ATC/Current/AdminGuide/Best practices"
Improve how you build outcomes by reviewing best practices.
Best practices
Genesys Predictive Engagement tracks activity on your website at a very detailed level. In order 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.
- In order 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 will be matched to the segment.
- Conditions are not shared across segments and outcomes.
Comments or questions about this documentation? Contact us for support!