Google Open Bidding integration (Site & App)

This article is reviewing Google Open Bidding integration for sites & Apps.

To connect your Google Open Bidding publishers in the dashboard, you can create an inventory partner per Google OB publisher. You also have the option to create a 'Default' inventory (one per account) which will be used for all non-publisher specific traffic incoming from Google OB connections. To establish the integration with Google only one general EP should be sent to your account manager in Google  no matter how many Google OB publishers you will connect in the dashboard.

To associate a Google publisher with your dashboard's inventory, when choosing Google Open Bidding integration, you will insert the Google publisher identifier in the inventory setup screen as described in the instructions below:


To connect Inventory by using a Google open bidding (for sites & apps ) follow the next steps:

  1. Create a new Inventory.
  2. Choose a  Source - Site or App. 
  3. Choose 'Google Open bidding' in the 'Inventory Integration' (Integration Type) select box.
  4. Choose one of the 2 options to fill in the 'Inventory ID On Google Open bidding' field:
    1. Option 1: Insert the 'dfp_ad_unit_code' or Publisher ID.
    2. Option 2: Insert the word 'Default'  if you wish to declare this Inventory as the default Inventory for all non-specific Google OB publisher connections.
      All traffic in which the publisher ID is unknown will be associated with this inventory.

      There can be only one 'Default Google OB Inventory' per account.
  5. Go to the 'Integration' tab and copy the RTB endpoint to be sent to your Google account manager to complete the connection.
    How Gamoshi is funneling traffic to the “right” inventory ID
    Gamoshi uses an order lookup to find the “right” inventory for a specific bid request from Google Authorized Buyers.
    The order does matter and the first one to match is served. Google provides a few possible matching keys:
    1. Publisher ID (appears under the site or app object)
    2. Billing IDs (appears under the impression extension)
    3. DFP AD UNIT CODE (appears under the impression extension)
    When traffic comes in, we will first look for a match to a DFP AD UNIT CODE which is the smallest granularity. Then, if no match is found, we will check for a match to the publisher ID; if no match is found then, we will look for a match to a billing ID.

    💡 It is a best practice to monitor the Default Inventory traffic for errors/mistakes that might occur as it acts as a catch-all inventory for your Google OB connections (For example, wrong definition in publisher-specific inventories).