Scope Selector

   Journey Analytics Previously known as Transact Insights.  |   Analytics User |   Latest Version Latest version 21.05.0 cloud hosted.

The Journey Analytics scope selector allows users to select what and when to analyse. It includes a dropdown to let you select the application and version or job. It also includes a second dropdown which is used to select the date range.

Select form or job scope

Some views are capable of displaying multiple forms (applications) and versions. Whereas, other views only show data for a single form and version. Use the steps below to select the scope:

To select multiple applications or jobs, or multiple versions in a Journey Analytics view:

  1. Click on the form (application) or job dropdown.
  2. Click all the versions you want to analyze. If there is only one version, simply click on it.
  3. Click OK.
Click the image to view animated example

To select a single application or job in a Journey Analytics view:

  1. Click on the form (application) or job dropdown.
  2. Click the version you want to analyze. If there is only one version, simply click on it.
  3. Click OK.
Click the image to view animated example

Select All, Clear All and Cancel

Click Select All to select every form or job and all of their versions.

Click Clear All to clear the current selection and make another selection, or click Cancel to leave the scope as is.

Sorting

If multiple organizations are accessible for the current user, the scope selector will show the Org Name above each form entry. In addition, sorting buttons appear at the top of the scope selector.
  • Click a toggle button option to sort the list alphabetically by Form or Org name.
  • Use the Cancel button if you wish to see the default sort order.

Select the date range scope

As part of selecting the scope, you can also adjust the date range using the Period dropdown.

  1. Click on the Period Selector.
  2. Click on the date range you want to analyze. Use the Custom option to set the range manually.
  3. Click OK.
Note

As Journey Analytics is a near real-time analysis tool, user transaction data is regularly aggregated and is not immediately available. The delay before data from new transactions becomes available for visualization can be up to 24 hours after the transaction is completed.

To minimize the impact of this delay on your analysis, previous duration options are recommended as they do not include data from today. If you need to inspect transactions from today, use the Last Analysis to determine the freshness of available data.

Period duration options

Use the table to understand each date range available:

Option Description Result - if today is 10th April 2021

Today

Use this option to view analyzed transactions that started today.

From 10th April 2021 (12 am) to now is shown.

Use Last Analysis to determine when analysis last ran.

Yesterday

Use this option to view analyzed transactions that started yesterday.

From 9th April 2021 (12 am) to 9th April 2021 (11.59 pm) is shown.

Last Week

Use this option to view analyzed transactions that started within the week ending yesterday.

From 3rd April 2021 (12 am) to 9th April 2021 (11.59 pm) is shown.

Last Fortnight

Use this option to view analyzed transactions that started within the fortnight ending yesterday.

From 26th March 2021 (12 am) to 9th April 2021 (11.59 pm) is shown.

Last Month

Use this option to view analyzed transactions that started within the month ending yesterday.

From 9th March 2021 (12 am) to 9th April 2021 (11.59 pm) is shown.

Last Quarter

Use this option to view analyzed transactions that started within the previous quarter ending yesterday.

From 9th January 2021 (12 am) to 9th April 2021 (11.59 pm) is shown.

Last Year

Use this option to view analyzed transactions that started within the previous year ending yesterday.

From 9th April 2020 (12 am) to 9th April 2021 (11.59 pm) is shown.

Custom

Select the individual start and end dates from the calendars.

From start date (12 am) to end date (11.59 pm) is shown.

Note

Timezone can affect the actual window of time selected. For example, a transaction from today in Australia (UTC +10hrs) will not be available if the timezone is set to Hawaii Standard Time (UTC -10hrs). In scenarios such as this, it's recommended to set the timezone to where the transactions originated.