Journey Analytics Previously known as Transact Insights. | Analytics User | Latest Version Latest version 21.05.0 cloud hosted.
Journey Analytics, formerly known as Transact Insights, is a purpose-built behavioral analytics module that provides additional extensive analytics on your applications hosted on the Temenos Journey Platform.
Once set up, Journey Analytics aims to assist customers to track the performance of their applications on their Journey Platform from an analytical perspective. Journey Analytics provides a wide variety of analytical views that capture completion analysis for one or more applications. As well as these features, Journey Analytics also supports rich filters that allow customers to understand the device type, browser and other attributes of the devices used to complete applications.
Journey Analytics must be enabled for Maestro, Composer or Open UX applications in Journey Manager to be able to collect Journey Analytics data.
A key value Journey Analytics offers is the behavioral analytics to assist our customers to understand user engagement with the form, the effort it takes to submit an application, and where users are abandoning their applications.
These fine-grained metrics help to identify abandonment hotspots in the customer application and further explore problematic fields to:
Journey Analytics now offers eight main analytical views for both application performance analytics and user behavioral analytics:
The Journey Analytics User Interface is common to all analytical views. Use the interface to select the required analysis views, select the timeframe for analysis, and set global filters and preferences.
From Journey Manager 18.11 a new user interface called the Visualizer was introduced, which is a modern user interface that brings together modern best practices to deliver a refreshed user experience. For customers on Journey Manager 18.11 and later, all analytical views will be seen through this refreshed user interface. For customers on Journey Manager 18.05 and earlier, the original legacy Dashboard user interface will display. Examples of both user interfaces are available in this documentation.
Journey Manager forms or applications designed in Maestro, Composer or Open UX are referred to as applications in Journey Analytics, and once a user submits the application in the browser it becomes a completed transaction in Journey Manager.
Transactions on Journey Manager may progress through any of the following statuses; Open, Bounced, Started, Saved, Completed, Abandoned.
Transactional data entered by users is not stored in Journey Analytics, however, Journey Analytics does store information about the transaction status and user behavior events from the application. This behavioral data is stored and used to populate all the Journey Analytics analysis views.
The transaction status and user behavior events DO NOT include any user input data itself and hence Journey Analytics DOES NOT collect any Personally Identifiable InformationPersonally identifiable information (PII) is any data that could potentially identify a specific individual. Any information that can be used to distinguish one person from another and can be used for de-anonymizing anonymous data can be considered PII. (PII). The Journey Analytics service has been explicitly designed to NOT record or store user input data and PII.
You may verify this by using the browser’s F12 tool to monitor the network traffic of an Journey Analytics enabled application. Journey Analytics employs all possible mechanisms and strategies to NOT store data relating to PII. For more information, see Journey Analytics Data Privacy and Security.
Journey Analytics is built and hosted on the Google Cloud Platform (GCP) infrastructure. It is a fully managed service built using the GCP. The image below describes the high-level architecture of Journey Analytics and how it fits into the Journey platform.
Journey Analytics collects events from two sources – Journey Manager and the browser where the application is rendered.
Journey Manager sends transaction status events and applications rendered in the browser send user interaction events. These two sources support the detailed statistical analysis of user behavior within applications.
The user interaction events from the browser include information such as - field visit, field completion, validation error, section navigation etc. These analytical events are directly comparable to the Google Analytics or Adobe Analytics events recorded by these analytics services. For more information, see Journey Analytics Data Privacy and Security.
Some setup and user administration is required to use Journey Analytics. Users must have the Journey Analytics user role and space added to their Journey Manager user accounts to be able to access Journey Analytics.