Insights Overview

   Insights This topic is related to Insights.  |   Analytics |  v5.1 & Higher This feature is related to v5.1 and higher. |  Updated in v18.11 This feature was updated in v18.11.

Insights is a purpose-built behavioral analytics module that provides additional extensive analytics on the applications hosted on the Transact Platform.

Once set up, Insights aims to assist customers to track the performance of their applications from an analytical perspective. Insights provides a wide variety of analytical views that capture completion analysis for one or more applications. As well as these features, Insights also supports rich filters that allow customers to understand the device type, browser and other attributes of the devices used to complete applications.

Insights must be enabled for Maestro, Composer or Open UX applications in Transact Manager to be able to collect Insights data.

A key value Insights 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:

Analytics Views

Insights now offers seven main analytical views for both application performance analytics and behavioral analytics:

  1. Dashboard View – gives a high-level overview of application performance providing key metrics on completion, device distribution, completion times and recent completion history.
  2. Timeline View – provides a trend of application statuses over a selected period. In addition, you can aggregate the data at various levels and split the data by device type, browser, application version and other options.
  3. Dropoff View – provides behavioral analytics capturing key insights on user interaction with the application. It includes section and field level metrics that help to identify abandonment hotspots, problematic fields, and application flow.
  4. Field Analysis View - provides detailed field-level statistics for each section of the application being analyzed. It also helps to identify abandonment hotspots by aggregating all field level behavioral data for all transactions during the selected time frame. In v18.05 this view is a component of the Dropoff View.
  5. User Journey View – introduced in 18.05, this view provides a map of custom milestones implemented in the application and how users are progressing through them towards completing the application. It also provides insight into all possible journey paths users are taking to complete transactions. In addition, it allows customers to perform segmentation analysis of the users based on the data sent by the Segment APIs from the application form or Transact Manager.
  6. Collaboration Job View - introduced in 18.11, this view uses a node graph to represent the Collaboration Job workflow. It provides a view into key metrics at the job, step, action, section and field level.
  7. Data Export View - introduced in 18.11, this view has been designed specifically to export the raw Insights data into a CSV file to perform custom analysis. It does not visualize the data like the other views.

Insights User Interface

The Insights 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.

 |  v18.11 This feature was introduced in v18.11.

Introduced in 18.11 is a new user interface called the Visualizer, a modern user interface that brings together modern best practices to deliver a refreshed user experience. For customers on Transact Manager 18.11, all analytical views will be seen through this refreshed user interface, and functionality in both user interfaces remains the same.


Transact Manager forms or applications designed in Maestro, Composer or Open UX are referred to as applications in Insights, and once a user submits the application in the browser it becomes a completed transaction in Transact Manager.

Transaction Status

Transactions on Transact Manager progress through the following statuses; Open, Bounced, Started, Saved, Completed, Abandoned.

Strict No PII Policy

Transactional data entered by users is not stored in Insights, however, Insights 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 Insights analysis views.

The transaction status and user behavior events DO NOT include any user input data itself and hence Insights 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 Insights 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 Insights enabled application. Insights employs all possible mechanisms and strategies to NOT store data relating to PII. For more information, see Insights Data Privacy and Security.


Insights 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 Insights and how it fits into the Transact platform.

Insights collects events from 2 sources – Transact Manager and the browser where the application is rendered.

Transact 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 Insights Data Privacy and Security.

Set Up and User Administration

Some set up and user administration is required to use Insights. Users must have the Insights user role and space added to their Transact Manager user accounts to be able to access Insights.