Chunks Used in Chat #67

3.1. Frequency Restrictions: Overrides **What Are Overrides?** Overrides allow you to define placement-specific interstitial ad frequency settings that override the global or default frequency restriction rules. This is especially useful when you want to fine-tune the ad experience per ad placement. Each override allows you to define conditions like time-based restrictions specific to that network or placement. **How Overrides Work** - When overrides are enabled, they take precedence over the default config. - You can add multiple override blocks. - Each override can have its own logic tree with AND/OR conditions. **When to Use Overrides** - You want to allow more frequent ads in a low-impact placement (like between levels) but restrict them during gameplay. - A specific network requires custom frequency rules. - You are A/B testing ad frequency strategies for different parts of the game. # 4. Back-to-Back Frequency Restrictions The “Back-to-back frequency restriction” setting allows the configuration of how frequently back-to-back interstitial ads are shown. By using a global setting and optional overrides for specific placements, this feature gives flexibility in managing ad frequency. | **Back-to-back frequency restriction** | | **Field Name** | **Description** | **Comments** | | **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. | 1. First, navigate to **Ad Config \> Interstitials** , and enable the setting. 2. In the “Show Back-to-back Interstitial After" text box, enter an integer value. 3. If required, you can set up overrides for specific ad placements by selecting Overrides. 4. Then, click the particular placement and select the required settings. # 5. Restrictions for Newcomers The "Restrictions for Newcomers" setting allows you to manage how ads are shown to new users in their early sessions. | **Restrictions for Newcomers** | | **Field Name** | **Description** | **Comments** | | **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  |   | 1. Enable the **Restrictions for Newcomers** setting by clicking on the  **[green + sign]**. 2. Fill in the fields following the information listed in the table above. 3. If required, you can set up overrides for specific ad placements by selecting Overrides. Then, click the particular placement and select the required settings.  # 6. Pause Duration to Resume Ads This setting allows Game Server to send a setting that defines a **"Pause duration to resume ad"**. The goal is to specify a time gap during which an ad will be shown to a user when they minimise the game and later return to it. Here’s how it works: 1. User Minimises the Game: When a player minimises the game (e.g., switches to another app or moves to the home screen), the timer starts tracking how long the game is minimised. 2. User Returns to the Game: When the player reopens the game after minimising it, the platform manages the timing and handles the ad display based on the settings provided by the Game Server. 3. Ad Display Based on Time Gap: If the user returns to the game within a predefined time gap (e.g., between 1 and 5 minutes), an ad will be triggered and displayed. This time gap is configurable: | **Pause duration to resume ad(Interstitials Setting)** | | **Field Name** | **Description** | **Comments** | | **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 | | **Max** | Specify the maximum part of the range for the pause duration to resume ad. **Example:** **Pause Duration: 1-5 minutes.** Maximum part of the pause duration is 5 in this example. | - Type = Float - Empty by default | 1. Enable the **Pause duration to resume ad** setting by clicking on the  **[green + sign]**. 2. Fill in the fields following the information listed in the table above.  # 7. Placement Bank The **Placement Bank** is a collection that stores a list of rewarded video placements. It allows you to manage and organise multiple rewarded video ad placements in one centralised location. | **Field Name** | **Description** | **Comments** | | **Placement Bank** | Bank with the list of rewarded video placements.  | Type: Dropdown with placement banks as options. | 1. Navigate to **Ads \> Configuration \> Rewarded Videos** , and enable the **Placement Bank** field by clicking on the  **[green + sign].** 2. Click the empty text box or the down arrow on the right to open the dropdown menu. 3. Choose the appropriate placement bank for your configuration. 4. If the desired placement bank is not listed, you can add a new one by following the instructions listed in the [Interstitial Placements & Interstitial Placement Banks](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/edit-v2/3705274372#Interstitial-Placements-%26-Interstitial-Placement-Banks) section below.  * * * # **8. Interstitials Request Throttling** The **Interstitials Request Throttling** setting defines the maximum number of memory to be allocated for loading the videos. | **Field Name** | **Description** | **Comments** | | **Interstitials Request Throttling** | Maximum memory in MBs to be allocated for loading the videos | - Type: Integer | 1. Enable the **Interstitials Request Throttling** setting by clicking on the  **[green + sign].** 2. In the field, specify the memory value.  # **9. Ad Slots Bank** The **Ad Slots Bank** setting 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. For steps to configure the Ad Slots refer to this [User Guide](/wiki/spaces/KB/pages/3996647517/Ad+Slots+Configuration#Configuring-Ad-Slots).  # **10. Interstitials TDS Ads** This setting allows to advertise TDS games in cases when we don't have ad from mediation platforms. | **Field Name** | **Description** | **Comments** | | **Interstitial TDS Ads config** | Select from the list of predefined TDS Ads. Refer to this [User Guide](/wiki/spaces/KB/pages/4307189763/TDS+Ads+and+TDS+Ad+Banks) to Configure TDS Ads. | - Type: Dropdown with the pre-configured options. - Default: None (not an option to pass validation) - Mandatory | | **Number of seconds before “X” button appears** | Time period in seconds before the close button appears for the player to close the ad. | - Type: Integer - Default: empty - Mandatory - Min: 1 | | **Maximum number of TDS ads per session** | Maximum number of ads the player will receive per session | - Type: Integer - Default: empty - Mandatory - Min: 0 |  # 11. Newcomers CPM floor restriction Configure impression suppression by setting a decreasing minimum CPM floor for new users based on the number of Ad\_Checks, applied across all placements for the first N checks. | **Field Name** | **Description** | **Comments** |

| **Number of seconds before “X” button appears** | Time period in seconds before the close button appears for the player to close the ad. | - Type: Integer - Default: empty - Mandatory - Min: 1 | | **Maximum number of TDS ads per session** | Maximum number of ads the player will receive per session | - Type: Integer - Default: empty - Mandatory - Min: 0 |  # 11. Newcomers CPM floor restriction Configure impression suppression by setting a decreasing minimum CPM floor for new users based on the number of Ad\_Checks, applied across all placements for the first N checks. | **Field Name** | **Description** | **Comments** | | **Initial starting CPM floor value** | Set up initial CPM floor for newcomers | - Type: Float - Mandatory - Default: 1.0 - Min: more than 0 | | **Change type** | Selecting static or multiplier change type | Dropdown with the list of the following values: - Static - Multiplier - Default: Static | | **Reduction value** | Specify Static value or Multiplier for which CPM floor for newcomers should be reduced after each Ad\_Check | - Type: Float - Default: empty - Mandatory - If **Change type** = Static, these validations should be applied - If **Change type** = Multiplier, these validations should be applied | | **Applies for first N Ad\_Checks** | Specify the number of Ad\_Checks for which Newcomers CPM floor restriction should work | - Type: Integer - Default: empty - Mandatory - Min: 1 |  # 12. Network Ranking multiplier Set up a network-specific Ad Ranking multiplier (independent of mediation) using the new “Network ranking multiplier” grouped setting, allowing multiple configurable sections. | **Field Name** | **Description** | **Comments** | | **Networks** | Specify the list of networks for which you want to set Ranking multiplier | Multi-select dropdown with the list of networks. | | **Ranking multiplier** | Provide Ranking multiplier which should be applied to selected networks | - Type: Float - Mandatory if the section is added - Default: empty - Min: 0.0 |  # 13. **Enable DT Postbid POC** | **Field Name** | **Description** | **Comments** | | **Enable DT Postbid POC** | Boolean flag to enable Digital Turbine Postbid POC | Default: False. Allows enabling for some users for testing purposes. |  # 14. Interstitial Placements & Interstitial Placement Banks Placements allow you to identify all the keys used for unique interstitial ad placements in different game features.  Interstitial Placements are used in Interstitial Placement Banks, which are a collection of placements where you can assign a probability for the placement to appear. In the home page of Interstitial Placements you can see which interstitials placements exist, along with their keys and if they’re being used in any bank currently.  

**Introduction** In this page you’ll learn… - What are rules? - How to use rules and combine them? - Available rules **Table of Contents** * * * # Getting Started with Rules Rules are one of the most important components of Game Server, and they can be found in almost every available application. Rules allow you to differentiate entities for specific user groups, and they can be used to target different sets of users. # Basics of Rules Rules are based on logical operators. The 2 operators used are AND and OR: | **AND operator** | **OR operator** | | --- | --- | | Users must match **all added rules** to receive the entity | Users must match **at least one of the rules** to receive the entity  | You can add as many rules inside a section of rules, and you can also combine sets of rules using [Sections](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/2668494860/Rules+in+Game+Server#Sections). Some rules also allow you to add multiple values by using the **[green + button]**.  ### **Example** Let’s say we want to target the following set of users: - From France OR UK  **AND** - Has Game version equal 2.7.0 **AND** - Installed the app 15 days ago or more **How will we represent this in terms of rules?** - Country = France or UK  - Only the users who comply with all of these these conditions will receive the entity  # Sections  Sections allow you to nest sets of rules and combine them to target users more accurately. Sections allow **up to 3 levels of nesting** , and they use different colours so that they can be distinguished easier. Sections also use the basic AND/OR operators to combine rules. Next to **[Add Rules]**, you’ll find **[Add Section]** (1) **.** After clicking the button, a new container will appear on top (2), where you’ll be able to add new rules and select which relation (AND/OR) should have with the other set of rules.  If you added your rules previously, and now you need to create a section, you can use the yellow button **[Convert to a section]** to create sections of rules without having to delete and add the rules in a section.  - If there are rules without a section on the selected level, these rules will be moved to the newly created section - If there are 2 sections, then the system would convert it to a section with 2 sub sections (including top level) - By the click on the ‘Convert to a section’, system converts selected level of nesting into section and puts all the rules and sections from this level under created section - The button is disabled for the 3rd and 4th level of nesting #### **Example** Now we would like to target the following set of users: - Country = France or UK **AND** - Game version = 2.7.0 **AND** - Cohort day \>= 15 **OR**   - Country = France or UK **AND** - Game version =  3.0.0 **AND** - Cohort day \>= 3 **How will we represent this in terms of rules?** To do so, we need to create 2 sections of rules with the operand OR above, and include inside each set, the rules we want to match. Game Server will then look for players matching the rules on the first set OR the second one.  # Named Rule Groups _Named Rule Groups_ allow you to create and save a set of rules that can be later reused in any feature that uses rules, allowing you to save time setting up your configurations.