Reviewing Technical Considerations

Analyzing WalkMe Loading and Evaluation Processes

Objective

After completing this lesson, you will be able to analyze WalkMe load processes and evaluation types to optimize content performance and troubleshooting.

How WalkMe Works

Link_DisclaimerWalkMe is an overlay that loads on top of a web platform.

It is critical to have a high level understanding of how WalkMe loads on the page. This will empower you to create content that functions as intended and/or explain it to colleagues as needed.

Watch the video to learn the technical explanation of how WalkMe works.

Key Takeaways

WalkMe loads after your web page finishes loading, using a snippet or browser extension. This asynchronous behavior ensures WalkMe doesn’t slow down or interfere with your site’s primary load performance.

WalkMe immediately evaluates page conditions to decide which content to display.

Some WalkMe functions continue evaluating even after the page load. WalkMe keeps monitoring certain settings dynamically to make sure relevant content appears when it's needed, ensuring a responsive user experience.

WalkMe in Action

Here's a simplified version of what those steps looks like in practice:

  1. Web page loads
  2. WalkMe loads via the snippet or extension
  3. WalkMe evaluates conditions
  4. Content appears for end users
Banner for Two Types of Evaluation

WalkMe loads asynchronously, meaning that it doesn't hold the site in order to load and therefore shouldn't impact the end user experience. Even with this architecture, we want to be absolutely sure that we build WalkMe solutions as efficiently as possible to maximize the end user experience.

There are two phases of evaluation WalkMe will run: Page Load Evaluation and Continuous Evaluation.

Page Load Evaluation

The first phase of evaluation is the Page Load Evaluation. This occurs when a web page loads or there is a page refresh.

WalkMe checks all the conditions to see which content it should try to load. There is a specific hierarchy of which setting WalkMe checks first which can help understand where to apply certain rules or troubleshoot.

  1. First, WalkMe checks any Segmentation tags.
  2. Next, WalkMe checks Display Conditions ("local segmentation") for individual items.
  3. And finally, it checks engagement rules for those items (think: autoplay rules).

Why is this important? The number of page load evaluations and the way they are configured can impact the speed at which WalkMe loads upon page load.

A flowchart showing the page load evaluation logic, which sequentially checks segmentation tags, display conditions, and engagement rules to determine if content should be shown or autoplayed.

Continuous Evaluation

The second phase of evaluation is Continuous Evaluation. This occurs after the web page and content initially loads.

There are three things that WalkMe will continuously evaluate to see if content should appear after page load and/or track analytics:

  1. Goals. For Goals in Smart Walk-Thrus, it will continuously evaluate from the time the Smart Walk-Thru is started for up to two hours after. Onboarding Tasks, on the other hand, are constantly evaluated.
  2. Element Behavior settings.
  3. Display Conditions when the "Removal Behavior" setting is active.

Why is this important? The number of continuous evaluations and the way they are configured are important to keep in mind from a performance standpoint.

Image for Continuous Evaluation

Note

If the site is a Single Page Application (SPA), WalkMe checks the page evaluation rules based on the configuration we set in the SPA tab of the Editor.

This is typically configured during the initial technical setup of a platform.

What Works vs. What Does Not Work

With these concepts in mind, let's tackle a not-so-rare mistake Builders have made in the past to get ahead of potential challenges.

The Auto Play Upon Button Click

In the past, some Builders have tried to make a ShoutOut or Smart Walk-Thru automatically show up after the page load evaluation runs. This will not work.

  • Common Example: We want a ShoutOut to automatically appear when the user clicks a specific button.
  • Why it Doesn't Work: Auto play rules are evaluated upon page load - not continuously - so WalkMe will not be checking if the user clicked that button to auto play the ShoutOut. It will never play.
  • Try This Instead: Put an Invisible Launcher on top of the button that activates the ShoutOut as needed.

Watch the video to learn about using Invisible Launchers on top of a button that activates a ShoutOut.

Having a solid understanding of how WalkMe operates will allow you to think critically about what content to create, implement solutions that are effective, and even troubleshoot if something isn't working as expected.