Player Metrics Configuration Reference¶
This page is a quick-reference companion to the Player Metrics Triggers guide. Use it to check which configuration combinations are valid.
Qualification Metrics and Operators¶
Not every operator is available for every metric. The table below shows all valid combinations.
| Metric | = |
> |
>= |
< |
<= |
|---|---|---|---|---|---|
| Total Stake Amount | Yes | Yes | |||
| Total Win Amount | Yes | Yes | |||
| Bet Count | Yes | Yes | Yes | ||
| Player Net Profit | Yes | Yes | Yes | Yes | |
| Player Net Profit Margin | Yes | Yes | Yes | Yes |
Note
Multiple conditions are combined with AND logic. For example, Total Stake Amount >= 100 AND Player Net Profit < 0 means the player must have wagered at least 100 and ended with a net loss.
Currency Modes¶
| Setting | Metrics Calculated In | Best For | Dynamic Free Bet Output Currency |
|---|---|---|---|
| Wallet Currency | The player's own wallet currency | Single-currency operations (e.g., all players use NGN) | Must match both the selected reward currency and the chosen wallet currency |
| Base Currency | A common base currency (USD) after conversion | Multi-currency operations where you need a fair comparison across regions | Taken from the selected reward currency |
Note
For Dynamic Free Bet, Output Currency is not an independent setting. It must always match the selected Free Bet reward currency.
Reward Configuration Modes¶
There are two ways to assign rewards. Each has different requirements and trade-offs.
| Tiered Rewards | Dynamic Free Bet | |
|---|---|---|
| How it works | Maps metric value ranges to different pre-defined rewards | Computes bet value and/or bet count from a player's metrics |
| Reward type required | Any reward in the campaign | Free Bet reward |
| Number of rewards | Multiple (one per tier) | Single |
| Player gets same value? | All players in the same tier get the same reward | Every player can get a different value |
| Use when | You want distinct reward tiers (Bronze/Silver/Gold) | You want proportional rewards (e.g., % cashback) |
Note
A Dynamic Free Bet can target a fixed or ranged Free Bet reward. However, any configuration that uses Relative to Metric for either Bet Value or Bet Count requires a reward that allows enrollment overrides — in practice, a ranged Free Bet.
If the selected reward is fixed, both configured values must remain Absolute and match the reward's fixed bet value and bet count.
Dynamic Free Bet Permutations¶
When using a Dynamic Free Bet, both Bet Value and Bet Count can be configured independently as either a fixed number or a value derived from a player metric.
Bet Value Options¶
| Mode | Description | Example |
|---|---|---|
| Absolute | Every qualifying player gets the same bet value | Bet Value = 5.00 |
| Relative to Metric | Bet value is calculated from a metric: (Metric × Multiplier), clamped to Min/Max | Bet Value = Player Net Profit × -0.10, Min 1.00, Max 50.00 |
Bet Count Options¶
| Mode | Description | Example |
|---|---|---|
| Absolute | Every qualifying player gets the same number of bets | Bet Count = 1 |
| Relative to Metric | Bet count is calculated from a metric: (Metric × Multiplier), clamped to Min/Max | Bet Count = Bet Count × 0.1, Min 1, Max 10 |
All Combinations¶
These four combinations cover every possible Dynamic Free Bet configuration:
| # | Bet Value | Bet Count | Use Case |
|---|---|---|---|
| 1 | Absolute | Absolute | Simple: every qualifying player gets the exact same free bet package (e.g., 1 bet at 5.00) |
| 2 | Relative | Absolute | Cashback: bet value scales with player activity, fixed number of bets (e.g., 1 bet worth 10% of losses) |
| 3 | Absolute | Relative | Volume reward: fixed bet value, but more active players get more bets (e.g., 1.00 bets, count = 10% of their total bets) |
| 4 | Relative | Relative | Fully dynamic: both value and count scale with player metrics |
Note
All four combinations are supported, but any combination that uses Relative to Metric requires a ranged Free Bet reward. If the selected Free Bet is fixed, both Bet Value and Bet Count must stay Absolute.
Tip
Combination #2 (Relative Value, Absolute Count) is the most common pattern. It covers the majority of cashback and activity-based promotions.
Available Metrics for Dynamic Free Bet Calculation¶
The same metrics used for qualification can also drive the reward value and/or bet count.
| Metric | Typical Use in Reward Calculation |
|---|---|
| Total Stake Amount | Cashback as a percentage of total wagered |
| Total Win Amount | Reward proportional to winnings |
| Bet Count | Scale number of free bets by activity volume |
| Player Net Profit | Loss-based cashback (use a negative multiplier to convert losses to a positive reward value) |
| Player Net Profit Margin | Rarely used for reward calculation — better suited for qualification conditions |
Negative Values
When using Player Net Profit for a loss-based cashback, remember that the value is negative for losing players. Use a negative multiplier (e.g., -0.10) to produce a positive reward value. The Min/Max clamps will then ensure the result stays within your intended range.
Evaluation Period Options¶
| Period | Window | Timezone-Aware |
|---|---|---|
| Previous Interval | The previous trigger interval, ending at least 5 minutes before execution | No |
| Previous Day | Midnight to midnight of the previous calendar day | Yes |
| Last 24 Hours | Rolling 24-hour window ending at least 5 minutes before execution | No |
| Previous 7 Days | The 7 calendar days before the current day | Yes |
| Last 7 Days | Rolling 7-day (168h) window ending at least 5 minutes before execution | No |
| Previous Week | Monday to Sunday of the previous calendar week | Yes |
| Custom | A specific duration you define | No |
Validation Rules
The To boundary must resolve to at least 5 minutes in the past, and the configured period must resolve to at least one trigger iteration window. Otherwise the configuration is rejected.
Previous Day vs Last 24 Hours
Previous Day always covers a full calendar day (e.g., Monday 00:00 – Monday 23:59). Last 24 Hours is relative to when the trigger fires, but still ends slightly before execution because of the validation buffer. Choose based on whether you need calendar-aligned reporting or rolling coverage.