Behavioral Segments
Last updated
Was this helpful?
Last updated
Was this helpful?
Behavioral segments are based on the behavior of the user.
It combines data from both the user profile state and his behavior. The segment is based on the historical behavior of the user, e.g. users that did total wagering of more than 100 EUR on Slot games in the last 30 days.
Inside the segment template, you can find information about the segment's last and next rebuilds based on the defined schedule.
You can manually initiate the rebuild process by clicking the 'Rebuild Segment' button. Once triggered, the segment will be added to the queue, and the rebuild will begin shortly. Progress can be monitored in the Calculation History section.
In order to set up the segment you must fill in the following sections:
User activity and timing - which activity you solid like to track and for what period of time. The maximum time for analysis depends on the activity. For example, for Deposit is 365 days, and for Casino bets is 90 days.
Event attributes - you can define related to the event (activity) attributes
Total conditions - could be a count of activities, Total, MIN or MAX conditions. E.g. to segment users who did "Total" bet amount above 1000 EUR
Update schedule - define a schedule when the segment will be rebuilt
State Conditions - To make your segment even more precise you can also add a user state condition like brand, registration country, language, etc
Behavioral segments like other segments can be exported and have a scheduled export if needed. You can choose to export specific properties or include all properties.
If a scheduled export exists for a segment, it will be indicated in the Segments grid view with an icon. Hovering over the icon will display the scheduled details.
This type of segment can be used in any context in CRM Automation or Gamification modules:
to limit Real-time and Scheduled campaigns
to limit Automation rules
to limit the visibility of Tournaments, Store items, and Mini-games
Behavioral segments can include user state properties. However, if a Behavioral Segment with user state properties is used in a Campaign, Automation Rule, Tournament, Mini-game, etc., any changes to a user's state properties before the next scheduled rebuild will not be applied. The user will continue to progress in the Campaign, Rule, Tournament, etc., based on their status during the last rebuild.
🔍 Example:
You have a Behavioral Segment for users who deposited more than 100 EUR in the last 30 days with the user state property: Last login device = Desktop.
At 00:00, a scheduled rebuild occurs, and John matches the segment conditions.
At 02:00, John logs in using a mobile device.
Despite the change, John will continue to match the segment criteria until the next rebuild.
If John tries to register for a Tournament at 02:00, he will be allowed because the segment still considers him as having logged in from a Desktop.
We've introduced two new period types to help you build Behavioural segments. The options are available only for the behavioral segments and can be found under the ‘Period Type’ option:
Fixed Period: Set specific dates, e.g., from 01.01.2024 to 23.01.2024 (UTC).
Relative period: Use dynamic ranges like Current day till now, Previous full day, Last weekend, Last full week, Last full month, etc. You can also select different time zones and the calculations of the user segment will be based on it.
For example, you can now create a behavioral segment for users who deposited more than 1000 EUR total in the last full month in UTC +6.
