Inventory
      Back to home
      1. Help Center
      2. Enterprise Modules
      3. Inventory

      Mapping rules tab

      In this tab, users can configure the mapping rules for a specific Inventory. These rules ensure that setups made in other platforms or systems are properly reflected in the requests sent to the Inventory.

      Mapping Rules – Customizing Request Mapping

      Content

       

      Overview

      The Mapping Rules tab enables you to define custom rules that modify how incoming request properties are mapped to target properties in your inventory setup. This is useful for aligning your system with an inventory’s configuration, such as mapping bundles or domains to placements.

      Key Requirement: When you create a mapping rule for a Domain or Bundle, you must associate it with data records. Otherwise, your advertiser’s activity will be paused.

       

       

      How to Access Mapping Rules

      • For New Advertisers:

        • Create and save the inventory’s General tab

        • Go to the Mapping Rules tab in the inventory’s details form

      • For Existing Advertisers:

        • Navigate to Inventories Module > Inventories List

        • Click the edit icon in the Actions column

        • Go to the Mapping Rules tab

      • Alternative Access: Manage all mapping rules across advertisers in the Inventory Module > Mapping Rules, allowing for searching, filtering, bulk editing, and data records management.

       

      Creating and Managing Mapping Rules

       

      1.  Defining Rules

      • Each rule connects an Incoming Property (the request dimension being matched) to a Target Property (the request dimension that holds the mapped value).

      • Example: map domains or bundles (incoming) to placements (target).

      • Note: Defining a mapping rule for a domain or bundle automatically creates an allowlist for that property. No need to duplicate them in the Lists module.

       

      2.  Adding Data Records

      • Add records manually or by uploading a CSV/TXT file (max size 10MB).

      • Use the special value $_other_$ when you wish to catch all values not explicitly listed.

        • ⚠ Important: This rule will not act as an allowlist.

      • Please make sure records are always added for bundle/domain mappings; otherwise, activity will be paused.

       

      3.  Bulk Replacement

      • Use bulk replacement to substitute a specific TO value across all data records in a mapping rule.

       

      4.  Applying Rules Across Inventories

      • While creating/editing a mapping rule, you can apply it to multiple inventories or to All Partners with one switch.

      • ⚠ Be advised: Applying rules globally may cause conflicts if other inventories already have their own mapping rules.

       

      Understanding Incoming Properties

      Incoming properties represent dimensions in the bid request you want to match.
      Examples include:

      • ALL_REQUESTS (matches all incoming requests, can only contain one record)

      • APP_ID, APP_NAME, BUNDLE, DOMAIN, SITE_ID, SITE_URL

      • BID_FLOOR, PRICE, DEAL_ID, MEDIA_TYPE

      • For the full list of incoming properties, refer to Mapping rules Metrics.

       

      Understanding Target Properties

      Target properties represent where the mapped values are applied in the inventory setup.
      Examples include:

      • APP_ID, APP_NAME, BID_FLOOR, PRICE, PLACEMENT, OS, SITE_URL

      • 'BLOCKED_xxx' properties:

        • BLOCKED_ADVERTISERS, BLOCKED_APPS, BLOCKED_ATTRIBUTES, BLOCKED_CATEGORIES 

        • The values must be in quotes, comma-separated.
          For example: "value1, value2, value3, value4, value5"

      • For the full list of target properties, refer to Mapping rules metrics.

       

      Deal ID rules

      • The format is: id|price|seat
      • Multiple seats: id|price|seat1,seat2,seat3
      • Multiple deals: separate with $ 
        Example: my_deal|3.3|234$my_deal2|0|34,23
        • Per this example, Gamoshi will create two private deals:
          First deal
          name: my_sp_deal
          price: 3.3 and 
          Seat: 234
          Second deal
          name: my_sp_deal_2
          price: auction price 
          Seat: 34,23
        • ⚠ The Price and Seat are not mandatory. 

       

      Pricing Rules

      • Price = 0/nothing → use the bid request price

      • Price > 0 → use the defined price

      • Price < 0 (-1) → use the bid floor price

       

      • Video placement types

        • For your Video placement type mapping, use the  ID number only (x) from the detail values lists below.

        • VIDEO_PLACEMENT_TYPE:
          (1) In-Stream, (2) In-Banner, (3) In-Article, (4) In-Feed, (5) Interstitial

        • VIDEO_PLCMT:
          (1) Instream, (2) Accompanying Content, (3) Interstitial, (4) Standalone 

       

       

      Filters

      Mapping rules can be filtered by:

      • Ad Sizes

      • Ad Type

      • Device Type

      • Countries

      • Source

      • Operating System

       

      Troubleshooting

      • Advertiser paused unexpectedly?

        • Check if a domain/bundle mapping rule exists without data records.

      • Conflicting behavior?

        • Verify/check if rules are being applied to multiple inventories via "All Partners."

      • Not seeing expected mapping results?

        • Confirm correct Incoming/Target property pairing.

        • Validate CSV/TXT formatting & file size.

        • Ensure "Block_xxx"   record values are enclosed in quotes and comma-separated.