Manage outcomes
Learn how to define the business goals that you want to track and predict. To simplify the process of creating an outcome, duplicate an existing outcome.
Notes:
- Specify at least one condition.
- Outcome Scoring is unavailable by default.
- To create an outcome after you reach the outcome limit, delete an existing outcome.
Create or edit an outcome
| Entity | Description |
|---|---|
| Outcome Details | |
| Name | A 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 website. To deactivate an outcome temporarily, slide the toggle to No. To remove an outcome permanently, delete it instead. |
| Outcome Scoring | Enable the outcome for scoring. You can enable scoring for up to 10 outcomes. Note: Available only for Predictive Engagement customers |
| Define your outcome conditions | |
| Session type/Event source | Select the type of session:
|
| First event | Attributes that identify visitors based on shared behaviors. For example, completing a form or going to a specific webpage. Note: If the outcome is to be enabled for scoring, Genesys recommends that only the actual achievement event, such as the URL uses ‘/paymentSuccessful’ and the outcome is not limited to a particular domain. This process helps improve the accuracy of predictions. |
| 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 extract from the outcome that you are tracking. Currently, only numeric value types are supported.
Note: You can assign a value only to the event you added last. For example, if you define a series of three events to achieve your outcome, you can assign a value only to the third event. |
| Define your visitor characteristics | |
| Visitor attributes | Attributes that identify visitors based on characteristics such as location, browser, or device type. |
Customer 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 Campaign attributes.
| Attribute name | Description | Examples |
|---|---|---|
| Device category | Category of device that the visitor is using. |
|
| Device type | Type of device that the visitor is using. |
|
| OS family | Operating system family that the visitor is using. |
|
| Browser family | Browser family that the visitor is using, including all versions of the browser within that family. |
|
| Browser version | Major version of the browser that the visitor is using. |
|
| Campaign source* | A search engine, newsletter, or other source (UTM parameter). |
|
| Campaign medium* | Medium such as email or cost-per-click (UTM parameter). |
|
| Campaign name* | Specific product promotion or strategic campaign (UTM parameter). |
|
| Campaign term* | Keywords for this ad (UTM parameter). |
|
| Campaign content* | Ads or links that point to the same URL (UTM parameter). | |
| Campaign Click ID* | A unique number that generates when a potential customer clicks an affiliate link (UTM parameter). |
|
| Campaign network* | Ad network to which the click ID belongs (UTM parameter). |
|
| Country | Visitor’s country. |
|
| City | Visitor’s city or town. |
|
| Region | Visitor’s region.
To track by United States, supply the two-digit state code in all caps. |
|
| Post code | Visitor’s postal code. |
|
| CCA2 code | Two-letter country code. |
|
| Browser language code | Language to which the visitor’s browser is set. | |
| Device OS language | Language to which the visitor’s device is set. | |
| Organization name | Organization name derived from the IP. |
|
| Referral URL | Referrer page URL. |
|
| Referral hostname | Referrer host or hostname. |
|
| Referral medium | Referrer medium. |
|
| Authenticated | Indicates whether the event was produced during an authenticated session. |
|
| App name | Name of the application. |
|
| App namespace | Unique application ID. |
|
| App version | Application version number. |
|
| App build number | Application build number. |
|
Customer journey attributes
When you define a condition that includes a visitor journey attribute, Genesys Cloud 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.
Notes:
- To track a more complex visitor journey, define multiple conditions. Genesys Cloud evaluates all conditions in the visitor journey sequentially, in the order that you define them. The system doesn’t validate free form text. If you misspell a value, the outcome doesn’t trigger. For example, typing “ACB Retailer” when the page title is “ABC Retailer.”
- When specifying a 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, you have a custom event called “CartValue” and you want to target all customers who have a cart value of $100 or more. 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 | Session type | Example |
| autotrackClick | To track when and where a visitor clicks a webpage. For more information, see autotrackClick. | Web | Clicks the ‘More’ button. |
| Custom attribute | Allows you to identify groups of visitors based on characteristics and behaviors that are specific to your business. | Web App | “productCode” or “productName” |
| Event name | Represents actions that occur on your website. For example, an 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. | Web App | The recommended format is object_action.
|
| form:track | To track the value of webpage form submissions. For more information, see forms:track. | Web | sign-up-form |
| Page URL | URL of the page. A full protocol is required. | Web | https://www.genesys.com/?s&q=predictive%20engagement |
| Page title | Meta title of the page (not the heading on the page). | Web | Contact Us |
| Page hostname | Host name of the page’s URL. | Web | app.genesys.cloud |
| Page domain | Domain of the page’s URL. | Web | app.genesys.cloud |
| Page fragment | A 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. | Web | #/journey/segment/create |
| Page keywords | Keywords from the HTML<meta>tag of the page. | Web | contact |
| Page pathname | Path name of the page. | Web | /journey/admin/ |
| Search query | Represents the keywords in a visitor’s search query. | Web App | test |
| URL query string | Query a string that passes to the page in the current event. | Web | q=test |
| Screen name | Name of the viewed mobile app screen. | App | Products |
[NEXT] Was this article helpful?
Get user feedback about articles.