Difference between revisions of "ATC/Current/AdminGuide/Outcomes"
From Genesys Documentation
m (1 revision imported) |
DannaShirley (talk | contribs) (Copied from Draft) |
||
| Line 8: | Line 8: | ||
|Type=Unstructured | |Type=Unstructured | ||
|freetext=Altocloud uses your outcomes to analyze which visitors achieve your business goals and to score future visitors as they make progress towards it. As visitors progress towards an outcome, you can track their progress and design engagements that will steer your visitors towards your goals. When you create an outcome, you select the persona attributes and journey patterns to which it applies. | |freetext=Altocloud uses your outcomes to analyze which visitors achieve your business goals and to score future visitors as they make progress towards it. As visitors progress towards an outcome, you can track their progress and design engagements that will steer your visitors towards your goals. When you create an outcome, you select the persona attributes and journey patterns to which it applies. | ||
| − | * [[#SegmentAttributes| | + | * [[#SegmentAttributes|Visitor attributes ]] are characteristics that all the visitors in the group share. Examples of visitor attributes are visitors who use Chrome and visitors from Canada. |
| − | * [[#JourneyPattern| | + | * [[#JourneyPattern|Visitor journeys ]] are actions on your website that all the visitors in the group have taken. Examples of visitor journeys are completing a form or going to a specific webpage. |
| − | You can specify any combination of | + | You can specify any combination of visitor attributes and visitor journeys for a segment. The more of these conditions you define, the more specific the segment, and the fewer number of visitors who belong to it. |
| + | |||
| + | You complete the same process of defining visitor attributes and visitor journeys when you create both segments and outcomes. However, visitor attributes and visitor journeys are different and are not shared across segments and outcomes. | ||
}}{{Section | }}{{Section | ||
|sectionHeading=View your outcomes | |sectionHeading=View your outcomes | ||
|Type=Structured | |Type=Structured | ||
|alignment=Horizontal | |alignment=Horizontal | ||
| − | |image= | + | |image=OutcomeView2.png |
|structuredtext=# Click '''Journey''' > '''Outcomes'''. | |structuredtext=# Click '''Journey''' > '''Outcomes'''. | ||
|fullwidth=No | |fullwidth=No | ||
| Line 24: | Line 26: | ||
|Type=Structured | |Type=Structured | ||
|alignment=Horizontal | |alignment=Horizontal | ||
| − | |image= | + | |image=OutcomeCreate3.png |
| − | |structuredtext=# Click '''Journey | + | |structuredtext=# Click '''Journey'''> '''Outcomes'''. |
# Click '''Create Outcome'''. | # Click '''Create Outcome'''. | ||
# Use a descriptive name. | # Use a descriptive name. | ||
# Define at least one of the following: | # Define at least one of the following: | ||
| − | #* [[#SegmentAttributes| | + | #* [[#SegmentAttributes|Visitor attribute]] |
| − | #* [[#JourneyPattern| | + | #* [[#JourneyPattern|Visitor journey]] |
| − | # | + | # Click '''Save and close'''. |
| − | {{NoteFormat|You can specify as many | + | {{NoteFormat|You can specify as many visitor attributes and visitor pattern conditions as you want. You must specify at least one.|1}} |
|fullwidth=No | |fullwidth=No | ||
}}{{Section | }}{{Section | ||
| − | |sectionHeading= | + | |sectionHeading=Visitor attributes |
|anchor=SegmentAttributes | |anchor=SegmentAttributes | ||
|Type=Structured | |Type=Structured | ||
|alignment=Horizontal | |alignment=Horizontal | ||
| − | |image= | + | |image=VisitorAttributes.png |
| − | |structuredtext= | + | |structuredtext=Visitor attributes identify visitors based on characteristics like location, browser, device type, and so on. |
{{NoteFormat|If you want to match based on a non-numeric criteria, such as the name of a browser, select the '''like''' or '''not like''' operator. |2}} | {{NoteFormat|If you want to match based on a non-numeric criteria, such as the name of a browser, select the '''like''' or '''not like''' operator. |2}} | ||
|fullwidth=No | |fullwidth=No | ||
}}{{Section | }}{{Section | ||
| − | |sectionHeading= | + | |sectionHeading=Visitor journeys |
|anchor=JourneyPattern | |anchor=JourneyPattern | ||
|Type=Structured | |Type=Structured | ||
|alignment=Horizontal | |alignment=Horizontal | ||
| − | |structuredtext= | + | |image=VisitorJourney.png |
| + | |structuredtext=A visitor journey identifies visitors based on their behavior on your site. For example a visitor journey might include all visitors who: | ||
* Viewed a specific page | * Viewed a specific page | ||
* Clicked a specific button | * Clicked a specific button | ||
* Submitted a form | * Submitted a form | ||
| − | {{NoteFormat|Track these actions as events in your code. To track a more complex journey | + | |
| + | A visitor journey can also reflect a negative event. For example a visitor journey might include all visitors who added a product to their shopping cart but did not complete the transaction. | ||
| + | |||
| + | {{NoteFormat|Track these actions as events in your code. To track a more complex visitor journey, add conditions. Genesys Altocloud evaluates all conditions in the visitor journey sequentially, in the order you define them. |1}} | ||
Set each condition to one of these matching options: | Set each condition to one of these matching options: | ||
| − | * '''Once''': The | + | * '''Once''': The segment matches when the condition is met. |
| − | * '''Never''': After the visitor leaves the site, the | + | * '''Never''': After the visitor leaves the site, the segment matches if this condition was not met during the visit. This applies to all segments that contain at least one '''Never''' condition. |
|fullwidth=No | |fullwidth=No | ||
}}{{Section | }}{{Section | ||
| − | |sectionHeading= | + | |sectionHeading=Deactivate an outcome |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|anchor=OutcomeDelete | |anchor=OutcomeDelete | ||
|Type=Structured | |Type=Structured | ||
|alignment=Horizontal | |alignment=Horizontal | ||
| − | |image= | + | |image=OutcomeDeactivate.png |
| − | |structuredtext= | + | |structuredtext=Deactivate an outcome when you no longer need it. |
| + | # Click '''Journey''' > '''Outcomes'''. | ||
| + | # Click the name of the outcome you want to deactivate. | ||
| + | # Click the '''Active''' toggle so it isgray. | ||
| + | # Click '''Submit'''. | ||
| + | |||
| + | {{NoteFormat|Do not delete outcomes.}} | ||
|fullwidth=No | |fullwidth=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 17:57, November 9, 2018
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Outcomes correspond to business goals that you want to monitor and achieve.
About outcomes
View your outcomes
- Click Journey > Outcomes.
Create an outcome
- Click Journey> Outcomes.
- Click Create Outcome.
- Use a descriptive name.
- Define at least one of the following:
- Click Save and close.
Important
You can specify as many visitor attributes and visitor pattern conditions as you want. You must specify at least one.Visitor attributes
Visitor attributes identify visitors based on characteristics like location, browser, device type, and so on.
Tip
If you want to match based on a non-numeric criteria, such as the name of a browser, select the like or not like operator. Visitor journeys
A visitor journey identifies visitors based on their behavior on your site. For example a visitor journey might include all visitors who:
- Viewed a specific page
- Clicked a specific button
- Submitted a form
A visitor journey can also reflect a negative event. For example a visitor journey might include all visitors who added a product to their shopping cart but did not complete the transaction.
Important
Track these actions as events in your code. To track a more complex visitor journey, add conditions. Genesys Altocloud evaluates all conditions in the visitor journey sequentially, in the order you define them. Set each condition to one of these matching options:
- Once: The segment matches when the condition is met.
- Never: After the visitor leaves the site, the segment matches if this condition was not met during the visit. This applies to all segments that contain at least one Never condition.
Deactivate an outcome
Deactivate an outcome when you no longer need it.
- Click Journey > Outcomes.
- Click the name of the outcome you want to deactivate.
- Click the Active toggle so it isgray.
- Click Submit.
Important
Do not delete outcomes.Comments or questions about this documentation? Contact us for support!