View Business Journey events from the Analytics Search UI in the same way as any other event type. Alternatively, use the Analytics Search button on the Business Journey UI.

Search for Business Journeys

Use the Analytics Search button in the Business Journeys UI for one-click access to the underlying events. Selecting an enabled Business Journey and clicking Analytics Search takes you directly to the Searches page in Basic mode. Analytics Search button is unavailable for definitions in Draft and Valid Draft states.


Alternatively, access the Analytics Search UI and use the event type dropdown to find your Business Journey event. The Business Journey name identifies the event type in the Search UI similar to custom events. In this example, it is "loanapprovals".

You can search the Business Journey data and create visualizations in the same fashion as for any other analytics event type.

Business Journeys also gives you the ability to perform analytics, slice and dice data, and create widgets. For example, using the loan approval Business Journey, visualize percentile values of approval time, loan amount by type, and loan applications by type as follows:

The 50th Percentile line indicates that 50% of the loan approvals occurred below this line. Similarly, each percentile line represents the corresponding percentage of loans approved below that line.

Business Journeys ADQL Queries

To use ADQL to query Business Journey events, you need to use the full namespaced field name for each milestone. The field names are constructed by appending the milestone name to the field. When constructing queries with ADQL in the Search UI, you must use the full name of the field. The following image shows constructing a sample ADQL query.

A sample ADQL query for the loanapproval Business Journey is:

Business Journeys Metrics

Analytics generates out-of-the-box metrics at the Business Journey definition and milestone levels. You can view these metrics in the Metric Browser. The metric values are reported per minute. For example, an observed value of 5 indicates that it's the count of the records received in the one-minute interval. If the number of records reported in the last five minute is 25, the Metric Browser reflects an approximate observed value, that is 5. To calculate metrics, Analytics adds two fields named timeTaken and totalTime.

The timeTaken field is added to the associated event for each milestone. This field represents the time taken for an event to reach a milestone from the previous milestone, and therefore, the first milestone will not have this value.

The totalTime field is added to the associated event for each Business Journey definitiontotalTime represents the time for an event to cover all the milestones comprising the Business Journey. It is the time an event takes to reach the last milestone from the first one. If the first or the last milestone is missing, totalTime is not calculated for that event. For example, if the loan application is rejected in the CreditCheck stage, the workflow never reaches the approval stage. In this case, totalTime is not determined. 

By using the above-mentioned fields, the following out-of-the-box metrics are generated.

Milestone Level

Average timeTaken: Average of the values measured for the timeTaken field. Evaluates the events that started in the last one day and reached the milestone in the last one minute. 
Calls per minute: Number of events that started within the last one day and reached the selected milestone in the last one minute.

Definition level

Average totalTime: Average of the values measured for the totalTime field. Evaluates the events that started in the last one day and reached the first milestone in the last one minute.
Calls per minute: Number of Business Journey events measured per minute. This number is equal to the calls per minute value of the first milestone. The value is calculated by evaluating the events that started in the last one day and reached the first milestone in the last one minute.

The lookback period to generate out-of-the-box metrics is one day. The values for the metrics might not be accurate if events take more than a day to complete or to even reach the next milestone. This is due to the lack of sufficient event records for Analytics to generate correct values, leading to displaying incorrect values. For example, the average totalTime metrics will only be accurate if events finish within the lookback period, that is one day. 

Note that the existing definitions will not have the out-of-the-box metrics created. You need to create new definitions to generate corresponding out-of-the-box metrics.

Business Journeys Dashboard

Analytics provides two Views for Business Journeys: Card View and Grid View. Business Journeys page defaults to the Grid View, but after switching to the Card View the UI makes it as the preference. The next time you log in, Business Journeys page defaults to the Card View. Use the View button on the toolbar to switch between the Views.

The Card View displays an out-of-the-box dashboard for each Business Journey definition along with key metrics. The dashboard highlights the milestones associated with each Business Journey definitions and these metrics:

Dashboards for Business Journeys created prior to the release of Analytics 4.5 do not display the Average time to reach the next milestone metric. To workaround, edit the Extract Field section of one of the milestones and add the new field or remove an existing field. After the definition is saved Analytics starts generating the missing values. Within a few minutes, you should see values for Average time to reach the next milestone for the Business Journey you edited.

Time range menu determines what events are considered for calculating metrics. The events that are considered for calculating metrics are only those started in the selected time range.

  • End-to-End: The average end-to-end time an event takes to complete the corresponding Business Journey. It is the average time taken by an event to reach the last milestone from the first one.
  • Conversion: The conversion rate represents the percentage of events that reached the last milestone from the first one. It is calculated as (events reached the last milestone) * 100 / (events reached the first milestone).
  • Average time to reach the next milestone: It is the average time an event takes to reach the next milestone from the current one. This value is represented by the number shown in between each milestone. 
  • Event count per milestone: It is the number of events that reached a particular milestone. This value is indicated by the number shown inside the circles representing each milestone.