Common Cases Segments
Overview
The Common Cases Segment is designed to simplify user targeting based on frequently used behavioral patterns. It offers a selection of predefined templates, allowing you to quickly configure conditions and control rebuild settings.
Current support types of common cases:
Users with failed communication of resource X in campaign Y. Parameters for segmentation:
Campaign - required
Fail reason(s) - optional
Communication resource that failed - optional
Date/time period when failed to send communication - required
Users that have X remaining spins in the Mini-game Y. Parameters for segmentation:
Name of mini-game template (only games based on the spin attempts) - required
Number of spin attempts that users have remaining - required
Users registered in specific tournament
Tournament - required
Instance Type - required. You can choose between the current instances of the tournament or Completed. The 'Current' instances include all the instances that are currently in status ‘PUBLISHED, STARTED, REGISTER, FINALIZING and the 'Completed' ones includes the instances that are in Status 'FINALIZING’
Had minimum score points in the selected tournament - optional
Users who have opted into a mission but haven’t completed it
Mission - required
Opted in, in the last X days - required
Users who have made progress in mission X, but haven’t completed it
Mission - required
Had progress in the last X days - required
Users who have completed mission X, but haven’t claimed the prize
Mission - required
Completed mission in the last X days - required
Users who have made progress in Badge X, but haven’t completed it
Badge - required
Had progress in the last X days - required
Users who have played mini-game X, but haven't claimed their rewards
Mini-game - required
Unclaimed prizes - required. Only claimable prizes will be displayed.
Had unclaimed rewards in the last X days - required
Users who have opted in to a Jackpot X
Jackpot - required
Had opted in, in the last X days - required
Users who finish in position X in the Leaderboard
Leaderboard - required
Position, from - required
Position, to - required
Finish in position X in the last X days - required
Users who completed X Badges
Badges Completed (From) - required
Badges Completed (To) - optional
Completed X badges in the last X days - required
We are planning to add more cases based on requests from our clients.
If you cannot cover your segmentation needs, please raise a ticket to Smartico JIRA with explanation of needed segmentation conditions, and we will review your specific case.
The Common Cases segment is available in the Segments section of the Back Office. To use it, simply select "Common Cases" when creating a new segment, then complete the required setup based on the selected template.
How It Works
1. Selecting a Template
Choose from a list of predefined Common Case templates.
Each template includes specific conditions.
After selecting a template, configure the related conditions to define your segment.
Segment Behavior
Works similarly to Behavior Segments.
A Rebuild Schedule option allows you to control how and when the segment is updated.
Segment Rebuilding Logic
When Rebuild Schedule is (by default) - the system will automatically rebuild the segment once immediately after it is created - to populate the user list. After this initial rebuild, the segment will not update again unless manually triggered.
When Rebuild Schedule is Enabled - No automatic rebuild after creation - the segment will only rebuild on the scheduled date or if manually triggered using the 'Rebuild Segment' button.
User Lists
Real-time Users List:
Displays users currently (in real-time) matching the segment conditions
Updates are live, but do not represent the saved segment users
Segment Users Tab:
Shows the list of users from the last completed rebuild
This is the active list used for actions like campaign targeting
Last updated
Was this helpful?