Journey Analytics The behavioural analytics tool. | Analytics User | Latest Version Latest version 23.04.0 cloud hosted.
| FAQs | Answer |
|---|---|
|
Are the Journey Analytics screens and the Journey Manager Analytics screens the same? |
No, the screens in Journey Manager include all transaction whether or not analytics has been enabled. However, Journey Analytics only tracks transactions which are analytics enabled. The charts therefore will not match for that reason. |
|
Are all user interactions captured by Journey Analytics? |
No, users may have settings or extensions in their browsers that block analytics events. For example, “Do Not Track” settings, ad blockers, or privacy-focused extensions can prevent the collection of behavior analytics. |
|
Can you confirm the Journey Analytics data only shows fields that have been interacted with? |
This is correct. Journey Analytics is a behavioral analytics tool and is only aware of fields if it receives at least one event for a field. This includes navigation, validation or completion, such as clicking in a field, auto population of a field or one or more keystrokes to complete the field. It is not possible with the current architecture of the application to know anything about fields that are never actually touched by a user. |
| In the Dropoff view, what is the difference between the Conversion Rate and the Completion Rate? |
Conversion Rates are calculated based on all incoming traffic to the form, which includes robots, search indexers and other non-user activity. Completion Rates, however, are calculated based on only the transactions where users actually interacted with fields on the form, or Started the application. |
| In the Dropoff view, why do stats differ between Transaction Metrics and Section Completion? |
Stats may differ between Transaction Metrics (form transaction-level stats) and Section Completion (form section-level stats) when users install browser addons which can block analytics events being captured for sections. |
| Is rounding used? | Rounding is used only to display larger numbers in a readable manner. Rounded numbers can be identified by the k (thousand), m (million) or b (billion) abbreviation. However, calculations use the actual raw counts, not the rounded figures. These can be found anywhere throughout the application where large numbers are presented. |
|
Why do the Journey Analytics Dashboard Duration statistics display as a median value, whereas Field Errors and Field Help are displayed as an average? |
Because Duration can have such a wide variation in values, we throw out the very high and very low values, to display the median. However the Field Errors and Field Help are often a much tighter bunch of values, so it makes sense to display them as an average. The range of numbers of errors is typically smaller compared to the time taken to complete a transaction. |
|
How long does it take for data to flow into Journey Analytics? |
It usually takes around 90 minutes from the time the user interacts with the application. However, when a new form is introduced, please allow up to 24 hours for the new form to be available in Journey Analytics dashboards due additional processing requirements. |
|
How long before a transaction is considered abandoned? |
Typically it takes 24 hours, and is configurable in Manager. |
|
How long is historical data available for viewing? |
Currently Journey Analytics data is warehoused indefinitely. |
| Why do the same segments appear in our DEV and UAT environments? | The Segment Whitelist is shared across all Journey Manager environments (DEV, UAT, TEST, STAGING, PROD). Changes to the Segment Whitelist in one environment will be reflected in all environments. |
| Why are transactions from the last 24hrs not included in the preset periods? | The preset periods do not contain the last 24 hours. Simply use the custom period with an end date of today. |
| Why after logging into Journey Analytics are the views all blank? | Log out, clear your browser cache and log back into Journey Analytics. |