Admin loginSmartico.aiTheAffiliatePlatform.com

▪️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:

  1. Users with failed communication of resource X in campaign Y. Parameters for segmentation:

    1. Campaign - select the Campaign

    2. Fail reason(s) - select the fail reason

    3. Communication resource that failed - select the communication channel

    4. Date/time period when failed to send communication - select the time period when the communication was not sent

  2. Users that have X remaining spins in the Mini-game Y. Parameters for segmentation:

    1. Name of mini-game template (only games based on the spin attempts) - select the name of the mini-game

    2. Number of spin attempts that users have remaining - select the number of remaining spin per user

  3. Users registered in specific tournament

    1. Tournament - select the tournament

    2. 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' ones includes the instances that are in Status 'FINALIZING’

    3. 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

  4. Users who have opted into a mission but haven’t completed it

    1. Mission - select the mission

    2. Opted in, in the last X days - filter players who opted in during the selected period

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 progress in at least one task but haven’t finished them all will be included in the segment.

  1. Users who have made progress in mission X, but haven’t completed it

    1. Mission - select the mission

    2. Had progress in the last X days - filter players who made progress during the selected period

  2. Users who have completed mission X, but haven’t claimed the prize

    1. Mission - select the mission

    2. Completed mission in the last X days - filter players who have completed the mission during the selected period, but haven't claimed their prize

  3. Users who have made progress in Badge X, but haven’t completed it

    1. Badge - select the badge

    2. Had progress in the last X days - filter players who made progress during the selected period

  4. Users who have played mini-game X, but haven't claimed their rewards

    1. Mini-game - select the mini-game

    2. Unclaimed prizes - select the prize. Only claimable prizes will be displayed.

    3. Had unclaimed rewards in the last X days - filter players who had unclaimed rewards in the selected period

  5. Users who have opted in to a Jackpot X

    1. Jackpot - select the Jackpot

    2. Had opted in, in the last X days - filter players who opted in during the selected period

  6. Users who finish in position X in the Leaderboard

    1. Leaderboard - select the Leaderboard

    2. Position, from - select the player position from (e.g. from position 1)

    3. Position, to - select the player position to (e.g. to position 10)

    4. Finish in position X in the last X days - filter players who finished in the specified position in the selected period

  7. Users who completed X Badges

    1. Badges Completed (From) - specify the minimum number of badges completed by the player

    2. Badges Completed (To) - specify the maximum number of badges completed by the player (e.g. player competed between 1 and 10 badges)

    3. Completed X badges in the last X days - filter players who completed a specific number of badges for the selected period

  8. Users with failed bonus Y given by X

    1. Given by - define where the bonus was issued from (Campaign, Automation Rule, Mission, Mini-game, Store, etc.)

    2. Activity - select the specific campaign, mission, store item, mini-game, etc that issued the bonus

    3. Period when bonus failed - define the period when the bonus has failed

  9. Users who won in a Raffle draw

    1. Raffle - select the ID/name of raffle

    2. Draw - select the name of Draw

    3. Days count - set a time window

  10. Users have push token with status X for platform Y

    1. Platforms - select the platform (Chrome, Safari, Native Android, Chrome mobile, etc.)

    2. Token status - select the status of the token (Active, Inactive)

    3. Min. tokens count - select the minimum token count

    4. Max. tokens count - select the maximum token count

  11. Users have X tickets for Raffle Y

    1. Raffle - select the ID/name of raffle

    2. Tickets count from / to – define the ticket range to filter users based on how many tickets they’ve earned for the selected Raffle

  12. Users who are qualified for tournament X, but didn't opt in

    1. Tournament - select the tournament

    2. Instance - select the tournament instance

  13. Users who have opted in to tournament X, but are not qualified

    1. Tournament - select the tournament

    2. Instance - select the tournament instance

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 an explanation of the 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.

You can also segment users 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 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.

  1. Segment Behavior

  • Works similarly to Behavior Segments.

  • A Rebuild Schedule option allows you to control how and when the segment is updated.

  1. 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.

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.

  1. 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?