About Insights Tracked Events

Last Updated December 10, 2024

Brief Overview

With Tracked Events, you can easily track any meaningful event on your website or application, such as end-users signing up for your service or upgrading to a new plan.

Once defined, Tracked Events will be identified in all subsequent sessions. Tracked Events are re-usable and help you to filter sessions more effectively and create better flows to track end-user engagement with your website using Flow Analytics.

Unlike WalkMe engaged elements and Smart Walk-Thru goals, tracked events enable you to follow end-user completion of processes with or without the presence of WalkMe items on your website. By tracking before and after WalkMe, you can gauge the effectiveness of your WalkMe solution.

Tracked Events support

Interactions with WalkMe content
Clicks and input (requires DXA to be enabled)
Page visits (requires page selection to be enabled)

Use Cases

Tracked Events use cases include the following:

Keep tabs on when and how many users view a signup page, and how many ultimately sign up
Track when users complete a purchase
Keep track of when users enable an advanced feature
Easily filter sessions by a wide range of user actions

Creating a Tracked Event

To create a Tracked Event, follow the instructions here:

How to Create Events

FAQs

What is the maximum number of tracked events we can use?

Users can have an unlimited number of tracked events.

Can using tracked events slow down the performance of an environment?

Based on investigations it has been concluded that WalkMe is not the root cause of the performance issues.

Technical Notes

Available retroactively when full DXA is enabled
Created by manual setup or capturing
There are character limits for Tracked Event classes and IDs in a selector
- Classes are limited to 35 characters per class
- IDs are limited to 40 characters per ID
If the character limit is exceeded, the tracked event will return 0
- Note: This only applies to individual classes and not for multiple classes
- Example: [class='btn btn_otherclass button_enable_specific_button superlongclassthatissupposedtobethislongtoreachthelimit]
- The classes "btn btn_otherclass button_enable_specific_button" will be collected but the class "superlongclassthatissupposedtobethislongtoreachthelimit" will not be collected
Copying tracked events between environments requires support intervention
Data capture or collection for elements that begin with a number is not supported
- For example: #1av345-d345

Was this article helpful?

Yes No

Yes

Thanks for your feedback!