Segmentation allows you to display your WalkMe content to different user groups. You can push items to specific users or remove items from a user's view according to the Segmentation conditions you define.
Segmentation allows you to create different groups of users so you can display the right WalkMe content to the right end users.
Watch the video to understand the user experience with Segmentation.
| Key Takeaways |
|---|
Segmentation allows to decide when to display WalkMe content to different types of users. You can push items to specific users or remove items from a user's view according to the Segmentation conditions you define. |
Segmentation allows to create Segmentation Tags to decide which WalkMe content to display to which types of users. Sometimes, content you create should only show depending on the type of user. Common examples are managers or non-managers, HR, Support, etc.
Before any WalkMe content can appear in the Player Menu or on the screen, WalkMe will first evaluate if the Segmentation you create is true.
Segmentation is created using the Condition Builder. As a result, you can create Segments based on all conditions, including Date, Variable, Element On-Screen, or Current URL.
The figure shows how you can set Segmentation conditions such as variables through the Condition Builder.
All WalkMe application types with the exception of Help Desk and Live Chat can be Segmented to appear for target audiences: Smart Walk-Thrus, Launchers, Onboarding Tasks, Resources, Shuttles, Surveys, SmartTips, and ShoutOuts.
Common Groups of Users
Purposeful Segmentation is an important part of builds. If WalkMe items aren't relevant to certain users or under certain conditions end users often don't event need to see them!
Removing them for view will allow people focus on the available WalkMe content and reduce clutter on the screen and in the WalkMe Menu. Different use cases may require you to show or hide certain pieces of content depending on the user's:
| Segmentation Use Cases | Description |
|---|---|
| Role | Example: Managers vs. Individual Contributors. Maybe the managers of your company have been asked to complete a new process to fill out reviews of their direct reports. Non-managers don't need to see related content. |
| Department | Example: Support vs. Finance. Finance team members likely don't need to be shown a Smart Walk-Thru about a new product feature customers will use. |
| Geographic Location | Example: United States vs. France. There may be different laws in these countries, so messaging in a SmartTip needs to be different depending on where the user lives. |
| Permissions | Admins vs. Content Viewers. Not all users have the same level of permission access in a platform. Admins may benefit from Resources for guidance on back-end processes. |
| Feature Access | Example: Reporting Feature. Contractually, not all users may have access to a reporting feature. User's who can't access it shouldn't see a ShoutOut about a new tool on the reporting dashboard. |