What is User Action Verification?

• Introduction
• Benefits of User Action Verification

Introduction

Have you ever wanted to understand if you've configured User Actions correctly on the application, if they have latched to the correct element or if there is already a user action on the element? If User Actions are not created correctly, the data that you collect could be inaccurate. The only way to check if the User Actions are working is by creating an Insight, which can be cumbersome. With User Action Verification, Whatfix enables you to do the following:

• View all the User Actions created on the page
• Verify if the User Actions are latched correctly on the elements
• Preview User Actions
• Edit User Actions
• Create new User Actions

The Verification experience provides content creators the ability to validate User Actions contextually on the application where they're created and identify and fix any problems in real time. This improves the overall quality of the Analytics data generated for User Actions.

Benefits of User Action Verification

Identify if User Actions are configured correctly

Using Verification, you can identify if the User Actions you created are captured on the application. It highlights all the available User Actions on the page and also shows any hidden or unavailable User Actions. Hidden or unavailable means that the User Action is hidden from view; for example, the User Action is created on an option inside a dropdown menu or Whatfix is unable to detect the element. You can use this information to reselect or create new User Actions.

Verify and remove duplicates

You can use Verification to validate User Actions post-creating them. When you validate User Actions, you can understand if the elements are selected correctly and the User Actions are captured.

You can verify User Actions even after pushing them to Production. This enables you to understand if they're working fine, that is, if the User Action gets triggered based on the set Completion Rules, and also helps you detect duplicates. For example, there are two User Actions created on the same UI element. It also helps you find out if a User Action gets completed twice. This happens due to incorrect element selection while creating a User Action.