About Insights Engaged Elements

Updated on October 11, 2020 Download PDFDownload as PDF
Download PDF

Brief Overview

Engaged Element is an Insights feature that allows you to understand how your end-users behave in the underlying platform, even if you prefer not to use Digital Experience Analytics (DXA) due to security concerns. Engaged Elements will help understand your end-users interactions regardless of WalkMe’s different features. This type of analytics will help you better understand your end-users pain points in order to make better implementation decisions.

Please note:

This feature is currently not supported in the EU. To enable for your account, contact your WalkMe Account manager

How it Works

After an Element is captured as an Engaged Element in the Editor. These elements will then be automatically shown in Insights as Tracked Events (link) and can be analyzed in Insights as any other Tracked Events in Funnels, Tracked Events Dashboard, etc.

Creating an Engaged Element in the WalkMe Editor

1. Open the WalkMe Editor → All Items → Engaged Elements

2. Click on + next to the page list to create a new page or click on the orange + to create a new Engaged Element in an existing page

3. Capture the element you wish to track

4. Give the Engaged Element a name

5. Specify the Interaction Type you wish to track:

  • Click
  • Input
  • Hover
  • Visible

6. Click Save

7. Publish to the relevant environment

When to specify the page for the Engaged Element and when to use sitewide instead?

When selecting an element that is placed on a component of the site that is common to all pages (for example, Sidebar navigation, footer, headlines, etc.), make sure to specify to track the element Sitewide to cover all pages where it appears. This means selecting All Site Pages (Sitewide) as the Page before capturing the Engaged Element.

However, it is best practice to set a specific page or section of the Platform that defines the “context” of the element. This Page will be the location the element will be tracked in.   When you have similar elements in several pages and you wish to get data for a specific page only, make sure you create the Engaged Element only for that certain page.

Example: a “Save” button for a New Opportunity page should be set to track on the opportunity page only. It will eventually filter the clicks tracked for this button to these occurred on this page only.

How to Identify the Page

Since WalkMe’s September 2020 Version of Engaged Elements, Segmentation Center rules are supported for defining a Page.

Each Supported Platform has its own Best Practices to define a Page or a section of the Platform that defines the “context” of the Element such as “Form” or a specific Menu.

Example: in Workday, Worklets are common ways to identify the location of the element.

Analyzing Engaged Elements in Insights

Once an Engaged Element is saved, it is available in Insights as a Tracked Event of type Engaged Element. These Tracked Events can be used as any Tracked Events to create Funnels, to be analyzed in the Tracked Events Dashboard, or even used to Filter sessions.

Keep in mind that only published Engaged Elements will collect data. Draft, modified, and archived Engaged Elements will still show in Insights with the relevant notification.

Deleted Engaged Elements will not be shown.

Supported Platforms

The following platforms currently support the use of Insights Engaged Elements:

  1. SuccessFactors
  2. Workday
  3. Salesforce Classic
  4. Microsoft Dynamics

Best practices

  1. For best performance try to reduce the number of Engaged Elements in the “All site” category.
  2. You can create an additional page that answers a specific regex in the application, like so:
    1. Click on the Engaged Element to open the settings.
    2. In the Interaction Tab – click on “open the page’s settings
    3. Click on Edit URL Role (Tip: Use Like with combinations of asterisk signs ( * ) to define a more dynamic URL)
    4. Click on Save.

Limitations

Engaged Elements is currently not available when using:

  1. Editor Segments
  2. On-Premise
  3. EU data center

The number of Engaged Elements is limited to 20 per Page to ensure the best Site Performance results.

Data Latency: Any change of Engaged Elements in the Editor (creation, modification, or publish state change) might take up to 30 minutes to sync on Insights.

By design, only the following Rule Types are allowed for defining a page. This is to ensure the Rules are used to define a location (Where to search for the element) and not the end-user or time (Who? When? type of Rules are not supported):

  1. URL
  2. On Screen Element
  3. jQuery Element
  4. Workday (if workday plugin is installed)
  5. Salesforce (for sfVars)
  6. Segments reuse
Please Note:

No PII is collected from the element attributes as in DXA. The risk for PII collection is the same as in WalkMe Engagement (be aware that PII can still be apparent in URLs, page titles, End User identifiers or Analytics Properties. See Insights: Prevent collecting PII using Insights Privacy Settings)

Was this article helpful?

Related Articles