> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/gamification-basics/missions/dynamic-missions.md).

# 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 sport bet amount
* Recommended deposit amount

Each player sees a personalized version of the same mission, based on their historical activity.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-b6b55d4929403a6be0489fe7184fabca057bc2c4%2FScreenshot_18.png?alt=media" alt=""><figcaption><p>BO: Mission task setup</p></figcaption></figure></div>

{% hint style="success" %}
**Note:** Populating these properties requires activation. Please contact your Success Manager for more details.
{% endhint %}

#### 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 UT&#x43;**,** and updates are delivered through the system event `Core: favorite/recommended metrics update` (technical name `core_fav_game_update`). Sport favorites (sport type, league and market) are delivered through the system event `Core: favorite/recommended sport update`.

Recommended amounts are visible in the user profile in the CRM tab for each player

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-b68c8a66d4a63ed640344aaf9104529aed8a8697%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

👉 Read more about:

* [Favorite product, game, game type & game provider](https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider)
* [Recommended bet & deposit amounts](https://help.smartico.ai/welcome/products/ai-models/recommended-bet-and-deposit-amounts)

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

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-ff7f5bfea773d50aa2958e470ae52cd65c4ad26d%2FScreenshot_24.png?alt=media" alt=""><figcaption></figcaption></figure></div>

### How to Set Up a Dynamic Mission

1. Create a Mission - Dynamic missions are configured inside standard mission templates.
2. 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: Bet`
* `Casino: Bet-Win`
* `Casino: Win`
* `Acc: Deposit Approved`

**Step 2: Add Property-to-Property Conditions**

Dynamic missions rely on property-to-property comparisons.

**Example for Favorite Game Mission**

1. Favorite game name, top 3 → has any of → Casino: Bet Game Name
2. Progress is made only when the player bets on their own favorite casino games.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-2780a2e139a22143ba24062fbe4a0766685a0788%2FScreenshot_17.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**Example for the Recommended Deposit Mission**

1. Accounting: Last Deposit Amount >= Core: recommended deposit amount
2. Progress is made only when the deposit is at least the player’s recommended deposit amount.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-ab7c559b93679753776bfd4685b0d8effb8d0f16%2FScreenshot_42.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**Example for Recommended Casino Bet Mission**

1. Casino: Bet Amount >= Core: recommended casino bet amount
2. Progress is made only when the bet is at least the recommended casino bet amount.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-4eca4241512588577268d351b68ebebeea79ac2e%2FScreenshot_41.png?alt=media" alt=""><figcaption></figcaption></figure></div>

Supported operators for favorites:

* `has on pos.1 any of` – favorite in position 1
* `has on pos.2 any of` – favorite in position 2
* `has on pos.3 any of` – favorite in position 3
* `has any of` – any favorite in the top 3
* `doesn't have any of` – excludes favorites in top 3

{% hint style="success" %}
This logic applies equally to favorite game types and favorite providers. The same operations are available for Favorite sport market.
{% endhint %}

### 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:

```
Make 100 bets on {{suggested_games}}!
```

Will automatically become:

```
Make 100 bets on Book of Dead, Sweet Bonanza, Gates of Olympus!
```

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:

```
Deposit {{suggested_value}} and get your reward!
```

Will automatically become:

```
Deposit 50 EUR and get your reward!
```

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:

```
Place 3 bets on {{suggested_sport}}
```

Will automatically become:

```
Place 3 bets on Football, Basketball, Tennis
```

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:

```
Place 3 bets on {{suggested_market}}
```

Will automatically become:

```
Place 3 bets on Over/Under, 1x2, Both Teams to Score
```

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:

```
Deposit {{suggested_amount}} in total
```

Will automatically become:

```
Deposit 100 EUR in total
```

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

| Operator in the condition   | The tag shows                                                             | Example output               |
| --------------------------- | ------------------------------------------------------------------------- | ---------------------------- |
| 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, Accounting: 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:

| Recommended amount | Multiplier | Player sees |
| ------------------ | ---------- | ----------- |
| 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.

{% hint style="info" %}
**Note:** For a task created before `{{suggested_amount}}` was available, open the task and save it again, so the multiplier is stored for the tag.
{% endhint %}

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

{% hint style="info" %}
**Note:** After you add a tag to an existing mission, the change may take a short time to appear because of caching. If the tag is still shown as plain text in one field while it is replaced correctly in the others, clear the cache and check again.
{% endhint %}

#### 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`.

| Situation                                                       | Mission name, sub-header, description, T\&C | Task name                                         |
| --------------------------------------------------------------- | ------------------------------------------- | ------------------------------------------------- |
| 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             |

{% hint style="info" %}
When tasks target different favorites or amounts, put the tags in the task names and keep the mission name general. A tag in the mission name always shows the first matching task’s value.
{% endhint %}

#### 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 of` or `has on pos.3 any of` and 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)

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-61a19e4c2e84f7f2293024112b67236fcd49faa8%2FScreenshot_12.png?alt=media" alt=""><figcaption></figcaption></figure>

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

{% hint style="success" %}
Locking is available only when using property-to-property comparisons. Favorite conditions on a task share one Lock switch, named after them (for example **Lock Favorite Game/Type/Provider**). A recommended amount condition or a Prop to Prop target has its own switch, **Lock Recommended Deposit/Bet Amount**. For favorite sport market conditions, use the **Lock Favorite Sport Market** toggle. If the same task also has a favorite sport type or league condition, the toggle is shown as **Lock Favorite League/Sport, Favorite Sport Market** and locks both.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-83cfd63a5dc0f8294093fa2ff827c91867159dde%2FScreenshot_19.png?alt=media" alt=""><figcaption></figcaption></figure></div>

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

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-351e39851d097450524e19db1a1bee8116f4099c%2FScreenshot_9.png?alt=media" alt=""><figcaption></figcaption></figure></div>

### Example Use Cases

**Generic Favorite Game Mission:**

1. Make 100 bets on any of your top 3 favorite games.
2. The player can progress by playing any of their current favorites.
3. 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.<br>

**Specific Position Mission:**

1. Make 100 bets on your the most favorite game.
2. Only progress when the player plays their top-ranked game (position 1).
3. The mission task name 'Make 100 bets on `{{suggested_games}}` will be transformed to 'Make 100 bets on A'<br>

**Specific Game in Favorite Position:**

1. Play your #1 favorite game: Book of Dead.
2. Only if this specific game is the player's game (in position 1) he can progress
3. If their favorites change, they’ll still see the mission, but won’t be able to progress further.<br>

**Recommended Deposit Amount:**

1. Make 5 deposits of your recommended amount
2. Player progresses only if the deposit equals their recommended value
3. Task name: Make 5 deposits of {{suggested\_value}}
4. UI example: Make 5 deposits of 50 EUR<br>

**Recommended Casino Bet Amount:**

1. Make 10 bets with your recommended casino bet amount
2. Player progresses only if each bet matches the recommended value
3. Task name: Make 10 bets with {{suggested\_value}} each
4. UI example: Make 10 bets with 5 EUR each<br>

**Generic Favorite Sport Mission (Top 3 Sports):**

1. Place 3 bets on any of your top 3 favorite sports.
2. The player can progress by placing bets on any of their top 3 sports (e.g., Football, Basketball, or Tennis).
3. The mission task name: `Place 3 bets on {{suggested_sport}}` transforms to `Place 3 bets on Football, Basketball, Tennis`.
4. Recommended: Enable **Lock Favorite League/Sport** if the task requires multiple bets, so the sports remain consistent throughout the mission round.<br>

**Top League Mission (Position 1 Favorite League with Lock):**

1. Place 5 bets on your #1 favorite league.
2. The player progresses only when betting on their top-ranked league (e.g., Premier League).
3. The mission task name: `Place 5 bets on your favorite league: {{suggested_sport}}` transforms to `Place 5 bets on your favorite league: Premier League`.
4. 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.<br>

**Specific League in Favorite Position:**

1. Bet on the UEFA Champions League (only active for players who have it as their #1 league).
2. Only players who currently hold UEFA Champions League in position 1 of their top leagues can progress.
3. If their favorites shift prior to starting, they will still see the mission but cannot progress until it returns to position 1.<br>

**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.<br>

**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 Name, 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.<br>

**Recommended Sport Bet Amount:**

1. Place 5 sport bets of at least your recommended sport bet amount.
2. Condition: Sport: Bet Amount >= Core: recommended sport bet amount.
3. Task name: `Place 5 sport bets of at least {{suggested_value}}`
4. UI example: Place 5 sport bets of at least 10 EUR<br>

**Prop to Prop Wagering Target:**

1. Wager 3 times your recommended casino bet amount in total.
2. Target: Total amount should reach, Prop to Prop enabled with 3 × Core: recommended casino bet amount.
3. Task name: `Wager {{suggested_amount}} in total`
4. UI example for a player with a recommended casino bet of 50 UAH: Wager 150 UAH in total<br>

**Per-Bet Amount and Total in One Task:**

1. Bet at least your recommended casino bet amount per spin, and 10 times that amount in total.
2. Condition: Casino: Bet Amount >= Core: recommended casino bet amount. Target: Prop to Prop enabled with 10 × Core: recommended casino bet amount.
3. Task name: `Bet at least {{suggested_value}} per spin, {{suggested_amount}} in total`
4. UI 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.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-47c522e38c2083999734fb9b49269f4afa3cf76a%2Fimage%20(9).jpg?alt=media" alt=""><figcaption></figcaption></figure>

<mark style="color:purple;">Read more about Favorite games and Game types:</mark>

{% embed url="<https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider#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 the player's recommended amount 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}}`.

{% hint style="info" %}
**Note:** Keep in mind that the recommended amount is dynamic and may change over time.
{% endhint %}

**How to Configure in BackOffice:**

1. Navigate to Gamification → Missions and edit or create a mission task.
2. Select the task type: "Complete action a few times, check a SUM of attribute" (e.g., Deposit total or Bet total).
3. Choose the triggering action and the property to accumulate (e.g., Casino: Bet Amount).
4. In the "Total amount should reach" section, switch the "Enable 'Prop to Prop' for 'Total amount should reach'" toggle to Yes.
5. Configure the dynamic calculation fields:
   * **Multiply**: Set the multiplication factor (defaults to 2x).
   * Property: Select the recommended amount used as the baseline: **Core: recommended deposit amount**, **Core: recommended casino bet amount** or **Core: recommended sport bet amount**. Other player properties cannot be used here.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-9ea6bf0ba86caf5dc61c989cc71d7889c7213a2a%2FScreenshot%20at%20Oct%2001%2016-50-26.png?alt=media" alt=""><figcaption></figcaption></figure>

**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. Progress already made is kept with and without the lock. Without the lock, the games, sports or amounts the task expects can change when the player's favorites or recommended amounts change.

**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**](https://help.smartico.ai/welcome/technical-guides/games-catalog-api.md)**?**\
**A:** Names of the games are taken from the bets/wins [transactions](https://help.smartico.ai/welcome/technical-guides/data-integration#casino-bets-and-wins). At this point, they are not connected to the game details from the [Games Catalog](https://help.smartico.ai/welcome/technical-guides/games-catalog-api.md).

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/gamification-basics/missions/dynamic-missions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
