Setting Up Unique User Identifiers

Welcome to the Certified WalkMe Builder II program! Let's get started!

Understanding the various technical configurations you can make in the WalkMe Editor is an important part of ensuring your WalkMe content will work as expected.

We will start with understanding what a Unique User Identifier is and how to set one up.

When building your WalkMe Solutions, you need to consider how you would like to track your end users. Configure your Unique User Settings so WalkMe Insights will be able to show you data related to your WalkMe Implementation. WalkMe could track how many (or possibly who - if you would like) users complete specific actions.

It could be a good ideal to set it up so that your WalkMe analytics can be collected with the same end user tracking method as your platform, providing a close integration between WalkMe Insights and your site by identifying users in the same way.

Setting up the Unique User ID will allow you to do things like:

• Track the number of unique users that see WalkMe on a monthly basis.
• Get accurate data on Insights, WalkMe's analytics platform.
• Check an individual’s progress and that they are reaching relevant Goals with WalkMe.
• Set up an Onboarding Task list that must be completed by each individual user - and track who is completing Tasks.
• Configure Smart Walk-Thrus and ShoutOuts to play automatically under specific conditions.

The following options are available to set as a unique user identifier to track each end user's activity:

1. IDP Integration (Recommended Method) - IDP integration can be used to validate end users' identities, enrich content segmentation capabilities, and expand on user behavior monitoring
   • IDP is the most accurate and reliable way to identify end users, and when possible, it is the method recommended by WalkMe to use for all new systems.
   • This method provides one reliable and secure User ID across all systems without the need to define a unique user ID for each system with different variables.
   • Reach out to your WalkMe Contact for more information.
   • IDP Integration Support Article
2. WalkMe ID - A dynamically created ID when a user lands on a WalkMe page, which is stored in the users browser cache
   • WalkMe ID is particularly useful for collecting large numbers of users, specifically for external sites. WalkMe ID is not ideal for internal sites where you want WalkMe to remember your user.
   • This method does not allow you to personally identify users, since the user identifier will be cleared if the user uses a different browser or clears cache. They will show as a new user in Insights and any Onboarding tasks they have completed will be reset.
3. Cookie - If your site is configured with Cookies, you can use them to uniquely identify users
   • To use cookies, you will need to set up cookies on your site and supply the name of the cookie in the unique user settings in the editor.
   • This method does not allow you to personally identify users, since the user identifier will be cleared if the user uses a different browser or clears cache. They will show as a new user in Insights and any Onboarding tasks they have completed will be reset.
4. jQuery Selector - Track unique users by an element present on the user's screen
   • This method requires the same element to be visible on ALL pages, and will work across different browsers or if the user clears cache.
   • For example, if you have WalkMe present on your login page, but the jQuery selector is not available on this page, a WalkMe ID will instead be generated for your user
5. Variable - A JavaScript variable correlated to User ID or Name
   • This is the recommended method for user tracking as the variable does not need to be present on every page, and is unaffected if the user clears cache or uses a different browser.
   • These variables can be manually created by your development team for your site
   • When using IDP is not possible, variables are the recommended method for user identifiers. The variable utilized in favor of the UUID should be available on every page.
6. Salesforce ID - Specifically for Salesforce implementations, an 18 digit Salesforce ID

   This method is similar to a WalkMe ID, and does not allow you to personally identify users. If using Salesforce, it is recommended to use the variable UserContext.userName which usually returns the user's email address.

7. None - Do not track unique users

   When none is selected as your user identifier, Onboarding tasks will not cross off, Auto Play cannot be used, and a new ID will be generated each time a new session begins.

Pro Tip

To check if your UUID is loading as intended on your platform, within the developer console, you can run the following command:

_walkMe.getEndUserID()

Note

In Insights, if you find that your deployables are showing more plays than you expect or the numbers for your content appear off, verify that your Unique User Identifier is consistent and that WalkMe is able to recognize your defined Unique User Identifier.

Note

Changing your UUID will reset all Insights data, Onboarding Tasks and AutoPlays. Please proceed with caution if you decide to do so.

1. Click the Settings icon at the top right of the Editor.
2. Under the "SETTINGS" section, select System settings.
3. On the General tab under the Unique User Settings section, choose a User Identifier option from the dropdown.
4. Supply additional information if you selected Variable, jQuery, or Cookie.
5. Optionally, you can add an Expected format for validation of the user identifier.
6. Click Save.
7. Publish Settings to the Environment(s) where you would like to identify your users by this Unique User Identifier.

Note

If WalkMe cannot immediately find the defined Unique User Identifier on the initial load of the page, it will generate a WalkMe ID, which looks like a generated string of letters and numbers, to identify the user.

Next, we will look at what a single page application is and why it's so important.