# "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. {% hint style="info" %} **We are planning to add more cases based on client requests.** If you cannot meet your segmentation needs, please raise a ticket in Smartico JIRA with an explanation of the required segmentation conditions, and we will review your specific case. {% endhint %} 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.
You can also use "Common cases" segments as a sub-condition of other segments by selecting a specific "Common Case" segment. This can be done using the property: `Core: CSV & Common case segments`

BO: 'CSV & Common case segments' property in User state segments

## How to set up **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 Rebuilding Logic** * When Rebuild Schedule is **Disabled** (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 rebuild only on the scheduled date or when manually triggered via the 'Rebuild Segment' button.
When setting the rebuild schedule, the system will automatically select a time with lower system load by default. You can change this to a different time if needed. However, if the selected time falls within a high-load period, a message will appear recommending an alternative time to help avoid calculation delays. You can still proceed with your chosen time - the system will display an estimated delay for your reference.
**User Lists** * **Real-time Users** Tab: * 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
## **Supported common cases** #### **Users with failed communication of resource X in campaign Y** * Campaign - select the Campaign * Fail reason(s) - select the fail reason * Communication resource that failed - select the communication channel * Date/time period when failed to send communication - select the time period when the communication was not sent #### **Users who have X remaining spins in the Mini-game Y.** Parameters for segmentation * Name of mini-game template (only games based on the spin attempts) - select the name of the mini-game * Number of spin attempts that users have remaining - select the number of remaining spins per user #### **Users registered in a specific tournament** * Tournament - select the tournament * Instance Type - select the tournament instance. 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' instances include the instances that are in Status 'FINALIZING.’ * Select users by points or by position - you can segment users by the score points they have or by the position they have in the selected tournament #### **Users who have opted into a mission but haven’t completed it** * Mission - select the mission * Opted in, in the last X days - filter players who opted in during the selected period {% hint style="danger" %} Please note that: * Progress in a recurring mission only counts for its current instance. Progress from previous instances does not carry over or get saved. * All users who have made progress in at least one task but haven’t finished them all will be included in the segment. {% endhint %} #### **Users who have made progress in mission X, but haven’t completed it** * Mission - select the mission * Had progress in the last X days - filter players who made progress during the selected period #### **Users who have completed mission X, but haven’t claimed the prize** * Mission - select the mission * Completed mission in the last X days - filter players who have completed the mission during the selected period, but haven't claimed their prize #### **Users who have made progress in Badge X, but haven’t completed it** * Badge - select the badge * Had progress in the last X days - filter players who made progress during the selected period #### **Users who have played mini-game X, but haven't claimed their rewards** * Mini-game - select the mini-game * Unclaimed prizes - select the prize. Only claimable prizes will be displayed. * Had unclaimed rewards in the last X days - filter players who had unclaimed rewards in the selected period #### **Users who have opted in to a Jackpot X** * Jackpot - select the Jackpot * Had opted in, in the last X days - filter players who opted in during the selected period #### **Users who finish in position X in the Leaderboard** * Leaderboard - select the Leaderboard * Position, from - select the player position from (e.g., from position 1) * Position, to - select the player position to (e.g,. to position 10) * Finish in position X in the last X days - filter players who finished in the specified position in the selected period #### **Users who completed X Badges** * Badges Completed (From) - specify the minimum number of badges completed by the player * Badges Completed (To) - specify the maximum number of badges completed by the player (e.g., player completed between 1 and 10 badges) * Completed X badges in the last X days - filter players who completed a specific number of badges for the selected period #### **Users with a failed bonus Y given by X** * Given by - define where the bonus was issued from (Campaign, Automation Rule, Mission, Mini-game, Store, etc.) * Activity - select the specific campaign, mission, store item, mini-game, etc that issued the bonus * Period when bonus failed - define the period when the bonus has failed #### **Users who won in a Raffle draw** * Raffle - select the ID/name of the raffle * Draw - select the name of Draw * Days count - set a time window #### **Users have a push token with status X for platform Y** * Platforms: select the platform (Chrome, Safari, Native Android, Chrome mobile, etc.). * Token status - select the status of the token (Active, Inactive) * Min. tokens count - select the minimum token count * Max. tokens count - select the maximum token count #### **Users have X tickets for Raffle Y** * Raffle - select the ID/name of the raffle * Tickets count from/to – define the ticket range to filter users based on how many tickets they’ve earned for the selected Raffle #### **Users who are qualified for tournament X, but didn't opt in** * Tournament - select the tournament * Instance - select the tournament instance #### **Users who have opted in to tournament X, but are not qualified** * Tournament - select the tournament * Instance - select the tournament instance #### **Users who have ever opened the Gamification Widget** * Opened Section/Modal (Ever) - select the section/modal/GF widget that was opened * Opened section/modal in the last X days - filter players who have opened the section/modal/GF widget in the selected period #### **Lock User State Segment** * Select segment - define the segment you want to lock\ Read more in the [#locking-option-for-user-state-segments](#locking-option-for-user-state-segments "mention") #### **Users who opted into a mission** * Mission - Select a mission to segment players who have opted in to it (regardless of completion) * Opted in, in the last X days - define the time period to filter users who opted in to the selected mission within that timeframe. #### **Users who participated in Campaign X** * Select Campaign - Select the campaign in which the users participated. * User progress state - Select the user's campaign progress state (e.g., Still in Campaign, Finished). * Started in the last X days - define the time period to filter users who have entered in the selected campaign within that timeframe. * Finished in the last X days - define the time period to filter users who have completed the selected campaign within that timeframe. * Converted in the Campaign - define if the users have converted in the Campaign or not #### Users who bought a store item in the last X days * Select Store item - select the store item or store items that the user bought * Bought in the last X days - define the time period to filter users who bought the selected store items #### Users who didn't open recent communications * Communication channel - select the communication type that was sent, e.g. email, SMS, Viber * Sent in the last X days - define the time period to filter users who didn't open specific type of communication * Minimum number of not opened communications - define how many not opened communications the users have in the specified period #### Users who have bonus X with status Y * Bonus template - select the bonus template that was issued * Bonus status - select the status of the bonus that was issued * Issued in the last X days - define the time back period when the bonus was issued, for example 10 days ago #### Users who didn't change level in the last X days * Didn't change level in the last X days - Enter how many days back the system should look from today. For example, ‘7' will include data from the last 7 full days in UTC + the current day. * Specify 'From' and 'To' Level Change - by default disabled, meaning that you will be segmenting all the users who haven’t changed their level in the specified period. Once enabled you can select: * ‘From’ level - Specify the level from which the player did not progress to the next level (includes downgraded players). For example, players who reached Level 3 but never advanced to Level 4. This also includes players who were later downgraded and are no longer on Level 3. * ‘To’ level - Specify the level the player has not reached. (e.g., players who have never reached level 4) You can also define a broader range. For example, setting From Level = Level 2 and To Level = Level 5, this means that you will segment all the users who once reached Level 2, but never reached level 5. ## Locking Option for User State Segments The Lock User State Segment feature allows you to “freeze” the user list of any state-based segment at a specific point in time.\ This ensures users remain in the segment even if their behavior changes later. ### Why This Is Needed - Example Imagine you are running a promotion: * Target users: Users who haven’t deposited for 30 days * Promotion rule: They must deposit to get an attempt in the mini-game You create a segment defined as:\ “Users that haven’t deposited for 30 days.” #### The problem As soon as a user makes a deposit: * They immediately drop out of this segment * Because the mini-game is restricted to that segment, the user can no longer access the promotion - even though their deposit was required to qualify This creates a logical conflict:\ The user must deposit to participate, but depositing removes them from the segment. #### The Solution - Locking the Segment To solve this, Smartico introduces the Lock User State Segment mechanism. Instead of directly using the state-based segment, you can now lock it by creating a Common Case segment that copies the user list from the original segment. #### How it works 1. You select any state-based segment (e.g., “No deposit for 30 days”). 2. You create a Common Case segment that: * Takes a snapshot of the user list from the original segment * Does this either once or on a scheduled basis (daily, weekly, etc.) 3. The Common Case segment becomes a frozen version of the segment: * Users stay in it even if their behavior changes later * Perfect for promotions that require stable user lists #### Result Your promotion can safely: * Target users who had not deposited for 30 days * Require them to deposit to unlock the mini-game * Keep them eligible even after they deposit The Common Case segment ensures the user list is stable, predictable, and refreshed only when you choose, not instantly when user behavior changes. ### How to setup It can be created in Segments > Create > Common cases segment
From the templates list, choose Lock User Segment.
### Segment Eligibility Rules When “Lock User State Segment” is selected, the system shows only segments that qualify for this feature:
**Eligible segments:** * User State Segments are built entirely on state-based conditions. **Not Eligible segments:** * Segments created from CSV imports. * Segments based on behavioral data. ### Locking Behavior Once a segment is locked, its user list becomes static. The membership reflects the exact users present at the moment of locking and will not update automatically as the user states change. The locked user list can be found at the "Segment Users" tab:
The scheduling option remains active, giving operators full freedom to choose when the segment should be rebuilt and its user list adjusted. It can also be rebuilt manually from the top right corner:
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.smartico.ai/welcome/products/crm-automation/segmentation/common-cases-segments.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.