Difference between revisions of "ATC/Current/AdminGuide/About outcomes"
From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
| Line 4: | Line 4: | ||
|Platform=PureEngage, PureConnect, PureCloud | |Platform=PureEngage, PureConnect, PureCloud | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Context= | + | |Context=Learn how to define the business goals you are trying to achieve so that you can evaluate users' progress and the effectiveness of your action maps. |
|TSSection={{TSSection | |TSSection={{TSSection | ||
|sectionheading=Best practices | |sectionheading=Best practices | ||
Revision as of 20:05, October 10, 2019
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Learn how to define the business goals you are trying to achieve so that you can evaluate users' progress and the effectiveness of your action maps.
Best practices
Improve how you build outcomes by reviewing best practices.
- [[ATC/Current/AdminGuide/Outcomes_best_practices|]]
Outcomes
Build and maintain outcomes.
Conditions and operators
Conditions are the criteria by which Genesys Predictive Engagement assigns users to segments. Every condition must have an operator.
- [[ATC/Current/AdminGuide/About_conditions|]]
- Operators
- Visitor attributes
- Campaign attributes
- Visitor journey attributes
- Custom attributes
Comments or questions about this documentation? Contact us for support!