Welcome to the
WalkMe Help Center
Please log in to continue
Please log in to continue
With WalkMe Behavioral Segments, you can use WalkMe analytics data to target your content more accurately and display the right message to the right users at the right time.
This feature lets you define a segment based on user characteristics, actions, or attributes collected by WalkMe. You can then apply that segment when building your content.
Create a behavioral segment in the Insights Console and use it as a condition in the WalkMe Editor.
Key Benefits
Near real-time targeting: Evaluate and target users immediately based on their latest events
User-level scoping: Segments are based on user-level activity across the entire selected date range, rather than being limited to a single session
Increased scale: Supports up to 10 segments per system and segment sizes of up to 50,000 users
Unified experience: Create, view, and manage all segments directly in the WalkMe Console

Behavioral segments
A group of users who match a defined set of rules within a chosen date range.
Example: Users who clicked ShoutOut A in the last week. This segment is defined in Insights and later used in the condition builder in the WalkMe Editor
Segmentation
The process of dividing users into groups based on shared behaviors, actions, or attributes. Segments are defined and managed in the editor. Once created, behavior based segments are available as a rule type in the rule engine.
Behavioral segments are designed for high performance and near real-time targeting.
Near real-time calculation: Segments are continuously monitors incoming events and calculated in almost real-time, about every 15-20 minutes
This process determines which users match the segment definition
Processing Status: While a segment is calculating for the first time, its status will show as Pending in the console segments table
During this time, the Calculate button in the segment builder provides a dry run estimate of your audience size based on existing data
The Behavioral Segments page in the console is your central hub for defining and managing user groups based on their activity. From here, you can monitor the status of your segments, perform maintenance, and export user lists for reporting.

Select + Create Behavioral Segment to open the three-step segment builder.
Segments that were created in Insights Classic will have the “Classic” label next to the name![]()
Description: A brief summary of the segment's purpose or specific logic (optional)
System: The specific WalkMe system where the segment is being evaluated
Status: The current state of the segment:
Active: The segment is running and available for use
Pending: The segment is currently being calculated for the first time
Expired: The segment has passed its end date or the fixed date range has concluded
Failed: An error occurred during the data evaluation process
Date Range: The timeframe used for the behavioral rules (for example, Last 30 days, Custom Range)
Evaluation End Date: The date when the segment will stop refreshing and become "Expired"
Rules: The number of individual conditions defined within the segment (up to 5)
Created By: The name of the team member who created the segment
Table icons
Group by Column: You can group columns by values
Click the Group by Column icon to organize the table by a specific value
This collapses the data into a group folder that can be expanded to view the data, making it easier to organize and view your data
Manage Columns: Remove or add columns from the table
Click the Manage columns icon
Select which columns you'd like to have in the table
Click Apply
Export: Click the Export icon to download the file to either CSV or XLSX
Search bar
Use the search bar to quickly find the segments you need
Export segment
Selecting the Export Segment Data icon opens a popup that lets you generate a report of all users currently matching your segment rules
Once you select Export Report in the popup, the file is processed and becomes available for download in the Exports and Subscriptions page in the Reports app
Delete segment
Click the Delete icon to permanently remove the segment
Creating a behavioral segment involves a three-step process:
Info
Evaluation period
Rules
To get started, go to the to the Behavioral Segments page and click the Create Behavioral Segment button.
![]()
Select the System on which the conditions will run.
Systems that have reached the limit of 10 segments will not be selectable
Enter a Name for your segment (mandatory)
Provide a description to define the segment's purpose (optional)
Select Next

Choose a Date range
This defines the data window for user activity
Set an optional Evaluation end date
This defines how long the segment remains active. Once this date is reached, the segment stops refreshing with new data and moves to "Expired" status
Users already in the segment will remain there, but no new users will be added even if they meet the criteria
Select Next

Select + Add Rule icon to set your conditions
Choose from available attributes or action-based conditions (for example, users who interacted with a specific Smart Walk-Thru)
Select Calculate button to see a preview of how many users currently meet these conditions
Select Save

After you create a behavioral segment, you can use it in the editor by assigning it directly to a WalkMe item or by creating a rule in the condition builder.
Assign a segment (Segmentation)

Create a rule (Condition Builder)
Maximum 10 segments per system
Maximum 50,000 users per segment
Only the Production environment is supported
Mobile Web systems are not supported
Maximum 5 rules per segment
Segments are system-specific and cannot track behavior across multiple systems
Migrated segments are read-only and use User-Level scoping (not Session-Level)
Expired segments cannot be re-activated; logic must be recreated in a new segment
It can take up to 15 minutes for data to appear
Behavioral Segments (formerly BBS) have been rebuilt on a real-time, event-based infrastructure within the WalkMe Console. This transition eliminates the slow, offline processing used in Insights Classic, offering significantly higher performance and scalability.
Understanding the Shift to User Scoping
The most significant logic change is the move from Session-Based to User-Level scoping.
In Classic: A rule like "Completed SWT X AND saw ShoutOut Y" only included users who did both in a single session
In Console: The same rule includes users who performed these actions at any point within the selected date range, providing a more accurate reflection of long-term user behavior