CPM Percentile Configuration
Chunk #0
# Introduction
A new feature has been introduced to support CPM floor configurations. This feature allows setting CPM floor values based on CPM percentiles. For example, the 80th percentile represents the CPM value below which 80% of impressions fall. Floors can be configured per country or per platform, cohort, and other parameters for the configuration.
* * *
## **New CPM Percentile Configuration Section**
- A new sub-section, **CPM Percentiles** has been added under the Ads menu in the left sidebar.
Navigate to **Ads \> CPM Percentiles \> Interstitials** , and select the  **[green + sign]** to create a new entity.
### **List View and Available Filters**
All the regular filters are available for CPM Percentile configurations.
### **Standard Fields for New/Edit View**
#### **Fields Descriptions**
| **Name** | **Validations** | **Description** |
| --- | --- | --- |
| Name | - Default: Blank - Type: String - **Mandatory** : Yes | Specify the Name for the configuration |
| Priority | - Default: Blank - Type: Integer - **Mandatory** : Yes | Specify the priority of the configuration |
| Label | - Default: Blank - Type: Single-select dropdown - **Mandatory** : No | Select the relevant label from the available options. |
| Platform | - Default: None - Type: Single-select dropdown - Options: None, iOS, Android - **Mandatory** : Yes | **Usage** : Determines the platform used to retrieve CPM values from storage |
| CPM source country | - Default: None - Single-select dropdown - Options: - **Mandatory** : Yes | **Usage:** Defines base country to fetch CPM floor from storage |
| Additional countries to apply CPM | - Default: None - Two fields: - **Mandatory** : Yes | 1. Operator: Use this to define how the selected countries in the second field should be treated in the rule logic. Options: None, IN, NOT IN) 2. List of all countries excluding those already available for selection in the “CPM Source Country” field Choose one or more countries to which the CPM percentile setting should also apply (if using IN) or exclude (if using NOT IN). For the countries selected in this field, CPMs will be taken from country selected in “CPM source country” field |
| Cohort Day | - Default: Blank - Single select dropdown these options: - **Mandatory** : Yes | Selected Cohort range is used to define which cohort day should be used to find required CPM value from the storage. |
| Percentile | - Default: Blank - Single select dropdown with these options: - **Mandatory** : Yes | Selected Percentile value is used to define which Percentile value should be used to find required CPM value from the storage. |
* * *
## Static CPM Configuration for MAX Interstitial Ad Unit
The Static CPM Configuration section allows you to control the behaviour of CPM floor values based on either static settings or percentile-based logic. This section is visible when configuring MAX Interstitial Ad Units, and applies to all Bidding CPM Floor Types.
### Overview of Changes
- Static floor CPM is renamed to Fallback CPM value.
- A new configuration section, Static CPM Configuration, is introduced when the CPM floor type is set to either Static or Formula.
## How CPM Floor Values Are Determined
### When “Use Percentile” Is Enabled
If you enable the “Use Percentile” option, CPM floor values are dynamically selected based on percentile configurations. Here’s how it works:
1. Percentiles are available for Ad Slots for Interstitials / Rewarded Videos and MAX interstitials / Rewarded videos Ad Units.
2. The system identifies matching CPM percentile configurations using:
3. If multiple configurations match, the system selects the one with the highest priority.
4. The CPM value is retrieved from a backend storage system.
5. The retrieved value is sent to the client.
* * *
## Fallback Behaviour
Fallback settings ensure that a CPM floor is still sent even if a percentile-based value cannot be determined.
**Scenario 1: No Matching Configuration Found**
If no percentile config matches the user that is the user does not match to any of selected percentile config by the following parameters: **Platform, CPM Source Country, Additional Countries to apply CPM, or Cohort Day:**
- The system refers to the setting: If no matching configuration.
**Scenario 2: No Percentile Data Available**
If percentile data is unavailable (e.g., backend storage is inaccessible or lacks data):
- The system refers to the setting: If no percentile available.
* * *
### When “Use Percentile” Is Disabled
If “Use Percentile” is disabled, the system does not apply any percentile logic. Instead, the existing CPM logic is used based on either:
- A static CPM value, or
- A formula defined in the configuration.
### New Fields in Static CPM Configuration
| **Name** | **Validations** | **Description** |
| Fallback CPM Value | - Default: Empty - Type: float - Mandatory | Specify a fallback floor value to be sent to Max for interstitial bidding. |
| Use Percentile | - Default: False - Type: Boolean - Mandatory if enabled | Enable to use percentile for CPM floor value. |
| CPM Percentile Configs | - Default: Blank - Multi-select Dropdown - Options: List of available configs - Mandatory if Use Percentiles is enabled | Select the relevant config from the dropdown. |
| If No Matching Configuration | - Default: Return Fallback value - Type: Dropdown - Options: Return fallback value, Return nothing - Mandatory if Use Percentiles is enabled | Select the relevant option if no matching config is available. |
| If No Percentile Available | - Default: Return Fallback value - Type: Dropdown - Options: Return fallback value, Return nothing - Mandatory if Use Percentiles is enabled | Select the relevant option if no percentile is available. |
* * *
### Usage of Percentile Config in both Static and Formula Floor Types
The Percentile configuration is designed to work with both Static and Formula CPM floor types.
**Static Floor Type + (Use Percentile = true)**
When the floor type is set to **Static** and the **Use Percentile** option is enabled:
- The system ignores the fallback static CPM and instead follows the percentile-based logic:
**Formula Floor Type + (Use Percentile = true)**
When the floor type is **Formula** , the behaviour depends on the fallback policy defined in the formula configuration:
- **If “If insufficient ad requests” = “Return Fallback Value”** :
- **If “If insufficient ad requests” = “Return nothing”** :
* * *
## Ad Slots Config Changes
### Configuring Static CPM Floors in Ad Slots
When configuring ad slots, a Static CPM Configuration section is displayed based on your selected CPM floor type.
**When Static CPM Configuration Appears**
This section is shown if:
- CPM Floor Type is set to Static or Formula, or
- CPM Floor Type is Waterfall and Level Type is Fixed
**Key Changes and Fields**
- Static floor CPM has been renamed to Fallback CPM value.
- The configuration section includes the following fields:
The behaviour of these fields is described [here](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4244537368/CPM+Percentile+Configuration#New-Fields-in-Static-CPM-Configuration).
* * *
### **Behaviour in Waterfall CPM Floor Type with Level Type as Multiplier**
- Static CPM configuration is not shown
- Existing multiplier logic remains unchanged
- User can still enter a CPM floor, but percentile logic is not applicable
* * *
## **Summary of Logic**
- Static CPM configuration appears for:
- Percentile logic and fallback behaviour applies consistently across all applicable types
- If Waterfall → Type = Multiplier, only multiplier logic is used (no percentile support)
* * *
Setting up Ad Units
Chunk #0
# **Introduction**
This user guide describes the steps to configure Ad units for Interstitials, Recorded Videos, and Ad Slots.
* * *
# MAX Interstitial Ad Units
This setting allows you to manage and optimise interstitial ad units for the MAX ad platform. By configuring these units, you can control the delivery and behaviour of interstitial ads.
To do so, follow the steps below:
1. Navigate to **Ads \> Configuration \> Interstitials** , and enable **MAX Interstitials ad units** by clicking on the  **[green + sign].**
2. Once enabled, click **[Add].**
3. Fill in the required fields. You can add or remove Ad Units by using the buttons **[+Add]** or **[-Remove]**. There are no limitations regarding the number of Ad Units you can add.
To prevent misconfiguration, the same **Ad Unit ID config** cannot be used in more than one Ad Unit within the same Ad Slot configuration.
For the following fields, any Ad Unit ID already selected will be **filtered out** from the dropdown in other Ad Units:
- **iOS Interstitial ID**
- **Android Interstitial ID**
- **iOS Rewarded Videos ID**
- **Android Rewarded videos ID**
This ensures each Ad Unit in a slot uses a unique Ad Unit ID.
## Max Interstitial Ad Units Fields
| | **Max Interstitial Ad Units** | |
| **Field Name** | **Description** | **Validations** |
| **Max iOS Interstitial ID** | ID string for the ad unit in iOS | - Type: Dropdown with pre-defined options - Default: Empty - Mandatory - At least one symbol must be added |
| **Max Android Interstitial videos ID** | ID string for the ad unit in Android | - Type: Dropdown with pre-defined options - Default: Empty - Mandatory field - At least one symbol must be added |
| **CPM Calculations** |
| **Bidding Floor CPM. Bidding Floor Type** | This field determines the floor value to send to MAX for interstitial bidding. There are 2 options: - **Static** , where you determine a set value in dollars so that the Client can send it to Max for bidding - **Formula** , where a formula based on the past 50 collected events calculates the bidding floor. The settings are the same that apply to [Setting the CPM Floor](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#Setting-the-CPM-Floor). | - Default: Static - If **Static** is selected, Game Server will only display the section “Static CPM Configuration“. This section has the following fields: - If **Formula** is selected, an additional list of parameters for formula is displayed in sub-group called “ **Formula parameters** “. The settings are the same that are used in [Setting the CPM Floor](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#Setting-the-CPM-Floor). |
| **Static CPM Configuration. Fallback CPM Value** | Specify a fallback floor value to be sent to Max for interstitial bidding. | - Type: Float - Default: Empty |
| **Static CPM Configuration. Use Percentiles** | Enable to use percentile for CPM floor value | - Type: Boolean - Default: false - If enabled, system displays additional section to configure CPM percentile config (see details below) |
| **Static CPM Configuration. CPM Configurations** | Select from the list of predefined percentile configurations | - Type: Multi-select dropdown - Default: empty - You can delete any selected config - At least one config should be added - Available only if **Use Percentile = true** - If **Use Percentile** **= false** , setting is hidden - Display priority which is set for each config in the config name in the brackets |
| **Static CPM Configuration.If no matching configuration** | Select the return value if no matching configuration is available | - Type: Dropdown with the list of following values: - Default: Return fallback value - Available only if **Use Percentile = true** - If **Use Percentile** = false, setting is hidden |
| **Static CPM Configuration.If no percentile available** | Select the return value if percentile is not available | - Type: Dropdown with the list of following values: - Default: Return fallback value - Available only if **Use Percentile = true** - If **Use Percentile** = false, setting is hidden |
| **Formula Parameters. Formula Type** | Defines the type for calculating the formula. | Type: Dropdown with the following options: - Median - Average - Default: Median |
| **Formula Parameters.Use successful ad requests only** | Enable if you want to use only successful ad requests for calculation. | - Type: Boolean - Default: OFF - Available if type = formula |
| **Formula Parameters.Min ad requests to apply formula** | This field is used to provide minimum number of interstitials which should be taken into account to calculate formula | - Type: Integer - Mandatory if “Formula” is selected in “Bidding floor type” - Default: Empty - Min 1 - Max: 50 - Must be less than the value provided in the setting “Ad requests to apply formula to“ |
| **Formula Parameters.Ad requests to apply formula to** | This field is used to provide maximum number of interstitials which should be taken into account to calculate formula | - Type: Integer - Mandatory if “Formula is selected in “Bidding floor type” - Default: Empty - Min 1 - Max: 50 |
| **Formula Parameters.Percentage coefficient** | Specify the multiplier to minimise the Bid floor. | - Mandatory if “Formula” is selected in “Bidding floor type” - Min: more than 0 - Max: 2 - Max number of characters after comma = 2 - Incase multiplier results in `max_interstitials.cpm_floor` value with more than 2 characters after comma, GS rounds off the result using math rules. - (e.g. if we have as a result value 1,234 -\> round to 1.23 but if 1.235 -\> round to 1.24) |
| **Formula Parameters.If insufficient ad requests** | Defines the system behaviour when there is insufficient data for calculation. If “Return static value“ is selected, GS will send value from “Static floor CPM“. If “Return nothing“ is selected, GS won’t send any value. | Dropdown with the list of options provided below: - Return fallback value - Return nothing - Default: Return fallback value |
| **Formula Parameters.Use static in case of failed requests** | Enable this in case you want to send static value instead of formula calculation when N latest events have failed. | - Type: Boolean - Default: OFF - Disabled if “Use successful ad requests only” = true |
| **Formula Parameters.Number of failed requests** | Specify a number of latest failed requests. If this number is reached, static value will be used instead of formula calculation. | - Type: Integer - Default: empty - Disabled if “Use static in case of failed requests” = OFF - Mandatory and enabled if “Use static in case of failed requests“ = ON - Min: 1 - Max: 50 |
Setting up Ad Units
Chunk #1
Setting the CPM Floor
**Setting the CPM Floor**
Game Server provides two types of validations for Bidding Floor Type.
- Static
- Formula
**Choosing a Bidding Floor Type**
There are two options for defining the CPM floor:
**A. Static CPM Floor**
- **Definition** : Sends a fixed CPM value to the client, which is forwarded to the mediation system (e.g., Max, Google, or Meta).
- **How to Configure** :
- **Behaviour** : The same CPM value will always be used for bidding.
**B. Formula-Based CPM Floor**
- **Definition** : Dynamically calculates the CPM floor using the following formula:
- If **Median** is selected in the Formula type dropdown field:
_interstitial\_cpm\_floor = Median (most recent **N** CPM values) \* **K** _
- If **Average** is selected in the Formula type dropdown field:
_interstitial\_cpm\_floor = Average (most recent **N** CPM values) \* **K** _
This formula allows you to determine the number of CPMs stored ( **N** ). If the number of CPMs is lower than **X** (Minimum number of events required for calculation), Game Server won’t return anything, or will return a static value as determined by the settings.
**Determining N for Each Ad Unit**
- N represents the number of most recent CPM values retrieved from a bucket for median calculation.
- **How is N Defined?**
- **Handling Fewer Events than N** :
- **Minimum Number of Events:**
- **Behaviour for Insufficient Events (Fewer than X)**:
- **Multiplier K:**
- **Use successful ad requests only:** Enable/Check if you want to use only successful ad requests for calculation.
- **Use static in case of failed requests:** Enable/Check in case you want to send static value instead of formula calculation when a number of latest requests have failed. if static is selected for fallback value and Percentile is enabled, the system will firstly check if it is possible to use the static CPM based on percentiles. If yes, than the value is obtained from there. If no, the system will use the fallback value OR nothing. In case of nothing usually the system sends 0.0 as floor.
- **Number of failed requests:** Specify number of latest failed requests. If this number is reached, static value will be used instead of formula calculation.
For detailed information on how Analytics Buckets work, refer to this [User Guide](https://tripledotstudios.atlassian.net/wiki/x/BIBUAQE).
* * *
# MAX Rewarded Videos Ad Units
This setting allows you to manage and optimise rewarded videos ad units for the MAX ad platform. By configuring these units, you can control the delivery and behaviour of rewarded videos.
To do so, follow the steps below:
1. Navigate to **Ads \> Configuration \> Rewarded Videos** , and enable **MAX rewarded videos ad units** by clicking on the  **[green + sign].**
2. Once enabled, click **[Add].**
3. Fill in the required fields using the information described in the table below. You can add or remove Ad Units by using the buttons **[+Add]** or **[-Remove]**.
There are no limitations regarding the number of Ad Units you can add.
## Max Rewarded Videos Ad Unit Fields
| **Field Name** | **Description** | **Comments** |
| **Max iOS Rewarded videos ID** | AD unit ID configuration that includes the ID for the Ad unit in iOS | - Type: Dropdown with pre-defined options - Default: Empty - Mandatory - At least one symbol must be added |
| | | |
| **Max Android Rewarded videos ID** | AD unit ID configuration that includes the ID for the Ad unit in Android | - Type: Dropdown with pre-defined options - Default: Empty - Mandatory field - At least one symbol must be added |
| | | |
| **Request limit counter** | This field displays the number of number of requests which client will try to make in order to get an Ad from the mediation platform | - Default: Empty - Mandatory field |
| | | |
| **Auto Retry** | Uncheck this box if you don’t want to retry loading ad units in case the first attempt to load the ad unit fails. Please note this is a client-side setting and the full configuration needs to be done on the Client. | - Enabled by default |
| | | |
| **Sequential Fill** | Uncheck this box if you don’t want to enable sequential filling if the first attempt to load the ad unit fails. Please note this is a client-side setting and full configuration needs to be done on the Client. | - Enabled by default |
| | | |
| **Bidding Floor CPM. Bidding Floor Type** | This field determines the CPM floor value to send to MAX for the rewarded video bidding. There are 2 options: - **Static** , where you determine a set value in dollars so that the Client can send it to Max for bidding - **Formula** , where a formula based on the past 50 collected events calculates the bidding floor. The settings are the same that apply to [Setting the CPM Floor](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#Setting-the-CPM-Floor). - Percentile, which allows setting CPM floor values based on CPM percentiles. For example, the 80th percentile represents the CPM value below which 80% of impressions fall. Floors can be configured per country or per platform, cohort, and other parameters for the configuration. | - Default: Static - If **Static** is selected, Game Server will display the fields “Fallback CPM Value and Percentile Configuration“ |
| | | |
| **Static CPM Configuration. Fallback CPM Value** | Specify a fallback floor value to be sent to Max for Rewarded Video bidding. | - Type: Float - Default: Empty |
| **Formula Parameters.Formula Type** | Defines the type for calculating the formula. | Type: Dropdown with the following options: - Median - Average - Default: Median |
| **Formula Parameters.Use successful ad requests only** | Enable if you want to use only successful ad requests for calculation. | - Type: Boolean - Default: OFF - Available if type = formula |
| **Formula Parameters.Min ad requests to apply formula** | This field is used to provide minimum number of interstitials which should be taken into account to calculate formula | - Type: Integer - Mandatory if “Formula” is selected in “Bidding floor type” - Default: Empty - Min 1 - Max: 50 - Must be less than the value provided in the setting “Ad requests to apply formula to“ |
| **Formula Parameters.Ad requests to apply formula to** | This field is used to provide maximum number of Rewarded Videos which should be taken into account to calculate formula | - Type: Integer - Mandatory if “Formula is selected in “Bidding floor type” - Default: Empty - Min 1 - Max: 50 |
| **Formula Parameters.Percentage coefficient** | Specify the multiplier to minimise the Bid floor. | - Mandatory if “Formula” is selected in “Bidding floor type” - Min: more than 0 - Max: 2 - Max number of characters after comma = 2 - Incase multiplier results in `max_interstitials.cpm_floor` value with more than 2 characters after comma, GS rounds off the result using math rules. - (e.g. if we have as a result value 1,234 -\> round to 1.23 but if 1.235 -\> round to 1.24) |
| **Formula Parameters.If insufficient ad requests** | Defines the system behaviour when there is insufficient data for calculation. CPM percentiles can be used if enough information is not available for formula calculation. If “Return static value“ is selected, GS will send value from “Static floor CPM“. If “Return nothing“ is selected, GS won’t send any value. | Dropdown with the list of options provided below: - Return fallback value - Return nothing - Default: Return fallback value |
| **Formula Parameters.Use static in case of failed requests** | Enable this in case you want to send static value instead of formula calculation when N latest events have failed. CPM percentiles can be used if enough information is not available for formula calculation. | - Type: Boolean - Default: OFF - Disabled if “Use successful ad requests only” = true |
| **Formula Parameters.Number of failed requests** | Specify a number of latest failed requests. If this number is reached, static value will be used instead of formula calculation. | - Type: Integer - Default: empty - Disabled if “Use static in case of failed requests” = OFF - Mandatory and enabled if “Use static in case of failed requests“ = ON - Min: 1 - Max: 50 |
For information on setting up the CPM Floor, [refer to this information.](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#Setting-the-CPM-Floor)
* * *
# **Adding Ad Units to Ad Slots**
While configuring an Ad slot, you need to add Ad units.
- Multiple Ad Units can be added per Ad Slot.
## **Settings for Each Ad Unit**
- **IDs** (Dropdown from Ad Unit IDs based on platform and Ad Slot type).
- **Requests Limit Counter** (Integer, Default: 5).
- **Auto Retry & Sequential Fill** (Available for MAX and META mediation only. Not available for Google).
Refer to the [Ad Slots Ad Unit Fields Table](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#Ad-Slots-Ad-Unit-Fields) for more details.