▪️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
Favorite sport type
Favorite League
Favorite sport market type
Recommended casino bet amount
Recommended deposit amount
Each player sees a personalized version of the same mission, based on their historical activity.

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)
Favorite sport type
Favorite league
Favorite sport market
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
Core: Favorite Sport Type, Top 3
Core: Favorite Sport League, Top 3
Core: Favorite Sport Market, 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 sport 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
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:
For Favorite sport type and favorite league, use the tag {{suggested_sport}} , on the UI it will be automatically replaced by the player's favorite sport or league.
For example, title:
Will automatically become:
For Favorite sport market, use the tag {{suggested_market}}, on the UI it will be automatically replaced by the player's favorite sport market.
For example, title:
Will automatically become:
For the target of a Prop to Prop task (“Total amount should reach” with Prop to Prop enabled), use the tag {{suggested_amount}}. It is replaced with the amount the player has to reach, which is the multiplier × the player's recommended amount, and the user's currency.
For example, with a target of 2 × Recommended deposit amount and a recommended deposit of 50 EUR, title:
Will automatically become:
What a favorites tag shows for each operator
For {{suggested_games}}, {{suggested_sport}} and {{suggested_market}}, the output depends on the operator used in the condition.
Has any of
All top 3 favorites, separated by commas
Football, Basketball, Tennis
Doesn’t have any of
All top 3 favorites, separated by commas (the ones the player must avoid)
Football, Basketball, Tennis
Has on pos. 1 / 2 / 3 any of
Only the favorite in that position
Football
Favorite names are shown with spaces instead of underscores and in title case, so both_teams_to_score is shown as Both Teams to Score. If the player has fewer than 3 favorites, only the ones they have are shown.
Recommended amount tags: suggested_value and suggested_amount
A task can use a recommended amount in two places: in a condition (for example, Acc: Last deposit amount >= Core: Recommended deposit amount) and in the Prop to Prop target of “Total amount should reach” (for example, 2 × Core: Recommended deposit amount).
{{suggested_value}}shows the recommended amount itself.{{suggested_amount}}shows the amount the player has to reach: the target’s multiplier × the player’s recommended amount.
Task setup
{{suggested_value}} shows
{{suggested_amount}} shows
Recommended amount condition only
The condition’s recommended amount
Not replaced
Prop to Prop target only
The recommended amount the target is based on
Multiplier × recommended amount
Both a condition and a Prop to Prop target
The condition’s recommended amount
The target’s multiplier × its recommended amount
For example, with a target of 2 × Recommended deposit amount and a recommended deposit of 1002 UAH, the task name Deposit {{suggested_value}} / {{suggested_amount}} is shown as Deposit 1002 UAH / 2004 UAH.
How {{suggested_amount}} is calculated and shown:
30 EUR
1.5
45 EUR
50 UAH
3
150 UAH
50 UAH
2.5
125 UAH
600 EUR
2.5
1500 EUR
0 EUR
2
0 EUR
The amount is rounded to at most 2 decimals, without trailing zeros and without a thousands separator, for example 45.45, 50, 49.5, 1500.
The tag follows the player’s current recommended amount. When Lock Recommended Deposit/Bet Amount is on, it uses the amount captured at the player’s first progress, so the target the player sees does not change during the mission.
Changing the multiplier on the task changes the amount the tag shows.
Where you can use dynamic tags:
Dynamic tags are replaced with the player's personal values in the following mission fields:
Mission name
Mission sub-header
Mission description
Mission Terms & Conditions
Task name
In the mission name, sub-header, description and Terms & Conditions, the value is taken from the mission's task that has the matching property-to-property condition. In a task name, the value is taken from that task's own condition.
Dynamic tags are not supported in task descriptions, the unlock mission description, or in any communication channel (email, SMS, push, popup, etc.). In these places the tag is shown as plain text, e.g. {{suggested_value}}. To show a recommended amount in a communication, use the player's state tags instead.
What is displayed depending on where the tag is placed
In a task name, the value comes from that task’s own condition or target. A task name can only show values the task itself uses. If you put {{suggested_market}} in the name of a task that has no favorite market condition, or {{suggested_amount}} in a task without a Prop to Prop target, the player sees the tag as plain text.
In the mission name, sub-header, description and Terms & Conditions, the value is taken from the mission’s tasks. Smartico checks the tasks in their order in the mission and uses the first task that can fill the tag. Each tag is filled on its own, so different tags in the same text can come from different tasks.
For example, a mission has these tasks:
Task 1: Favorite sport type, top 3 → has any of. Task name:
Bet on {{suggested_sport}}Task 2: Favorite sport market, top 3 → has on pos. 1 any of. Task name:
Bet on {{suggested_market}}Task 3: Deposit total with a Prop to Prop target of 2 × Recommended deposit amount. Task name:
Deposit {{suggested_amount}} in total
The mission name {{suggested_sport}} week: deposit {{suggested_amount}} and bet on {{suggested_market}} is shown as Football, Tennis, Basketball week: deposit 100 EUR and bet on Both Teams to Score, and the tasks are shown as Bet on Football, Tennis, Basketball, Bet on Both Teams to Score and Deposit 100 EUR in total.
One task has the matching condition or target
Value from that task
Value in that task; plain text in the other tasks
Several tasks have the matching condition with different values
Value from the first of those tasks only
Each task shows its own value
No task has the matching condition or target
Plain text
Plain text
The same tag appears twice in one field
Both are replaced with the same value
Both are replaced with the same value
When the tag is shown as plain text
The player sees the tag itself, for example Bet on {{suggested_market}}, when:
The task (or, for mission-level text, any task) has no property-to-property condition or Prop to Prop target that fills this tag.
{{suggested_amount}}is used in a task without a Prop to Prop target.The player has no value for the property, for example no calculated favorite markets or no recommended amount. Segment the mission to players who have the value.
The condition uses
Has on pos. 2 any oforHas on pos. 3 any ofand the player has fewer favorites than that.The tag was added to an existing mission and the cached version is still shown. Clear the cache and check again.
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

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
Mission uses favorite sport markets → segment users with Favorite sport market, top 3 defined
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
Generic Favorite Sport Mission (Top 3 Sports):
Place 3 bets on any of your top 3 favorite sports.
The player can progress by placing bets on any of their top 3 sports (e.g., Football, Basketball, or Tennis).
The mission task name:
Place 3 bets on {{suggested_sport}}transforms toPlace 3 bets on Football, Basketball, Tennis.Recommended: Enable Lock Favorite League/Sport if the task requires multiple bets, so the sports remain consistent throughout the mission round.
Top League Mission (Position 1 Favorite League with Lock):
Place 5 bets on your #1 favorite league.
The player progresses only when betting on their top-ranked league (e.g., Premier League).
The mission task name:
Place 5 bets on your favorite league: {{suggested_sport}}transforms toPlace 5 bets on your favorite league: Premier League.With Lock Favorite League/Sport enabled, the moment the player places their first qualifying bet, the target league freezes to Premier League even if their profile shifts mid-week.
Specific League in Favorite Position:
Bet on the UEFA Champions League (only active for players who have it as their #1 league).
Only players who currently hold UEFA Champions League in position 1 of their top leagues can progress.
If their favorites shift prior to starting, they will still see the mission but cannot progress until it returns to position 1.
Generic Favorite Sport Market Mission (Top 3 Markets):
Place 3 bets on any of your top 3 favorite markets.
The player can progress by placing bets on any of their top 3 markets (e.g., Over/Under, 1x2, or Both Teams to Score).
The mission task name: Place 3 bets on
{{suggested_market}}transforms to Place 3 bets on Over/Under, 1x2, Both Teams to Score.Recommended: Enable Lock Favorite Sport Market if the task requires multiple bets, so the markets remain consistent throughout the mission round.
Favorite Market in Favorite League:
Place 5 bets on your #1 market in your #1 league.
The task has two conditions: Favorite sport league, top 3 → has on pos. 1 any of → Sport: Selection League, and Favorite sport market, top 3 → has on pos. 1 any of → Sport: Selection Market.
The mission task name: Place 5 bets on
{{suggested_market}}in{{suggested_sport}}transforms to Place 5 bets on Over/Under in Premier League.
Recommended Sport Bet Amount:
Place 5 sport bets of at least your recommended sport bet amount.
Condition: Sport: Bet amount >= Core: Recommended sport bet amount.
Task name:
Place 5 sport bets of at least {{suggested_value}}UI example: Place 5 sport bets of at least 10 EUR
Prop to Prop Wagering Target:
Wager 3 times your recommended casino bet amount in total.
Target: Total amount should reach, Prop to Prop enabled with 3 × Core: Recommended casino bet amount.
Task name:
Wager {{suggested_amount}} in totalUI example for a player with a recommended casino bet of 50 UAH: Wager 150 UAH in total
Per-Bet Amount and Total in One Task:
Bet at least your recommended casino bet amount per spin, and 10 times that amount in total.
Condition: Casino: Bet amount >= Core: Recommended casino bet amount. Target: Prop to Prop enabled with 10 × Core: Recommended casino bet amount.
Task name:
Bet at least {{suggested_value}} per spin, {{suggested_amount}} in totalUI example: Bet at least 5 EUR per spin, 50 EUR in total
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:
Dynamic Target Calculation (Prop-to-Prop) for Mission Tasks
With the Property-to-Property (Prop-to-Prop) dynamic targets for mission tasks that track accumulated values, such as “Complete action a few times, check a SUM of attribute.” You can create personalized, dynamic targets based on a numeric player state property multiplied by a custom factor. For example, a target can be calculated as 2 × Recommended Deposit Amount, allowing each player’s target to be determined automatically based on their individual property value.
A mission task can use either a fixed multi-currency target or a dynamic Prop-to-Prop target, but not both:
When fixed currency values are configured, the Prop-to-Prop option is hidden.
When Prop-to-Prop is enabled, the multi-currency input grid is hidden and replaced with a Property selector and Multiplier field.
To show the target the player has to reach, use the tag {{suggested_amount}}. It is replaced with the multiplier × the player's recommended amount and the user's currency, for example 45 EUR for 1.5 × 30 EUR. To show the recommended amount itself, use {{suggested_value}}.
How to Configure in BackOffice:
Navigate to Gamification → Missions and edit or create a mission task.
Select the task type: "Complete action a few times, check a SUM of attribute" (e.g., Deposit total or Bet total).
Choose the triggering action and the property to accumulate (e.g., Casino: Bet Amount).
In the "Total amount should reach" section, switch the "Enable 'Prop to Prop' for 'Total amount should reach'" toggle to Yes.
Configure the dynamic calculation fields:
Multiplier: Set the multiplication factor (defaults to 2x).
Property Dropdown: Select the numeric player property used as the baseline (such as Recommended Deposit Amount or custom CRM attributes).

Example Use Case:
Dynamic Casino Wagering Mission:
Task Goal: Wager real money based on recommended deposit.
Action: Casino: Bet-Win
Tracked Value: Bet Amount (Real)
Target Setting: Prop-to-Prop enabled with 1.5 × Recommended Deposit Amount.
Task name:
Wager {{suggested_amount}}Player Experience:
Player A (Recommended Deposit: €30) receives an automatic wagering target of €45 and sees the task as Wager 45 EUR.
Player B (Recommended Deposit: €200) receives an automatic wagering target of €300 and sees the task as Wager 300 EUR. Both players engage with the exact same mission while enjoying a challenge tailored to their activity level.
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. Use {{suggested_games}} for casino favorites, {{suggested_sport}} for sport types and leagues, and {{suggested_market}} for sport markets.
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.
Q: Where can I use dynamic tags? A: In the mission name, sub-header, description, Terms & Conditions and in task names.
Q: Can I use {{suggested_value}} or {{suggested_games}} in emails, SMS or popups? A: No. Dynamic tags are tied to the mission's task configuration and work only inside the mission. For communications, use the player's state tags.
Q: The tag works in the mission name but shows as plain text in the Terms & Conditions. Why? A: Most likely caching. If the mission is configured correctly and the tag is replaced in other fields, clear the cache and check again.
Q: Can I combine favorite sport market with favorite sport type or league in one task?
A: Yes. A task can have one favorite sport market condition and one favorite sport type or league condition. Use {{suggested_market}} and {{suggested_sport}} together in the task name.
Q: Which tags can I use in mission text?
A: {{suggested_games}}, {{suggested_sport}}, {{suggested_market}}, {{suggested_value}} and {{suggested_amount}}.
Q: What is the difference between {{suggested_value}} and {{suggested_amount}}?
A: {{suggested_value}} shows the player’s recommended amount. {{suggested_amount}} shows the amount the player has to reach for a Prop to Prop target, which is the multiplier × the recommended amount. With a 2× target and a recommended deposit of 50 EUR, {{suggested_value}} shows 50 EUR and {{suggested_amount}} shows 100 EUR.
Q: I used a tag in the mission name and the mission has several tasks. Which value is shown? A: The value from the first task, in mission order, that has a matching condition or target. To show a different value per task, put the tag in each task name.
Q: Why does my task name show {{suggested_market}} as text? A: The task has no favorite sport market condition, or the player has no favorite markets. A task name can only show values from its own conditions.
Last updated
Was this helpful?