Brief Overview

Engaged Elements are an Insights feature that track how users interact with elements in the underlying application, without relying on Digital Experience Analytics (DXA).

They allow you to understand user behavior even if you choose not to use DXA, while maintaining enhanced privacy and reliable data collection. Engaged Elements help identify user pain points and inform better implementation decisions across WalkMe experiences.

How It Works

An Engaged Element is a WalkMe content type published from the editor and tracked through Insights.

Engaged Elements can be tracked when:

• The element appears on screen
• A user interacts with the element

Supported interaction types include:

• Click
• Hover
• Input
• Visible
• Text change

Engaged Elements are created by capturing elements in the WalkMe Editor and use the rule engine to ensure accurate and reliable tracking. Capturing through the editor also provides an added layer of security for data-sensitive environments.

Use Cases

Use Engaged Elements when you need to:

• Track user interactions without manually defining events or writing selectors
• Collect interaction data directly from elements published in the WalkMe Editor
• Apply rules to improve accuracy and reduce false positives in analytics
• Gain reliable insights into user behavior with minimal configuration
• Track interactions in privacy-sensitive environments without relying on DXA
• Measure a variety of interaction types, such as clicks, input, hover, visibility, or text changes

Create an Engaged Element

To create an Engaged Element in Insights Console, follow the instructions here:

How to Create Engaged Elements

Best Practices

Scope and performance

• Limit the number of Engaged Elements using All site to reduce performance impact
• Prefer page-specific Engaged Elements when possible

Page context

Define a specific page or section of the application to establish the context of the element.

When similar elements appear on multiple pages, create separate Engaged Elements per page to ensure accurate data.
For example, track a Save button only on the New Opportunity page instead of across the entire application.

Define Page Identification Rules

Page identification rules determine where WalkMe should look for the element.

Best practices:

• Use URL-based rules to uniquely identify the page
• Use Like with wildcard characters (*) to define dynamic URLs
• Combine URL rules with element rules for improved accuracy

Each supported application may require different page-identification strategies.
For example, in Workday®, Worklets are commonly used to define page context.

Analyzing Engaged Elements in Insights

Once created in the Events page, Engaged Elements appear in the Events List and are available in Insights visualizations.

Insights Events Page

Technical Notes

Availability and limits

• Engaged Elements are not supported in:
  • Version history
  • On-Premise environments
• A maximum of 20 Engaged Elements per page is supported
• Multiple Engaged Elements cannot target the same element

Rule support

Supported rule types:

• URL
• On-Screen Element
• jQuery Element
• Workday® (plugin required)
• Salesforce (sfVars)
• Segment reuse

Only location-defining rules are supported. User- or time-based rules are not supported.

Platform support

Supported applications include:

• SuccessFactors
• Workday®
• Salesforce Classic
• Salesforce Lightning
• Microsoft Dynamics
• Any editor system using DeepUI

Privacy (PII)

• No PII is collected from element attributes
• PII risk is equivalent to WalkMe Engagement tracking
• PII may still appear in URLs, page titles, or identifiers

If this is a concern, refer to Insights: Prevent Collecting PII Using Insights Privacy Settings.