Brief Overview

Tracked Events let you measure meaningful user actions across your website or application, such as completing a signup, making a purchase, or enabling a feature.

Once defined, Tracked Events are identified in all subsequent sessions and can be reused across Insights. They help you filter sessions, analyze funnels, and measure user behavior both with and without WalkMe content present.

Unlike Engaged Elements and Smart Walk-Thru goals, Tracked Events allow you to track end-user completion of processes independently of WalkMe experiences, making them ideal for before-and-after analysis.

Use Cases

Use Tracked Events when you need to:

• Track key user actions that occur outside of WalkMe content
• Measure completion of end-to-end processes, such as signups or purchases
• Analyze user behavior before and after WalkMe is deployed
• Filter sessions based on specific actions users take
• Build funnels and dashboards around business-critical events

How It Works

Tracked Events support the following data types:

• Interactions with WalkMe content
• User clicks and input actions (requires DXA)
• Page visits (requires page collection to be enabled)

Create a Tracked Event

Learn how to create a Tracked Event in Insights Console:

How to Create Tracked Events

Technical Notes

Availability and data collection

• Tracked Events are available retroactively only when full DXA is enabled
• Tracked Events can be created using manual setup or capture
• There is no limit to the number of Tracked Events you can create

Performance

• Based on internal investigations, Tracked Events are not the root cause of environment performance issues

Selector limitations

• Character limits apply when defining selectors:
• Classes are limited to 35 characters per class
• IDs are limited to 40 characters per ID
• If a character limit is exceeded, the Tracked Event returns no data
• Character limits apply to individual classes or IDs, not combined selectors
• Elements with identifiers that begin with a number are not supported (for example, #1av345-d345)

Environment management

• Copying Tracked Events between environments requires support intervention