▪️Dynamic Missions
General Overview
Dynamic missions allow players to progress by completing actions that are personalized to their own behavior. Instead of static requirements, the mission adapts to each player using Smartico’s AI-driven metrics, such as:
Favorite casino game
Favorite game type
Favorite game provider
Recommended casino bet amount
Recommended deposit amount
Each player sees a personalized version of the same mission, based on their historical activity.
Note: Populating these properties requires activation. Please contact your Success Manager for more details.
How player data is calculated
Smartico continuously analyzes player behavior using internal AI models. The following metrics are automatically calculated per user:
Favorite products (game, game type, provider)
Recommended bet amount
Recommended deposit amount
These values are recalculated daily and refreshed between 02:30 - 04:30 AM UTC, and updates are delivered through the system event Core: favorite/recommended metrics update (technical name core_fav_game_update)
Recommended amounts are visible in the user profile in the CRM tab for each player
👉 Read more about:
Supported Dynamic Mission Types
Dynamic missions currently support the following behavior-based metrics:
Favorites (Top 3)
Core: Favorite game name, top 3
Core: Favorite game type, top 3
Core: Favorite game provider, top 3
These represent the user’s top 3 preferences, ranked by engagement.
Recommended Amounts
Core: Recommended casino bet amount (stored in the user’s currency)
Core: Recommended deposit amount (stored in the user’s currency)
How to Set Up a Dynamic Mission
Create a Mission - Dynamic missions are configured inside standard mission templates.
Segment Users Correctly - In Who can see and progress in the mission, make sure you target only users who actually have the required dynamic data. This prevents users from seeing missions they cannot complete.
Examples:
Mission uses Top 3 favorite games → segment users who have Top 3 favorites defined
Mission requires a recommended deposit amount → segment users who have a calculated recommended amount
Task configuration
The key difference between dynamic and regular missions lies in how task conditions are configured.
Step 1: Choose the Trigger Event
Select an event that matches the mission goal, such as:
Casino: BetCasino: Bet-WinCasino: WinAcc: Deposit Approved
Step 2: Add Property-to-Property Conditions
Dynamic missions rely on property-to-property comparisons.
Example for Favorite Game Mission
Favorite game name, top 3 → has any of → Casino: Bet Game Name
Progress is made only when the player bets on their own favorite casino games.
Example for the Recommended Deposit Mission
Last deposit amount >= Core: recommended deposit amount
Progress is made only when the deposit matches the player’s recommended deposit amount.
Example for Recommended Casino Bet Mission
Casino: Bet amount >= Core: recommended casino bet amount
Progress is made only when the bet matches the recommended casino bet amount.
Supported Operations for Favorited:
Has on pos. 1 any of– favorite in position 1Has on pos. 2 any of– favorite in position 2Has on pos. 3 any of– favorite in position 3Has any of– any favorite in the top 3Doesn’t have any of– excludes favorites in top 3
This logic applies equally to favorite game types and favorite providers.
Dynamic Tags for Mission Text
To display personalized values in the mission UI, use dynamic tags.
For Favorite games, providers, and types, use the tag {{suggested_games}}
For the top 3 favorites → It shows to 3 game names
For the top 1 → It shows only the #1 favorite game name
For favorite type/provider → It shows either the favorite game type or the favorite game provider
For example, title:
Will automatically become:
For Recommended deposit and bet amounts, use the tag {{suggested_value}}, it will be replaced with the value and the user's currency.
For example, title:
Will automatically become:
Front-End Presentation
The mission text is dynamically personalized per user
Each user sees their own favorite games or recommended values
Values update daily unless locking is enabled (explained below)
Locking Logic
You can control whether dynamic values stay fixed or update during the mission as soon as a recommendation/favorite is changed.
When Locked: The mission captures the player’s favorites (Top 3) or recommended amount at the moment they make their first progress. These values remain fixed until the mission is completed or expires, even if the player’s preferences change later.
When Unlocked: The mission updates automatically as the player’s favorites or recommended amounts change. Progress is preserved, but the required games, types, or recommended bet/deposit amounts may adjust over time.
Example:
On January 1st, the player's top provider is Pragmatic Play. They make 10 bets on it (10% progress). On January 2nd, their favorite changes to SoftGaming:
If locked, they must finish the mission by betting on Pragmatic Play.
If unlocked, the mission now expects bets on SoftGaming.
If the mission is recurring, subsequent rounds will always use the updated favorites.
This logic applies equally to:
Favorite games / types / providers
Recommended bet amounts
Recommended deposit amounts
Locking is available only when using property-to-property comparisons.
Ensuring Mission Consistency
Always align mission logic with segmentation:
Mission uses Top 3 favorites → segment users with Top 3 favorites
Mission requires a specific game as favorite → segment users who have it in Top 3
Mission uses recommended amounts → segment users with calculated values
Examples:
Mission uses Top 3 favorites → segment users with Top 3 favorites
Mission requires a specific game (e.g., Book of Itza) as a favorite → segment users who have it in position #1, #2, or #3
This prevents users from accessing missions they cannot progress in.
Example Use Cases
Generic Favorite Game Mission:
Make 100 bets on any of your top 3 favorite games.
The player can progress by playing any of their current favorites.
The mission task name 'Make 100 bets on
{{suggested_games}}will be transformed to 'Make 100 bets on A, B, C', where A, B, C will be the names of favorite games for a specific player.
Specific Position Mission:
Make 100 bets on your the most favorite game.
Only progress when the player plays their top-ranked game (position 1).
The mission task name 'Make 100 bets on
{{suggested_games}}will be transformed to 'Make 100 bets on A'
Specific Game in Favorite Position:
Play your #1 favorite game: Book of Dead.
Only if this specific game is the player's game (in position 1) he can progress
If their favorites change, they’ll still see the mission, but won’t be able to progress further.
Recommended Deposit Amount:
Make 5 deposits of your recommended amount
Player progresses only if the deposit equals their recommended value
Task name: Make 5 deposits of {{suggested_value}}
UI example: Make 5 deposits of 50 EUR
Recommended Casino Bet Amount
Make 10 bets with your recommended casino bet amount
Player progresses only if each bet matches the recommended value
Task name: Make 10 bets with {{suggested_value}} each
UI example: Make 10 bets with 5 EUR each
Favorite Casino Report
You can also analyze favorites in the Games & Sports Reports, where you’ll find data on most played games, top preferences, bet share, and unique users.
Read more about Favorite games and Game types:
FAQ
Q: Do favorites require activation? A: Yes. Contact your Success Manager.
Q: How often are favorites updated? A: Daily between 02:30–04:30 AM UTC.
Q: Do players keep progress if the favorites change? A: Yes, when using Not-Locked logic.
Q: Can I dynamically show player favorites in mission text?
A: Yes, using the {{suggested_games}} tag.
Q: Where does Smartico get the favorite game names from? Are they taken from the game catalog? A: Names of the games are taken from the bets/wins transactions. At this point, they are not connected to the game details from the Games Catalog.
Last updated
Was this helpful?