The Form Analytics overlay helps you evaluate the effectiveness of a form and how well visitors are able to complete it.
The following reports are provided:
- The Form funnel report shows the number of visits that were made to each element (input box, checkbox, button) on a form for a specified date range. A visit to a form element is incremented when a user clicks or taps on an element, or tabs into the element to edit or provide information in the form. With changes to Form Analytics in July 2018, individual elements that make up a radio button list are consolidated into a single entry on the Form Funnel report, rather than the individual element's xpath.
Note: The change to Form Analytics that consolidates individual elements from a radio button list, into a single entry, is not retroactive. The consolidation occurs for new data only. If a form is displayed that contains older visitor interaction data (from before the change to how Form Analytics handles radio button lists), both the group (name) and the previous individual radio button data points are displayed in the Form Funnel. If you want to display just the consolidated name values, you must specify a date range from the July 2018 release or later.
- Form activity shows the following information:
- A ranked list (by percentage) of the fields that customers interacted with most before they abandoned the form.
- A ranked list (by percentage) of the fields that customers first interacted with on the form.
The Form activity report also displays data on valid and invalid field states for forms submitted and forms abandoned. Valid is optional, but submitted/abandoned are split into percentages.To capture data for the Form activity report, the capture library must be updated for web or mobile apps. The captured data for the Form activity report uses a new message type. If the message type is not in the capture library, the report data will be incomplete.
- For information on how to configure Web SDK to let it know when a form is submitted, see TLT.logFormCompletion in the UI Capture Public API Reference.
- For an iOS example of how to let Tealeaf® know if a form is submitted for the report, see How to instrument Form Completion in your application in the Watson™ Customer Engagement | For Developers How-tos with Sample Code for iOS.
- For an Android example of how to let Tealeaf know if a form is submitted for the report, see How to instrument Form Completion in your application in the Watson Customer Engagement | For Developers How-tos with Sample Code for Android.
- The Dwell time report shows whether the time that the user spent on a form is above or below the average time that all users spent on a form. The average time is included in the above-average count.
- The Repeats report shows the number of times a user clicked a form more than once. A high number of repeated clicks can indicate a problem with the field or the instructions for the field.
A counter is used for each field to track how many extra times a user placed the cursor in the field. For example, if a user clicked in a field three times, the counter records two repeats. The Repeats report displays each field on the screen and how many times after the initial click that each field was clicked.
You can filter the data on the overlay by any dimensions that are associated with the data.
From all of the reports, you can go to a list of sessions that are used to create the reports. For example, you can go to a list of Completed or Abandoned sessions from the Form funnel report.
For all reports, when you hover over an item in a report, the form in the overlay is highlighted and the overlay moves so the form is in the visible area of the screen. The form might be behind the report and not immediately visible. You might need to move the report to another area of the screen to see the highlighted form.
Article is closed for comments.