WalkMe Data

Use Cases

WalkMe Data helps tailor user experiences by recording browser-based activity. You can use it to:

• Track that a user has completed an action and display additional items such as Smart Walk-Thrus, launchers, or ShoutOuts
• Record which steps a user completed so a Smart Walk-Thru can resume where they left off
• Mark when a process is sent for review and show content after approval
• Count how many times a user performs an action, such as logins or form submissions

Set WalkMe Data

WalkMe Data can be created or updated from different WalkMe items, depending on your build needs.

Each method stores data locally in the browser and can later be used in the Rule Engine to segment users, branch flows, or trigger content.

WalkMe Data rules

Learn how to test for the presence or value of WalkMe Data in the Rule Engine to trigger logic, show content, or branch flows.

To build a rule using WalkMe Data:

1. Open the Rule Engine
2. Select User Data as the rule type
3. Choose WalkMe Data as the data type
4. Specify the key and value to test for

For example, a rule could state: “WalkMe Data value equals 3” to trigger content after three visits.

Set WalkMe Data steps (Smart Walk-Thru)

You can set WalkMe Data directly from a Smart Walk-Thru by adding a Set WalkMe Data step.

This step stores data based on the user's action and lets you trigger follow-up content or resume a Smart Walk-Thru later.

Set WalkMe Data Flow Steps

WalkMe Data in ShoutOuts

You can also set WalkMe Data from the Visual Designer when configuring a ShoutOut.

1. Select an element with an action (such as a button or image)
2. Open the Action tab
3. Turn on Set WalkMe Data
4. Fill out the properties

This allows WalkMe to track when users interact with a ShoutOut and use that data in rules or segmentation.

Measuring Repeated Actions

To track how often a user performs the same action, use multiple WalkMe Data steps with the same key:

1. Create a WalkMe Data key such as wm-login-count and set the value to 1 the first time the action occurs
2. Add another WalkMe Data step using the same key and set the value to 2, and so on for each repetition
3. In your Smart Walk-Thru, create a Split step that checks for the stored value — for example, “WalkMe Data value equals 1” — to branch logic after the first or second occurrence
4. Use these stored values to trigger other content such as ShoutOuts, launchers, or Smart Walk-Thrus that appear after a specific number of actions

Continue increasing the value by one each time the action repeats to track multiple attempts or completions.

Best Practices

• Use the prefix wm- for key names to avoid conflicts with site cookies
• Avoid spaces in key names
• Use Yes as the value for single-use actions
• Use numeric values for counters
• Always test data persistence in test or a staging environment
• Store data only as long as needed for your use case

Technical Notes

Browser storage

Avoid using Incognito or private browsing when testing WalkMe Data, since cookies won't persist after the session ends.

Duration

For testing, use short durations such as a few minutes to confirm that data updates correctly. Once verified, update to the intended duration.

Quality Assurance (QA)

Use Flow Tracker to confirm that the WalkMe Data step triggered and saved correctly.

ShoutOut limitation

WalkMe Data can be set only for ShoutOuts created with dynamic layout. Classic layouts do not support this functionality.

Known limitation

If server storage is enabled and the expiry time is set to less than one hour, data will not be sent to WalkMe's servers.