Which two types of WalkMe content can make up an Onboarding Task?
SmartTips and Launchers
Smart Walk-Thrus and Resources
Resources and Shuttles
Smart Walk-Thrus and Shuttles
AnOnboarding Taskin WalkMe is a collection of steps or content designed to guide users through a set of actions to complete an onboarding process. The two types of WalkMe content that can be included in an Onboarding Task areSmart Walk-Thrus, which provide step-by-step guidance through processes, andResources, which link to help articles or external documentation to support onboarding. These content types are versatile and align with the goal of guiding users through critical tasks.
The other options are incorrect:
SmartTips and Launchers(A) are not part of Onboarding Tasks; SmartTips are field-specific, and Launchers trigger other content.
Resources and Shuttles(C) are partially correct, but Shuttles only navigate to pages, not guide through tasks.
Smart Walk-Thrus and Shuttles(D) are also partially correct, but Shuttles are not task components.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.8: Onboarding Tasks):
“Onboarding Tasks consist of Smart Walk-Thrus, which guide users through processes, and Resources, which provide supplementary help content to complete onboarding.”
The courseGetting Started with Building WalkMe Solutionsstates:
“Build Onboarding Tasks using Smart Walk-Thrus for process guidance and Resources for additional support, ensuring users have the tools to complete onboarding.”
Option B, Smart Walk-Thrus and Resources, is the correct answer.
Which steps would you take to publish items to Production that you add to the user-facing Menu in the Menu Organizer?
Adding items to the user-facing Menu are automatically published to Production.
Changing the name of an added item in the Menu Organizer publishes it to Production.
Manually publishing the item to Production after adding it to the Menu Organizer and saving it.
Adding an item to the user-facing Menu and clicking Save automatically publishes it to Production.
In WalkMe, adding items to the user-facing Menu via the Menu Organizer does not automatically publish them to Production. After adding and saving items in the Menu Organizer, Builders mustmanually publishthe changes to the Production environment using the WalkMe Editor’s publish feature. This ensures that only reviewed and tested content is deployed, maintaining control over what end users see.
The other options are incorrect:
Option Ais wrong because adding items requires manual publishing.
Option Bis incorrect, as renaming doesn’t trigger publishing.
Option Dis false, as saving in the Menu Organizer doesn’t publish to Production.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.5: WalkMe Menu):
“After adding items to the Menu Organizer and saving changes, manually publish the updated Menu to Production using the Editor’s publish feature to make it available to end users.”
The courseGetting Started with Building WalkMe Solutionsstates:
“To deploy Menu changes, add and save items in the Menu Organizer, then manually publish them to Production to ensure controlled deployment.”
Option C correctly describes the publishing process.
Your product team released a new feature last month and would like to get end user feedback within Insights. Which of the options below is the best approach?
Create a Survey and place it in the WalkMe Menu.
Use a Shuttle linking to a Google Form with detailed questions.
Add a ShoutOut on the feature page that activates a WalkMe Survey with multiple questions.
Use a 3rd party survey tool and send it to your users in an automated email campaign.
To collect end user feedback within WalkMe Insights, the most effective approach is to use WalkMe’s native Survey tool, as it integrates directly with Insights for seamless data collection and analysis. Placing aShoutOut on the feature pagethat activates a WalkMe Survey with multiple questions ensures high visibility and context-specific engagement, as users are prompted to provide feedback while interacting with the new feature. This method leverages WalkMe’s analytics to track responses and correlate them with user behavior, providing actionable insights.
The other options are less optimal:
A Survey in the WalkMe Menu(A) is less targeted, as users may not proactively access it.
A Shuttle to a Google Form(B) lacks integration with Insights, making data analysis cumbersome.
A 3rd party survey tool via email(D) is disconnected from the feature context and WalkMe’s analytics.
Extract from Official WalkMe Documentation:
According to the WalkMe Insights User Guide (SAP WalkMe Digital Adoption Consultant StudyGuide, Section 3.5: Surveys):
“WalkMe Surveys, when triggered by a ShoutOut on a relevant page, are ideal for collecting contextual feedback. Responses are tracked in Insights, enabling analysis of user sentiment and feature adoption.”
The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:
“For feature-specific feedback, use a ShoutOut to launch a WalkMe Survey on the feature page. This ensures users provide input in context, with data seamlessly captured in Insights for analysis.”
Option C is the best approach for collecting feedback within Insights.
The Dynamic Layout of a ShoutOut in the Editor consists of which three layers? Note: There are 3 correct answers to this question.
Frame
Canvas
Z-index
Widget
Player
The Dynamic Layout of a WalkMe ShoutOut in the Editor is composed of three layers: theFrame,Canvas, andWidget. TheFramedefines the outer structure and positioning of the ShoutOut (e.g., size and placement on the screen). TheCanvasis the content area where text, images, or buttons are placed. TheWidgetincludes interactive elements, such as the call to action button or close button, that users can interact with. These layers work together to create a customizable and visually appealing ShoutOut.
The other options are incorrect:
Z-index(C) is a CSS property that controls stacking order, not a layer of the ShoutOut’s layout.
Player(E) refers to the WalkMe Player, which delivers content but is not part of the ShoutOut’s internal structure.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.9: ShoutOuts):
“The Dynamic Layout of a ShoutOut consists of three layers: the Frame, which sets the structural boundaries; the Canvas, which holds the content; and the Widget, which includes interactive components like buttons.”
The courseAdvancing Your Skills in Building WalkMe Solutionselaborates:
“When designing ShoutOuts, understand the Dynamic Layout’s three layers—Frame, Canvas, and Widget—to effectively customize appearance and functionality for user engagement.”
Options A, B, and D are the correct layers of a ShoutOut’s Dynamic Layout.
What is the primary difference between Global Level Design and Local Level Design in WalkMe?
Global Level Design only affects ShoutOuts, while Local Level Design affects SmartTips andLaunchers.
Global Level Design applies to all WalkMe content, while Local Level Design applies to specific items and can override global settings.
Global Level Design requires CSS knowledge, while Local Level Design does not for certain elements.
Global Level Design is only available for administrators, while Local Level Design is available for all users.
In WalkMe, Global Level Design refers to styling and configuration settings that apply universally to all WalkMe content within an account, such as default fonts, colors, or balloon styles. These settings ensure consistency across deployables like Smart Walk-Thrus, ShoutOuts, and Launchers. Local Level Design, on the other hand, allows Builders to customize the appearance or behavior of specific WalkMe items (e.g., a single ShoutOut or SmartTip), overriding global settings when needed. This hierarchy enables flexibility while maintaining a cohesive brand identity.
The other options are incorrect:
Option Ais wrong because Global Level Design affects all content types, not just ShoutOuts, and Local Level Design applies to any item, not only SmartTips and Launchers.
Option Cis misleading, as both design levels can be configured without CSS knowledge using the WalkMe Editor’s UI, though advanced customization may involve CSS.
Option Dis incorrect, as both design levels are accessible to Builders with appropriate permissions, not restricted by user role.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.6: Design and Customization):
“Global Level Design sets the default styling and behavior for all WalkMe content in an account, such as fonts, colors, and balloon positioning. Local Level Design allows customization of individual items, overriding global settings to meet specific needs.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“Use Global Level Design to enforce brand consistency across all WalkMe deployables. For unique requirements, apply Local Level Design to specific items, which takes precedence over global configurations.”
Option B correctly captures the primary difference between Global and Local Level Design.
You are analyzing your Smart Walk-Thru steps and see significant drop-off following a Wait For step. What should you investigate to try to get to the root of the issue?
Update your step triggers.
Look at your Smart Walk-Thru step initiators.
Look at your Wait For condition rules.
Remove the step completely.
A Wait For step in a Smart Walk-Thru pauses the flow until specific conditions are met, such as an element appearing on the screen or a page load completing. If users are dropping off after a Wait For step, the most likely cause is that the condition rules are not being satisfied, causing the flow tostall. Investigating the Wait For condition rules—such as checking if the targeted element is correctly identified, the condition is achievable, or the timeout period is sufficient—helps identify and resolve the issue.
The other options are less relevant:
Updating step triggers(A) applies to user actions that advance steps, not Wait For conditions.
Looking at step initiators(B) relates to how the Smart Walk-Thru starts, not why users drop off mid-flow.
Removing the step completely(D) is a last resort and doesn’t address the root cause.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.2: Smart Walk-Thrus):
“Wait For steps pause a Smart Walk-Thru until predefined conditions are met, such as an element becoming visible. If users drop off at a Wait For step, review the condition rules to ensure they are correctly configured and achievable within the expected timeframe.”
The courseAdvancing Your Skills in Building WalkMe Solutionsadvises:
“Significant drop-off at a Wait For step often indicates misconfigured condition rules, such as an element not appearing as expected. Use the Flow Tracker and Insights to analyze and adjust these rules.”
Option C is the correct choice, as it focuses on investigating the Wait For condition rules to address the drop-off issue.
How does WalkMe help organizations enforce policy and compliance requirements?
By automatically restricting employees from using external software
By monitoring employees through real-time video feeds
By disabling access to all non-compliant employees
By displaying pop-ups for policy acknowledgment and using invisible Launchers to block sensitive fields
WalkMe supports organizations in enforcing policy and compliance requirements by providing tools to guide users and prevent non-compliant actions. Specifically, it usespop-ups for policy acknowledgment(e.g., via ShoutOuts or Smart Walk-Thrus) to ensure users confirm understanding of policies, andinvisible Launchersto block sensitive fields, preventing unauthorized interactions without altering the underlying application. This approach ensures compliance while maintaining a seamless user experience.
The other options are incorrect:
Restricting external software(A) is not a WalkMe capability; it focuses on in-app guidance.
Monitoring via video feeds(B) is unrelated to WalkMe’s functionality.
Disabling access to non-compliant employees(C) is too extreme and not a WalkMe feature.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: WalkMe Fundamentals):
“WalkMe enforces compliance by displaying policy acknowledgment pop-ups through ShoutOuts or Smart Walk-Thrus and using invisible Launchers to block sensitive fields, ensuring adherence to regulations.”
The courseWalkMe Fundamentalsstates:
“To support compliance, WalkMe uses tools like pop-ups for policy confirmation and invisible Launchers to restrict access to sensitive areas, promoting secure user behavior.”
Option D accurately describes how WalkMe enforces policy and compliance.
What is the correct order of operations for determining if WalkMe content should appear on the page?
Segmentation > Web page loads > Individual item conditions
Web page loads > Segmentation > Individual item conditions
Start Points > Web page loads > Segmentation
Individual item conditions > Segmentation > Web page loads
WalkMe follows a specific sequence to determine whether content should appear on a page:
Web page loads: The page must load for WalkMe to initialize and evaluate content.
Segmentation: Segmentation rules (e.g., user role, behavior) determine if the content is relevant to the user.
Individual item conditions: Specific conditions for each content item (e.g., element visibility, URL rules) are checked to finalize display.
This order ensures that WalkMe efficiently evaluates global applicability before checking item-specific criteria, optimizing performance and relevance.
The other options are incorrect:
Option Areverses the order of page load and segmentation.
Option Cincludes Start Points, which are specific to Smart Walk-Thrus, not general content display.
Option Dplaces individual conditions first, which is illogical as the page must load first.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.6: Content Display Logic):
“WalkMe content display follows this order: (1) Web page loads, initializing WalkMe; (2) Segmentation rules filter based on user attributes; (3) Individual item conditions, such as URL or element rules, determine final display.”
The courseGetting Started with Building WalkMe Solutionsexplains:
“The sequence for content display is web page load, followed by segmentation to target users, and then individual item conditions to confirm content relevance.”
Option B correctly outlines the order of operations.
Which of the following options would be appropriate to create a Segment in the Segmentation center? Note: There are 3 correct answers to this question.
IP Address
Autoplay on 1 page
Department
Geographic location
User Role
The WalkMe Segmentation Center allows Builders to create Segments to target content to specific user groups based on attributes. Appropriate options include:
Department(C): Segments can target users based on their department (e.g., Sales, Finance).
Geographic location(D): Segments can use location data to tailor content by region or country.
User Role(E): Segments can target roles (e.g., Admin, User) for role-specific guidance.
The other options are incorrect:
IP Address(A) is not a standard segmentation attribute in WalkMe.
Autoplay on 1 page(B) is a content trigger, not a user segment.
Extract from Official WalkMe Documentation:
According to the WalkMe Admin Center User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 3.3: Segmentation):
“Segments in the Segmentation Center can be based on attributes like Department, Geographic Location, and User Role, enabling targeted content delivery.”
The courseGetting Started with Building WalkMe Solutionsstates:
“Create Segments using criteria like Department, Location, or Role to ensure content is relevant to specific user groups.”
Options C, D, and E are appropriate for Segments.
Which of the options below is a use case for when to use jQuery? Note: There are 3 correct answers to this question.
To redesign the entire layout of the WalkMe balloons.
If the WalkMe element selector algorithm is not consistently identifying your element.
To close the WalkMe menu and start an Onboarding task.
To grab a dynamic value from an on-screen element and incorporate it into a ShoutOut for a personalized experience.
To target a very specific element on your website.
jQuery is a powerful tool in WalkMe for advanced element targeting and dynamic interactions. The correct use cases are:
If the WalkMe element selector algorithm is not consistently identifying your element(B): jQuery selectors provide precise targeting when WalkMe’s default algorithm struggles with dynamic or complex elements.
To grab a dynamic value from an on-screen element and incorporate it into a ShoutOut for a personalized experience(D): jQuery can extract values (e.g., a username) for use in personalized content.
To target a very specific element on your website(E): jQuery allows fine-tuned selectors for elements with unique attributes or structures.
The other options are incorrect:
Redesigning the entire layout of WalkMe balloons(A) is done via Global/Local Design settings, not jQuery.
Closing the WalkMe menu and starting an Onboarding task(C) uses WalkMe’s native APIs or rules, not jQuery.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.7: jQuery Selectors):
“Use jQuery in WalkMe to target specific elements when default selectors fail, extract dynamic values for personalization (e.g., in ShoutOuts), or address complex DOM structures requiring precise element identification.”
The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:
“jQuery is essential for scenarios like inconsistent element detection, grabbing dynamic data for personalized content, or targeting unique elements with custom selectors.”
Options B, D, and E are valid jQuery use cases.
When doing quality assurance and testing content, which of the options below should we be looking for? Note: There are 3 correct answers to this question.
Page load time is under ten seconds.
Content appears as expected.
Balloons are not blocking important site elements.
Smart Walk-Thru triggers work as expected.
The website’s background color matches the corporate branding.
Quality assurance (QA) and testing of WalkMe content focus on ensuring that the content functions correctly, displays appropriately, and enhances the user experience without causing disruptions. The key aspects to check include:
Content appears as expected(B): Verify that WalkMe content (e.g., SmartTips, ShoutOuts) displays with the correct text, styling, and positioning as designed in the Editor.
Balloons are not blocking important site elements(C): Ensure that WalkMe balloons (e.g., Smart Walk-Thru steps or SmartTips) do not obscure critical UI elements, such as buttons or forms, to maintain usability.
Smart Walk-Thru triggers work as expected(D): Confirm that triggers (e.g., clicks, page loads) initiate Smart Walk-Thru steps correctly, ensuring smooth guidance.
The other options are incorrect:
Page load time under ten seconds(A) is a website performance metric, not a WalkMe QA responsibility.
Website’s background color matching corporate branding(E) is outside WalkMe’s scope, as it pertains to the website’s design.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.4: Quality Assurance):
“During QA, verify that content displays correctly, balloons do not block critical UI elements, and Smart Walk-Thru triggers function as intended. These checks ensure a seamless user experience.”
The courseGetting Started with Building WalkMe Solutionsstates:
“QA involves confirming that WalkMe content appears as designed, does not obstruct important page elements, and that triggers for Smart Walk-Thrus execute reliably.”
Options B, C, and D are the correct aspects to focus on during QA.
What is WalkMe known as the leading provider of?
Digital Application Platform
Dynamic Assistance Provider
Direct Adoption Program
Digital Adoption Platform
WalkMe is recognized as the leading provider of aDigital Adoption Platform (DAP), which helps organizations ensure employees and customers effectively use digital tools and platforms. A DAP provides tools like in-app guidance, analytics, and automation to enhance user adoption, streamlineprocesses, and reduce friction in digital experiences.
The other options are incorrect:
Digital Application Platform(A) refers to app development platforms, not adoption.
Dynamic Assistance Provider(B) is not an industry term.
Direct Adoption Program(C) is not a recognized category.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: Introduction to Digital Adoption):
“WalkMe is the leading provider of a Digital Adoption Platform (DAP), delivering solutions that drive effective use of digital platforms through guidance and analytics.”
The courseGetting Started with Building WalkMe Solutionsstates:
“As a Digital Adoption Platform, WalkMe empowers organizations to maximize software adoption and user efficiency with tools like Smart Walk-Thrus and Insights.”
Option D, Digital Adoption Platform, is the correct answer.
When building SmartTips with multi-language support, which practice should you avoid to ensure compatibility?
Using language-independent element identifiers
Using the Customize tab for SmartTip text
Using "Text Is" rules within the Rule Engine
Adding inline CSS styles for language-specific elements
When building SmartTips with multi-language support, it’s critical to ensure compatibility across languages. The practice to avoid is using"Text Is" ruleswithin the Rule Engine, as these rules rely on specific text values that may change depending on the language. For example, a rule checking if a button’s text is “Submit” in English will fail in Spanish where the text might be “Enviar,” breaking the SmartTip’s functionality. Instead, use language-independent identifiers, such as element IDs or classes, to ensure rules are not affected by language variations.
The other options are acceptable or recommended:
Using language-independent element identifiers(A) is a best practice, as it ensures consistent targeting across languages.
Using the Customize tab for SmartTip text(B) is standard for defining multi-language content.
Adding inline CSS styles for language-specific elements(D) is permissible, though it should be used cautiously to avoid conflicts.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.8: Multi-Language Support):
“Avoid using ‘Text Is’ rules in the Rule Engine for multi-language SmartTips, as text-based rules are language-dependent and may fail when content is translated. Use language-independent identifiers like IDs or classes for reliable targeting.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“When configuring SmartTips for multi-language support, steer clear of ‘Text Is’ rules, which tie conditions to specific text strings that vary by language, causing compatibility issues.”
Option C, using "Text Is" rules, is the practice to avoid.
How would you write a jQuery selector for the following HTML element:
div#button
#blueBtn
div#blueBtn
div.blueBtn
In jQuery, selectors are used to target HTML elements based on their tag, class, ID, or other attributes. The HTML element
The other options are incorrect or less optimal:
Option A(div#button) incorrectly uses the class name as an ID.
Option B(#blueBtn) is valid but less specific, as it doesn’t confirm the element is a
Option D(div.blueBtn) targets the class, which is less specific than the ID and could match multiple elements.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.7: jQuery Selectors):
“When writing jQuery selectors for WalkMe, prioritize specificity and reliability. For elements with unique IDs, use the format tag#id (e.g., div#blueBtn) to ensure accurate targeting while clarifying the element type.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“For an HTML element like
Option C, div#blueBtn, is the correct jQuery selector.
A brokerage firm is interested in implementing WalkMe to address an issue their customers face when transferring money from their online accounts to their banks. They have heard that users do not know where to go on the platform to complete this, but once they reach the appropriate page, they know how to fill out the forms correctly without errors. Of the listed WalkMe apps, which would best address the issue?
Resource to explain how to complete all parts of the process
Shuttle to bring the user to the page
SmartTips on the fields of the page
ShoutOut to announce that this must be completed
The issue described is that users struggle to navigate to the correct page for transferring money, but once there, they can complete the forms without errors. AShuttleis the most appropriate WalkMe solution, as it directly addresses navigation challenges by guiding users from any page to the specific target page (e.g., the money transfer page) via a clickable link or button. Shuttles are designed to simplify navigation, making them ideal for this use case where the primary pain point is finding the right page.
The other options are less suitable:
Resource(A) provides detailed instructions, but the issue is navigation, not understanding the process.
SmartTips(C) offer field-level guidance, which is unnecessary since users already know how to fill out the forms.
ShoutOut(D) is for announcements and doesn’t directly solve the navigation problem.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.7: Shuttles):
“Shuttles are designed to guide users to a specific page or section of an application, addressing navigation challenges by providing a direct path to the target location.”
The courseGetting Started with Building WalkMe Solutionsstates:
“For scenarios where users struggle to find the correct page, such as initiating a process like a money transfer, a Shuttle is the most effective tool to direct them to the destination.”
Option B, a Shuttle, best addresses the navigation issue.
What role does WalkMe(X) play in Digital Adoption?
It provides AI-powered assistance within workflows to enhance user experience
It creates new software applications automatically
It restricts access to applications that users struggle with
It replaces the need for any human training sessions
WalkMe(X)is an AI-powered component of WalkMe’s Digital Adoption Platform that providesAI-powered assistance within workflowsto enhance the user experience. It offers contextual suggestions, automates repetitive tasks, and delivers personalized guidance, making digital platforms easier to use and improving adoption rates.
The other options are incorrect:
Creating new software(B) is not a WalkMe(X) function; it enhances existing applications.
Restricting access(C) is not its role; it focuses on assistance, not restrictions.
Replacing human training(D) is an overstatement; it supports, not eliminates, training.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: WalkMe Fundamentals):
“WalkMe(X) leverages AI to provide contextual, in-workflow assistance, enhancing user experience by delivering personalized guidance and automation.”
The courseWalkMe Fundamentalsstates:
“WalkMe(X) plays a critical role in Digital Adoption by using AI to assist users within workflows, improving efficiency and ease of use.”
Option A correctly describes WalkMe(X)’s role.
In the Editor, a Shuttle has a full green circle next to it when looking at the Production environment. How would you describe the status of this Shuttle?
Draft mode in Test
Archived in Production
Published to Production but has been modified
Published to Production
In the WalkMe Editor, afull green circlenext to a content item, such as a Shuttle, in the Production environment indicates that the item isPublished to Productionand is live for end users. This status confirms that the Shuttle has been successfully deployed without subsequent modifications or archiving.
The other options are incorrect:
Draft mode in Test(A) would show a different icon (e.g., gray or yellow) in the Test environment.
Archived in Production(B) would show an archived status, not a green circle.
Published but modified(C) would display a modified indicator, not a full green circle.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.10: Publishing and Status):
“A full green circle in the Production environment indicates that the content item, such as a Shuttle, is published and active for end users.”
The courseGetting Started with Building WalkMe Solutionsstates:
“Check the status icon in the Editor: a full green circle in Production means the content is live and published without pending changes.”
Option D correctly describes the Shuttle’s status.
You have received some feedback that your end users are having issues completing a Smart Walk-Thru that you built. Where are the best places to analyze where users are having issues? Note: There are 2 correct answers to this question.
Look in the WalkMe Player Menu.
Look at the Smart Walk-Thru steps in the Editor.
Look at the percent of users that played Smart Walk-Thrus.
Look at the Smart Walk-Thru step analysis in Insights.
To diagnose issues with a Smart Walk-Thru, Builders should analyze both the configuration of theSmart Walk-Thru and user interaction data. The best places are:
Smart Walk-Thru steps in the Editor(B): Reviewing the steps in the WalkMe Editor, along with using tools like the Flow Tracker, helps identify misconfigured triggers, conditions, or elements that may cause user issues.
Smart Walk-Thru step analysis in Insights(D): Insights provides detailed analytics on step completion rates, drop-off points, and errors, pinpointing exactly where users encounter difficulties.
The other options are less effective:
WalkMe Player Menu(A) is for end users to access content, not for analyzing issues.
Percent of users that played Smart Walk-Thrus(C) gives overall engagement but lacks step-specific insights.
Extract from Official WalkMe Documentation:
According to the WalkMe Insights User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 3.2: Analytics and Reporting):
“The Smart Walk-Thru step analysis in Insights shows completion rates and drop-off points, helping Builders identify where users struggle. Combine this with Editor-based troubleshooting using Flow Tracker to resolve issues.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“To troubleshoot Smart Walk-Thru issues, review step configurations in the Editor for errors and analyze step-level data in Insights to understand user behavior and pinpoint problem areas.”
Options B and D are the best places to analyze user issues.
Copyright © 2014-2025 Examstrust. All Rights Reserved