Google Open Bidding integration (Site & App)

Overview

Google Open Bidding integration connects your account to Google's unified auction, allowing you to bid on inventory from publishers using Google Ad Manager. This guide covers setting up for both the website and the mobile app inventory.

Integration Architecture

Inventory Structure Options:

Publisher-Specific Inventories: Create separate inventory entries for each Google Open Bidding publisher you work with. This provides granular control and reporting per publisher.

Default Inventory: Create one "Default" inventory per account to catch all non-publisher-specific traffic from Google Open Bidding connections. This acts as a catch-all for any traffic that doesn't match specific publisher configurations.

Single Endpoint Integration:

Important: Only one RTB endpoint needs to be shared with your Google account manager, regardless of how many Google Open Bidding publishers you connect in your dashboard.

Step-by-Step Setup

Step 1: Create New Inventory

Go to Inventory Module → List tab
Click '+' button to create new inventory

Step 2: Configure General Settings

Source: Select Site or App
Fill required fields:
- Inventory name (e.g., "Google OB - Publisher Name" or "Google OB - Default")
- Associated business partner (optional)
Integration Type: Select 'Google Open Bidding'

Step 3: Configure Google Publisher Identifier

Choose one of two options for the 'Inventory ID On Google Open Bidding' field:

Option 1: Publisher-Specific Inventory

Enter the dfp_ad_unit_code OR Publisher ID
This inventory will only receive traffic matching this specific identifier
Create multiple inventories for different publishers

Option 2: Default Inventory

Enter the word 'Default' (exactly as shown)
This inventory receives all traffic where the publisher ID is unknown
Limitation: Only one Default inventory is allowed per account
Acts as a catch-all for non-matched traffic

Click 'Create'

Step 4: Get RTB Endpoint

Navigate to the Integration tab
Copy RTB endpoint URL
Send the endpoint to your Google account manager to complete the integration

Quick Access: Click integration type in the 'Type' column from the Inventory List for instant endpoint pop-up.

How Traffic Matching Works

Traffic Routing Priority

Gamoshi uses hierarchical matching to route incoming Google Authorized Buyers requests to the correct inventory:

Matching Order (First Match Wins):

DFP AD UNIT CODE (highest priority - most granular)
- Found in impression extension
- Matches specific ad unit placements
Publisher ID (medium priority)
- Found in the site or app object
- Matches the entire publisher
Billing ID (lower priority)
- Found in impression extension
- Matches billing entity
Default Inventory (fallback)
- Catches all unmatched traffic
- Used when no specific match is found

Troubleshooting

No Traffic Received:

Check:

RTB endpoint shared with the Google account manager
Google has completed integration on their end
Campaigns are targeting Google OB inventory
Bid floors aren't set too high

Traffic Going to Wrong Inventory:

Review:

Publisher identifier format (dfp_ad_unit_code vs. Publisher ID)
Spelling and formatting of identifiers
Check Analytics to see which inventory is receiving traffic
Verify matching logic priority

All Traffic in Default Inventory:

Possible causes:

Publisher-specific identifiers not configured correctly
Google is not sending the expected identifier fields
Identifier format mismatch
Publisher-specific inventories have not been created yet

Default Inventory Not Working:

Verify:

Exactly one Default inventory exists per account
Field contains exactly the word "Default" (case-sensitive)
No typos or extra spaces in the identifier field

Integration Checklist

Before going live:

✅ Created publisher-specific inventories (if needed)
✅ Created Default inventory (catch-all)
✅ Copied RTB endpoint from Integration tab
✅ Sent endpoint to Google account manager
✅ Created campaigns targeting Google OB inventories
✅ Monitoring plan for Default inventory established