- 29 Jan 2025
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
What is User Action Verification?
- Updated On 29 Jan 2025
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
Introduction
Understanding whether User Actions are configured correctly on the application, latched to the correct element, or if a User Action already exists on the element is crucial. Incorrectly created User Actions can lead to inaccurate data collection. The only method to check if the User Actions function correctly 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 enables content creators to validate User Actions contextually within the application where they are created, allowing for real-time identification and resolution of any issues. This process enhances 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, identify whether the User Actions created are captured on the application. It highlights all available User Actions on the page and displays any hidden or unavailable User Actions. Hidden or unavailable indicates that the User Action is not directly visible on the screen; for example, the User Action may be created on an option within a dropdown menu, or Whatfix may be unable to detect the element. This information enables the re-selection or creation of new User Actions.
Verify and remove duplicates
Use Verification to validate User Actions after creation. Validate User Actions to determine whether the elements are selected correctly and if the User Actions are captured.
Whatfix enables you to verify User Actions even after pushing them to Production. This enables you to understand if they're working fine, that is, specifically if the User Action is triggered based on the set Completion Rules, and detects duplicates. For example, two User Actions may be created on the same UI element. It also identifies if a User Action completes twice, which occurs due to incorrect element selection during User Action creation.