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

   2. Fail reason(s) - optional

   3. Communication resource that failed - optional

   4. Date/time period when failed to send communication - required

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) - required

   2. Number of spin attempts that users have remaining - required

3. Users registered in specific tournament

   1. Tournament - required

   2. 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’

   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 - required

   2. Opted in, in the last X days - required

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

   1. Mission - required

   2. Had progress in the last X days - required

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

   1. Mission - required

   2. Completed mission in the last X days - required

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

   1. Badge - required

   2. Had progress in the last X days - required

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

   1. Mini-game - required

   2. Unclaimed prizes - required. Only claimable prizes will be displayed.

   3. Had unclaimed rewards in the last X days - required

5. Users who have opted in to a Jackpot X

   1. Jackpot - required

   2. Had opted in, in the last X days - required

6. Users who finish in position X in the Leaderboard

   1. Leaderboard - required

   2. Position, from - required

   3. Position, to - required

   4. Finish in position X in the last X days - required

7. Users who completed X Badges

   1. Badges Completed (From) - required

   2. Badges Completed (To) - optional

   3. Completed X badges in the last X days - required

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

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

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 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 only rebuild on the scheduled date or if manually triggered using the 'Rebuild Segment' button.

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