Configuring Ads in Game Server
Chunk #2
Settings List
In the table below, you’ll find all settings available in Base Ad Config and their descriptions. Click on the expand to open the list.
Fields in Ads Config
Find [here](/wiki/spaces/QA/pages/323878913/Types+of+ads+and+its+requirements) detailed information on the types of ads and its requirements.
| ### **Rewarded Videos** Rewarded videos are a type of incentivised advertising that rewards players for watching a promotional video. |
| **Field Name** | **Description** | **Comments** |
| **Placement Bank** | Bank with the list of rewarded video placements. | Type: Dropdown with placement banks as options. |
| **Overall Rewarded Video Limit** | The total limit of rewarded videos a player can watch. | - Type: Integer |
| **Overall Rewarded Video Limit Reset Time** | The number of hours (after midnight device time) to reset this limit. | - Type: Integer |
| **Bidding floor CPM for rewarded videos** | Floor value to be sent to MAX for rewarded video bidding. | - Type: Float - **Bidding floor CPM for rewarded videos** is available from tripledot-platform-ads 1.3.0 |
| **Consecutive Google Ads Limit** | A counter for the number of consecutive Google ads shown, so that you can control when we stop sending requests to the Google Direct auction and show the MAX ad currently in the cache. | - Type: Integer - **Consecutive Google Ads Limit** is available from tripledot-platform-ads 2.5 |
| **Enable interstitial instead of rewarded video** | If the toggle is ON, rewarded video can be replaced with interstitials in case there is no cashed rewarded videos or the price for interstitial is higher than rewarded video. | - Type: Integer |
| **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. | This setting is described in [detail here](/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#MAX-Rewarded-Videos-Ad-Units). |
| **Ad Slots Bank** | Select from the list of predefined Ad Slots banks. | - Type: Dropdown with the pre-configured options. |
| **Rewarded Videos Request Throttling** | Maximum memory in MBs to be allocated for loading the videos | - Type: Integer |
| ### **Settings Available in both Rewarded Videos and Interstitial Tabs** |
| **Postbid CPM Floor Multiplier** |
| **Postbid CPM Floor Multiplier Type** | Select the type of CPM floor multiplier strategy. | Type: Dropdown with the following options: - **Static** : A single, fixed multiplier. - **Range** : A range of multipliers with steps. - **Waterfall** : Multiple multipliers applied in sequence. |
| **Min Postbid CPM Floor Multiplier** | Provide Minimum Postbid CPM floor Multiplier below which it can’t go down | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range or Static - **Max Postbid CPM Floor Multiplier** is available from tripledot-platform-ads 2.4.0 if If **Postbid CPM floor Multiplier type** = Range. |
| **CPM Multiplier Step in range** | Specify the step value between each multiplier in the range, incrementing from the minimum to the maximum. | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range |
| **Max Postbid CPM Floor Multiplier** | Define the upper limit of the CPM floor multiplier when the "Range" option is selected. | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range |
| **Initial value** | Set up initial CPM from which range will start working. | Type: Float - Optional - Default: empty - If the field is empty, Min Postbid CPM Floor Multiplier is used. - **Initial value** is available from tripledot-platform-ads 2.5 |
| **Levels. Type** | Select the type of levels for waterfall multiplier type. | Type: Dropdown with the list of following options: - Fixed - Multiplier - Default: Fixed |
| **Levels. Postbid CPM Floor** | Specify the Postbid CPM Floor Value based on the selected level type. | - Type = Float - Empty by default - Mandatory if Level is added - Min: 0.0 |
| **Google Postbid IDs and Google Postbid Requests Limit Counter** |
| **Google Postbid Android ID** | Enter the **Postbid ID** specific to **Google Ads** for the Android platform. This ID helps configure and identify the Android app in Google's post bidding process. | Post bidding typically refers to bidding for an ad placement after an initial bid request. |
| **Google Postbid iOS ID** | Enter the **Postbid ID** specific to **Google Ads** for the iOS platform. Like the Android ID, this iOS ID configures and identifies the iOS app in Google's post bidding process. | |
| **Google Postbid Requests Limit Counter** | The **Google Postbid Requests Limit Counter** field sets a maximum number of requests that can be sent to Google Postbid before an ad is shown. | This number resets once a MAX ad is displayed. **Google Postbid Requests Limit counter** Google Postbid Requests Limit Counter is available from tripledot-platform-ads 2.5.0 |
| ### **Interstitials** An interstitial ad is a full-screen ad that covers the entire interface of the game. |
| **Field Name** | **Description** | **Comments** |
| **Placement Bank** | Bank with the list of interstitials placements | |
| **Restrictions for Newcomers (Interstitials Setting)** |
| **Enabled** | Enables the restrictions for newcomers | |
| **Relevant** | This dropdown offers 2 options: - For first session only (interstitial will appear on the first session of the game) - Through all the sessions (interstitial will appear in all sessions) | |
| **Block ** | This dropdown allows you to choose 2 options to block the interstitials: - Interstitials for first N seconds - First N interstitials | The seconds are determined in the field **Seconds** below. |
| **Seconds** | Numeric field to determine the seconds or the number of interstitials blocked for the player | |
| **Timer Counts on App Minimisation** | This field determines whether to count the time when the app is live but minimised to track time between interstitials | |
| **Frequency Restrictions (Interstitials Setting)** |
| **Config Type** | - Config Based on Network - Standard Config | |
| **Time-based: minimum time allowed between interstitials** | The ad will be shown only if the required minimum time has passed since the latest successful impression | Time in seconds |
| **Add to "Min time allowed per impression" for every successful impression ** | Click to enable the ability to increase the minimum time allowed between interstitials for the player for every successful impression | Disabled by default |
| **Per impression** | Adjusts the minimum time per impression | Time in seconds |
| **Max value** | Adjusts the maximum time between impressions | Time in seconds |
| **Reset after Rewarded Video** | After every rewarded video, time between interstitials will be tracked from zero | |
| **Reset after Interstitial** | After every interstitial, time between interstitials will be tracked from zero | Enabled by default. **Reset after Interstitial** is ignored by clients with platform version older than 5.4.1 |
| **Timer Counts on App Minimisation** | This checkbox determines whether to count the time when the app is live but minimised to track time between interstitials | Disabled by default |
| **Custom Frequency Restrictions (Interstitials Setting)** |
| **Key** | Identification key. You can add a new key or reuse any key that already exists in Ad Config | |
| **Min count allowed between Interstitials** | The ad will be shown only if required number of particular points in game is passed since the latest successful impression | |
| **Reset after rewarded video** | After every rewarded video, time between interstitials will be tracked from zero | |
| **Reset after Interstitial** | After every interstitial, time between interstitials will be tracked from zero | Enabled by default. **Reset after Interstitial** is ignored by clients with platform version older than 5.4.1 |
| **Back-to-back frequency restriction (Interstitials Setting)** |
| **Show Back-to-back interstitial after** | Provide number of interstitials after which Back-to-back interstitial should be shown. | If the value is set to "0," a back-to-back interstitial will be displayed after every instance. If the value is set to "1," a back-to-back interstitial will be displayed every second instance. |
| **Impression Restriction (Interstitials Setting)** |
| **Minimum CPM value. Min CPM Type** | Minimum CPM value that an interstitial ad should have in order to be shown. There are 2 options: - **Static** , where you determine a set value in dollars - **Formula** , where a formula based on the past 50 collected events calculates the bidding floor. | - Default: Static - If **Static** is selected, Game Server will display only the field “Static floor CPM“ - 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/3682861062/Copy+of+Configuring+Ads+in+Game+Server#Setting-the-CPM-Floor). |
| **Minimum CPM value. Static Floor CPM** | Specify a static value for the Bidding Floor CPM. | - Type : Float - Default: Empty - If “Return static value“, field is selected “Static floor CPM“ is mandatory. |
| **Pause duration to resume ad(Interstitials Setting)** |
| **Min** | Specify the minimum part of the range for the pause duration to resume ad. **Example: Pause Duration: 1-5 minutes.** Minimum part of the pause duration is 1 in this example. | - Type = Float - Empty by default |
Rewarded Videos Configuration
Chunk #2
1.8 Postbid CPM Floor Multiplier
This setting allows you to define how the CPM floor is managed for postbid ads. There are three options available for configuring the **Postbid CPM Floor Multiplier** :
- **Static** – A single, fixed multiplier is applied.
- **Range** – A flexible range of multipliers is applied with incremental steps.
- **Waterfall** – Multiple multipliers are applied in sequence, cascading through different values.
1. Enable the **Postbid CPM Floor Multiplier** field by clicking on the  **[green + sign]**.
2. From the **Postbid CPM Floor Multiplier Type** dropdown, select the relevant option.
3. Fill in the fields following the information listed in the table below.
Based on the selected type of **Postbid CPM Floor Multiplier** , the fields displayed will differ.
**Fields for Static Type:**
**Fields for Range Type:**
**Fields for Waterfall Type:**
| **Field Name** | **Description** | **Comments** |
| **Postbid CPM Floor Multiplier Type** | Select the type of CPM floor multiplier strategy. | Type: Dropdown with the following options: - **Static** : A single, fixed multiplier. - **Range** : A range of multipliers with steps. - **Waterfall** : Multiple multipliers applied in sequence. |
| **Min Postbid CPM Floor Multiplier** | Provide Minimum Postbid CPM floor Multiplier below which it can’t go down | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range or Static - **Max Postbid CPM Floor Multiplier** is available from tripledot-platform-ads 2.4.0 if If **Postbid CPM floor Multiplier type** = Range. |
| **CPM Multiplier Step in range** | Specify the step value between each multiplier in the range, incrementing from the minimum to the maximum. | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range |
| **Max Postbid CPM Floor Multiplier** | Define the upper limit of the CPM floor multiplier when the "Range" option is selected. | Type: Float - Min: 0 - Max: 2 - Default: empty - Available and Mandatory only if **Postbid CPM floor Multiplier type** = Range |
| **Initial value** | Set up initial CPM from which range will start working. | Type: Float - Optional - Default: empty - If the field is empty, Min Postbid CPM Floor Multiplier is used. - **Initial value** is available from tripledot-platform-ads 2.5 |
| **Levels. Type** | Select the type of levels for waterfall multiplier type. | Type: Dropdown with the list of following options: - Fixed - Multiplier - Default: Fixed |
| **Levels. Postbid CPM Floor** | Specify the Postbid CPM Floor Value based on the selected level type. | - Type = Float - Empty by default - Mandatory if Level is added - Min: 0.0 |
### 1.9 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.
This setting is described in [detail here](/wiki/spaces/KB/pages/4304109569/Setting+up+Ad+Units#MAX-Rewarded-Videos-Ad-Units).
### **1. 10 Bidding floor CPM for rewarded videos**
The **Bidding Floor CPM for rewarded videos** defines the minimum price (in cost-per-thousand impressions) that advertisers must meet for their rewarded video ads to be shown.
| **Field Name** | **Description** | **Comments** |
| **Bidding floor CPM for rewarded videos** | Floor value to be sent to MAX for rewarded video bidding. | - Type: Float - **Bidding floor CPM for rewarded videos** is available from tripledot-platform-ads 1.3.0 |
1. Enable **Bidding floor CPM for rewarded videos** by clicking on the  **[green + sign].**
2. In the field, specify the floor value.
* * *
### **1.11 Ad Slots Bank**
The **Ad Slots Bank** defines the Ad slots bank to be sent to the client.
| **Field Name** | **Description** | **Comments** |
| **Ad Slots Bank** | Select from the list of predefined Ad Slots banks. | - Type: Dropdown with the pre-configured options. |
1. Enable **Ad Slots Bank** by clicking on the  **[green + sign].**
2. From the dropdown, select the relevant option. The dropdown consists of Ad Slots pertaining to Rewarded Videos. For steps to configure the Ad Slots refer to this [User Guide](/wiki/spaces/KB/pages/3996647517/Ad+Slots+Configuration#Configuring-Ad-Slots).
* * *
### **1. 12 Rewarded Videos Request Throttling**
The **Rewarded Videos Request Throttling** setting defines the maximum number of memory to be allocated for loading the videos.
| **Field Name** | **Description** | **Comments** |
| **Rewarded Videos Request Throttling** | Maximum memory in MBs to be allocated for loading the videos | - Type: Integer |
1. Enable the **Rewarded Videos Request Throttling** setting by clicking on the  **[green + sign].**
2. In the field, specify the memory value.
* * *
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.