The Unique User ID (UUID) in WalkMe is used to track individual users for analytics and personalization. The most preferred setting to explore first is aVariable, as it allows Builders to leverage an existing user identifier from the application (e.g., a user ID stored in a JavaScript variable), ensuring accurate and reliable user tracking. Variables are typically provided by the application’s authentication system and are more robust than other methods, which may be less consistent or require additional configuration.
The other options are less preferred:
WalkMe ID(A) is a fallback generated by WalkMe but may not align with the application’s user data.
Cookie(B) can be unreliable due to browser restrictions or clearing of cookies.
jQuery(D) is not a standard method for UUID setup; it’s used for element selection, not user identification.
Extract from Official WalkMe Documentation:
Per the WalkMe Admin Center User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.10: User Identification):
“For UUID setup, the Variable method is the most preferred, as it uses an application-provided user identifier (e.g., a JavaScript variable) for accurate tracking. Explore this option first before fallback methods like WalkMe ID or cookies.”
The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:
“Start with the Variable setting for UUID configuration, as it integrates with the application’s user data, providing the most reliable and consistent user tracking for Insights analytics.”
Option C, Variable, is the most preferred UUID setting.
[References:, SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.10: User Identification., WalkMe Admin Center User Guide, “UUID Configuration” Section., Course:Advancing Your Skills in Building WalkMe Solutions, Module 16: User Tracking and Analytics Setup., ]
