Difference between revisions of "ATC/Current/AdminGuide/Manage outcomes"
(6 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
|DisplayName=Manage outcomes | |DisplayName=Manage outcomes | ||
|Context=Learn how to define the business goals that you want to track and predict. | |Context=Learn how to define the business goals that you want to track and predict. | ||
+ | |||
+ | <br /> | ||
|Dimension=Outcomes | |Dimension=Outcomes | ||
|ComingSoon=No | |ComingSoon=No | ||
Line 11: | Line 13: | ||
**'''Journey '''>''' Outcome '''>'''Add ''', '''Delete''', '''Edit''', '''View''' | **'''Journey '''>''' Outcome '''>'''Add ''', '''Delete''', '''Edit''', '''View''' | ||
|Section={{Section | |Section={{Section | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=To simplify the process of creating an outcome, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Outcomes#Duplicate|display text=duplicate an existing outcome.}}{{NoteFormat|1= | ||
+ | *You must specify as least one condition. | ||
+ | *Starting on June 14, 2021, you can no longer create more than 10 outcomes. To create an outcome after you reach the outcome limit, delete an existing outcome. For more information, see {{Link-Standalone|topic=ATC/outcome_limitation_change}}.|2=}} | ||
+ | |Status=No | ||
+ | }}{{Section | ||
|sectionHeading=Create or edit an outcome | |sectionHeading=Create or edit an outcome | ||
|anchor=CreateOutcome | |anchor=CreateOutcome | ||
|alignment=Horizontal | |alignment=Horizontal | ||
− | + | |structuredtext=<br /> | |
− | |||
− | |structuredtext= | ||
− | |||
− | |||
− | |||
|structuredtextwide=<br /> | |structuredtextwide=<br /> | ||
{{{!}} class="wikitable" | {{{!}} class="wikitable" | ||
Line 41: | Line 44: | ||
{{!}}Select the type of session: | {{!}}Select the type of session: | ||
− | *Web session: An example of a web session is when a user goes to your website and completes a form to place an online order. The associated events for the web session are: visitor visiting a website, visitor filling out the online order form, and visitor submitting the form. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_sessions | + | *Web session: An example of a web session is when a user goes to your website and completes a form to place an online order. The associated events for the web session are: visitor visiting a website, visitor filling out the online order form, and visitor submitting the form. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_sessions}}. |
− | |||
− | |||
{{!}}- | {{!}}- | ||
− | {{!}}{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes | + | {{!}}{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes#VisitorJourneyAttributes|display text=First event}} |
{{!}}Attributes that identify visitors based on shared behaviours. For example, completing a form or going to a specific webpage. | {{!}}Attributes that identify visitors based on shared behaviours. For example, completing a form or going to a specific webpage. | ||
{{!}}- | {{!}}- | ||
{{!}}Assign value to first event | {{!}}Assign value to first event | ||
− | {{!}}When you create an outcome, you can attach a perceived value to quantify the benefit of the specified outcome. For example, you can derive the value of an abandoned cart by creating an outcome. In the Value field, provide {{Link-SomewhereInThisVersion|manual=SDK|topic=Record|anchor=outcome_value|display text=a value to be extracted}} from the outcome that you are tracking. Currently, only numeric value types are supported. | + | {{!}}When you create an outcome, you can attach a perceived value to quantify the benefit of the specified outcome. For example, you can derive the value of an abandoned cart by creating an outcome. In the Value field, provide {{Link-SomewhereInThisVersion|manual=SDK|topic=Record|anchor=outcome_value|display text=a value to be extracted}} from the outcome that you are tracking. Currently, only numeric value types are supported. |
+ | Important | ||
+ | You can assign a value only to the event you added last. For example, if define a series of three events to achieve your outcome, you can assign a value only to the third event. | ||
{{!}}- | {{!}}- | ||
{{!}} colspan="2"{{!}}'''Define your visitor characterstics''' | {{!}} colspan="2"{{!}}'''Define your visitor characterstics''' | ||
{{!}}- | {{!}}- | ||
{{!}}{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes|anchor=VisitorAttributes|display text=Visitor attributes}} | {{!}}{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes|anchor=VisitorAttributes|display text=Visitor attributes}} | ||
− | {{!}}Attributes that identify visitors based on characteristics such as location, browser, or device type | + | {{!}}Attributes that identify visitors based on characteristics such as location, browser, or device type |
{{!}}} | {{!}}} | ||
|Status=No | |Status=No | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
}}{{Section | }}{{Section | ||
|sectionHeading=Visitor attributes | |sectionHeading=Visitor attributes | ||
Line 72: | Line 68: | ||
|structuredtext=For more information about visitor attribute operators, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}. | |structuredtext=For more information about visitor attribute operators, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Operators|display text=operators}}. | ||
− | For more information about visitor attributes that enable UTM-tracking of campaign-specific activities, see {{Link- | + | For more information about visitor attributes that enable UTM-tracking of campaign-specific activities, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes#VisitorAttributes|display text=Visitor attributes}}. |
<br /> | <br /> |
Latest revision as of 07:30, December 7, 2022
Contents
Learn how to define the business goals that you want to track and predict.
Prerequisites
- Configure the following permissions in Genesys Cloud CX:
- Journey > Outcome >Add , Delete, Edit, View
- You must specify as least one condition.
- Starting on June 14, 2021, you can no longer create more than 10 outcomes. To create an outcome after you reach the outcome limit, delete an existing outcome. For more information, see Outcome limitation change.
Create or edit an outcome
Entity | Description |
---|---|
Outcome Details | |
Name | Descriptive name of the outcome. |
Description | (Optional) Description of the outcome. |
Status | Outcomes are active by default. When an outcome is active, it is ready to use on your web site. To deactivate an outcome temporarily, slide the toggle to No. To remove an outcome permanently, delete it instead. |
Define your outcome conditions | |
Session type | Select the type of session:
|
First event | Attributes that identify visitors based on shared behaviours. For example, completing a form or going to a specific webpage. |
Assign value to first event | When you create an outcome, you can attach a perceived value to quantify the benefit of the specified outcome. For example, you can derive the value of an abandoned cart by creating an outcome. In the Value field, provide a value to be extracted from the outcome that you are tracking. Currently, only numeric value types are supported.
Important You can assign a value only to the event you added last. For example, if define a series of three events to achieve your outcome, you can assign a value only to the third event. |
Define your visitor characterstics | |
Visitor attributes | Attributes that identify visitors based on characteristics such as location, browser, or device type |
Visitor attributes
For more information about visitor attribute operators, see operators.
For more information about visitor attributes that enable UTM-tracking of campaign-specific activities, see Visitor attributes.
Attribute name | Description | Examples |
---|---|---|
Device category | Category of device that the visitor is using. | desktop
mobile other tablet |
Device type | Type of device that the visitor is using. | Apple
Archos Asus HTC Huawei Nokia Samsung SUN Microsystems Unknown |
OS family | Operating system family that the visitor is using. | Android
Chrome OS Firefox OS iOS Linux Mac OS Tizen Unknown Windows 9x Windows CE Windows NT Windows Phone Ubuntu |
Browser family | Browser family that the visitor is using, including all versions of the browser within that family. | Chrome
Firefox HTC_HD2_T8585 Opera IE Mobile Internet Explorer Opera Safari SamsungBrowser Viera |
Browser version | Major version of the browser that the visitor is using. | 55 |
Campaign source* | A search engine, newsletter, or other source (UTM parameter). | direct
adWords |
Campaign medium* | Medium such as email or cost-per-click (UTM parameter). | direct
organicsocialppcwebsite-ppc |
Campaign name* | Specific product promotion or strategic campaign (UTM parameter). | test campaign
Summer19 |
Campaign term* | Keywords for this ad (UTM parameter). | device
trialsubscription |
Campaign content* | Ads or links that point to the same URL (UTM parameter). | |
Campaign Click ID* | Unique number that generates when a potential customer clicks an affiliate link (UTM parameter). | CjwKCAiA1ZDiBRAXEiwAIWyNC2J6QZBJYwXHJPsZ
khECGKaZ7nRjmNEQzmn1Hqh8Labvn3FQ-Tn1pRoCEDYQAvD_BwE |
Campaign network* | Ad network to which the click ID belongs (UTM parameter). | search network
display network |
Country | Visitor's country. | United States |
City | Visitor's city or town. | Chicago |
Region | Visitor's region.
To track by U.S. states, supply the 2-digit state code (all caps). |
Midwest
IN |
Post code | Visitor's postal code. | 60610 |
CCA2 code | Two-letter country code. | US |
Browser language code | Language to which the visitor's browser is set. | en-gb |
Organization name | Organization name derived from the IP. | alto-universal.com |
Referral URL | Referrer page URL. | https://alto-universal.com/auto#quote-details |
Referral hostname | Referrer host or hostname. | alto-universal.com |
Visitor journey attributes
When you define a condition that includes a visitor journey attribute, Genesys Predictive Engagement matches visitors based on whether they take the action. For example, visitors who complete a form, go to a specific webpage, or add a product to their shopping cart but don't complete the purchase.
For more information about visitor journey attribute operators, see operators.- The system doesn't validate free form text. If you misspell a value, the segment doesn't trigger. For example, typing "ACB Retailer" when the page title is "ABC Retailer".
- When specifying time for a custom web event, include milliseconds.
- When specifying numeric values for a custom web event, only numeric relational operators are available. For example, say you have a custom event called "CartValue" and you want to target all customers who have a cart value of $100 or more. You would select the "greater than or equal to" operator and type 100 in the value box. Note: You can include decimal points but not the currency symbol.
Attribute name | Description | Example |
autotrackClick | To track when and where a visitor clicks on a webpage. For more information, see autotrackClick. | Clicks 'More' button. |
Custom attribute | Allows you to identify groups of visitors based on characteristics and behaviors that are specific to your business. | packageDeliveryStatus |
Event name | Represents actions that occur on your website. For example, object clicked (such as a button, link, or menu option), error generated, inactivity detected, URL changed, or scroll detected.
For more information about configuring events, see About modules. |
The recommended format is object_action.
|
form:track | To track the value of webpage form submissions. For more information, see forms:track. | sign-up-form |
Page URL | URL of the page. Full protocol required. | https://www.genesys.com/?s&q=predictive%20engagement |
Page title | Meta title of the page (not the heading on the page). | Contact Us |
Page hostname | Host name of the page's URL. | app.genesys.cloud |
Page domain | Domain of the page's URL. | app.genesys.cloud |
Page fragment | Fragment of the page's URL, sometimes called a named anchor. It usually appears at the end of a URL and begins with a hash (#) character followed by the identifier. | #/journey/segment/create |
Page keywords | Keywords from the HTML<meta>tag of the page. | contact |
Page pathname | Path name of the page. | /journey/admin/ |
Search query | Represents the keywords in a visitor's search query. | test |
URL query string | Query string that passes to the page in the current event. | q=test |