Many industries have complex workflows and user journeys that span multiple transactions and other event types such as logs and EUM data. These workflows typically take a long time to manifest and cannot be measured using transactions alone. Business Outcomes are a way to monitor and correlate the data flow across multiple event sources and track the total end-to-end time for defined business workflows. Typical multi-step workflows from different industries include:
- Payment transfers, credit card approval, and loan approval in financial services industries
- Cellphone Activation and data recharge (pre-paid) in the Telco sector
- Insurance application through policy approval and insurance claims approval for insurance companies
Enabling Business Outcomes
SaaS environments: Business Outcomes is enabled by default.
On-premises installations: Business Outcomes is disabled by default. To enable Business Outcomes for on-premises installations:
- Edit the
truebefore starting the Events Service.
Business Outcomes Definition
Business Outcomes provides the capability to define the following:
- Milestones (the steps in your business workflow) and the events comprising the milestones. A Business Outcome can include events from multiple analytics event types, such as logs, business transactions, and EUM data.
- Fields to capture from each milestone event.
- The primary key field that uniquely ties the events together. The primary key value must be present in each milestone event.
- Additional fields that allow you to segment on different dimensions of the business workflow, such as loan types or payment amounts.
- Health thresholds for monitoring the Business Outcome performance.
Data Prerequisites for Defining Business Outcomes
Analytics creates Business Outcome composite events by collecting events and fields that you already capture as analytics data. As you define the milestones in the Business Outcome, you specify which events to use and which fields to extract from the events. You can extract fields collected by default or custom fields that you have configured for collection.
You need to know your starting and ending event and the clearly defined steps in between.
To collect additional fields in the events being captured by Application Analytics use one or more of the following techniques:
Business Outcomes Health Thresholds
A threshold is a boundary of acceptable or normal performance. Business Outcome authoring provides default health thresholds against which it compares the performance of the Business Outcome. The Business Outcome health thresholds are based on the total time to complete all the milestones in your Business Outcome and are calculated by determining the standard deviation from the simple moving average over an interval of time. The default time interval is two hours. This means that if the average end-to-end time for the last two hours is N milliseconds, and if the Business Outcome takes time equal to the standard deviation over N milliseconds (ms), it violates threshold.
For example, consider a simple moving average that is 1500 ms with a standard deviation of 100 ms. If you set the threshold to three, it means that the threshold is three times the standard deviation. In other words, a transaction that takes more than 1500 + (3*100) or 1800 ms violates the health threshold.
Note the following: