Journey Analytics The behavioural analytics tool. | Analytics User | Latest Version Latest version 21.05.0 cloud hosted.
Global Filters allow you to choose filters to define which transactions to analyse within Journey Analytics. Any global filters applied will impact all analytics views. The behavior of global filters and how to apply them are described below.
The filter allows you to determine which transactions are used in visualizations for all views. Constraints can be in the form of either a whitelist or a blacklist:
To add global filters, use the following steps:
Selecting more than one filter value will restrict transactions to only those which match all selected values. The filters, in this way, are applied in an additive manner.
Global filters allow you to focus on particular transactions and to filter using a range of categories:
To only show trusted browser transactions, you could:
In this way, the filters are flexible so you can exclude or include transactions as needed.
The Legacy Dashboard app is now deprecated and replaced by the Journey Analytics Visualiser app. The Legacy app will be unavailable from v23.04.
The filters available allow you to focus on particular transactions and to filter by a range of categories which include:
To apply the global filters you selected, click Apply. The selected filters will then be applied across all applications visible in the analytics views.
To reset the global filters, click Reset.This clears the global filters and resets the time period to 1 week.
To reset the global filters, simply click Apply again.
In v18.05 the Scope filter allows you to choose applications from available organizations and/or spaces.
To filter by scope:
Consider the following:
The Scope filter is not required, as all organizations and spaces the user has access to in Journey Manager will be available for analysis.
The Period filter allows you to choose a specific time frame where transactions associated with the selected applications were undertaken. The time period will remain visible on the top right-hand corner in all views of Journey Analytics.
To select the date range:
To select a custom timeframe:
The pre-defined period options are calculated backwards from 11.59 pm of the day prior to the current date.
Filtering based on the client device allows you to analyze data coming from specific devices and configurations. This data provides information on how transaction data from different device configurations compare against one another.
For example, you may want to only show transactions completed using a mobile phone. To do this, filter by the Mobile Phone Device Type.
To filter by device:
The Location filter allows you to filter transaction data coming from specific geographies, such as Country, Region, or City.
To filter by location:
| v18.05 & Earlier This feature is related to v18.05 and earlier.
The Cohorts filter allows you to filter transactions based on specific custom milestones that have been identified and configured in Maestro, Composer or Journey Manager.
From v18.11 you can also filter by Segments, that have been configured and addedd to the Segment Whitelist.
From v19.05 you can also filter by Collaboration Jobs.
Custom milestones are preconfigured events that occur in a transaction. To filter by milestone is to filter by a specific event that occurred in a transaction.
To filter by milestones:
Selecting more than one milestone in the Filter will only include transactions that contain all selected milestones. For example, in an application with configured milestones called Prefilled Info and E-Signed, that trigger if the user chooses to auto-populate form details or sign electronically, choosing both milestones in the Filter will display only the transactions that have both Prefill Info AND E-Signed milestones.
| v18.11 & Higher This feature is related to v18.11 and higher.
Segments are custom events or groups that are preconfigured and sent from a Maestro or Composer application, or from a groovy/fluent service on Journey Manager to Journey Analytics. Each segment event lets Journey Analytics know to which segment or group a transaction belongs to. A transaction can only belong to one segment or group. For instance, transactions can be grouped by gender, age or age brackets, products selected, or Exchange packages used to complete an application, such as the Mitek drivers license scan.
To filter by segments: