Difference between revisions of "ATC/Current/AdminGuide/Outcomes"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "|Type=Structured" to "|Type=Structured |gif=No")
(Published)
Line 3: Line 3:
 
|DisplayName=Outcomes
 
|DisplayName=Outcomes
 
|Platform=PureEngage, PureConnect, PureCloud
 
|Platform=PureEngage, PureConnect, PureCloud
−
|Dimension=Journey
 
 
|Context=Outcomes correspond to business goals that you want to monitor and achieve.
 
|Context=Outcomes correspond to business goals that you want to monitor and achieve.
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=About outcomes
 
|sectionHeading=About outcomes
 
|Type=Structured
 
|Type=Structured
 +
|alignment=Vertical
 
|gif=No
 
|gif=No
−
|alignment=Vertical
+
|structuredtext=In order for {{MINTYDOCSPRODUCT}} to assist your customers in achieving your business goals, you must first define each business goal as an {{GlossaryTooltip|term=outcome}}  in {{MINTYDOCSPRODUCT}}. Every night, {{MINTYDOCSPRODUCT}} analyzes the customer activity from that day. Based on this analysis, {{MINTYDOCSPRODUCT}} learns how to use your action maps to steer future customers towards your business outcomes.
−
|structuredtext={{MINTYDOCSPRODUCT}} 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.
 
−
 
 
  
 
{{NoteFormat|The more outcomes you create, the better {{MINTYDOCSPRODUCT}} will be able to predict future outcome scores. |2}}
 
{{NoteFormat|The more outcomes you create, the better {{MINTYDOCSPRODUCT}} will be able to predict future outcome scores. |2}}
−
|fullwidth=No
 
−
}}{{Section
 
−
|sectionHeading=How {{MINTYDOCSPRODUCT}} uses outcomes to calculate outcome scores
 
−
|Type=Structured
 
−
|gif=No
 
−
|anchor=CalculateOutcomeScores
 
−
|alignment=Vertical
 
−
|structuredtext=After you create an outcome, {{MINTYDOCSPRODUCT}} analyzes the activity of your future website visitors against it. Every night, {{MINTYDOCSPRODUCT}}'s machine learning updates the outcome probability algorithms based on the visitor activity of the previous day. The next day, {{MINTYDOCSPRODUCT}} analyzes visitor activity using the updated outcome probability algorithm. This results in improved outcome probability scores.
 
 
|fullwidth=No
 
|fullwidth=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=View your outcomes
 
|sectionHeading=View your outcomes
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=OutcomeView0131.png
 
|image=OutcomeView0131.png
 +
|gif=No
 
|structuredtext=# Click '''Journey''' > '''Outcomes'''.
 
|structuredtext=# Click '''Journey''' > '''Outcomes'''.
 
|fullwidth=No
 
|fullwidth=No
Line 34: Line 24:
 
|sectionHeading=Create an outcome
 
|sectionHeading=Create an outcome
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=CreateOutcome
 
|anchor=CreateOutcome
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=OutcomeCreate0131.png
 
|image=OutcomeCreate0131.png
 +
|gif=No
 
|structuredtext=# Click '''Journey'''> '''Outcomes'''.
 
|structuredtext=# Click '''Journey'''> '''Outcomes'''.
 
# Click '''Create Outcome'''.
 
# Click '''Create Outcome'''.
 
# Use a descriptive name.
 
# Use a descriptive name.
−
# Define at least one {{#mintydocs_link:manual=AdminGuide|topic=VisitorAttsJourney|link text=visitor attribute or visitor journey}}.
+
# Define at least one {{#mintydocs_link:manual=AdminGuide|topic=VisitorAttsJourney|link text=visitor or journey attribute}}.
 
# Click '''Save and close'''.
 
# Click '''Save and close'''.
 
{{NoteFormat|You can specify as many visitor attributes and visitor journey conditions as you want. You must specify at least one.|1}}
 
{{NoteFormat|You can specify as many visitor attributes and visitor journey conditions as you want. You must specify at least one.|1}}
Line 48: Line 38:
 
|sectionHeading=Deactivate an outcome
 
|sectionHeading=Deactivate an outcome
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=OutcomeDelete
 
|anchor=OutcomeDelete
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=OutcomeDeactivate0131.png
 
|image=OutcomeDeactivate0131.png
 +
|gif=No
 
|structuredtext=Deactivate an outcome when you no longer need it.
 
|structuredtext=Deactivate an outcome when you no longer need it.
 
# Click '''Journey''' > '''Outcomes'''.
 
# Click '''Journey''' > '''Outcomes'''.

Revision as of 10:37, March 22, 2019

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

Outcomes correspond to business goals that you want to monitor and achieve.

About outcomes

In order for Genesys Predictive Engagement to assist your customers in achieving your business goals, you must first define each business goal as anNo results in Genesys Predictive Engagement. Every night, Genesys Predictive Engagement analyzes the customer activity from that day. Based on this analysis, Genesys Predictive Engagement learns how to use your action maps to steer future customers towards your business outcomes.

Tip
The more outcomes you create, the better Genesys Predictive Engagement will be able to predict future outcome scores.

View your outcomes

  1. Click Journey > Outcomes.

Create an outcome

  1. Click Journey> Outcomes.
  2. Click Create Outcome.
  3. Use a descriptive name.
  4. Define at least one visitor or journey attribute.
  5. Click Save and close.
Important
You can specify as many visitor attributes and visitor journey conditions as you want. You must specify at least one.

Deactivate an outcome

Deactivate an outcome when you no longer need it.

  1. Click Journey > Outcomes.
  2. Click the name of the outcome you want to deactivate.
  3. Click the Active toggle so it is gray.
  4. Click Submit.
Important
Do not delete outcomes.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Outcomes (2025-06-19 06:23:08)"
Comments or questions about this documentation? Contact us for support!