Getting Started with The MediaGrid¶
This page outlines the steps needed to integrate with The MediaGrid as a supply partner.
Step 1: Ads.txt Setup¶
To commence trading with The MediaGrid, an ads.txt entry must be added to every domain that is to be monetized. Often, the same entry can be used for all of your domains. When working with multiple Publishers, segregating Invalid Traffic (IVT) data and exact payout streams may require using several unique ads.txt entries.
Send or share a complete list of domains with our Publisher Support Team: firstname.lastname@example.org. This list should be broken down by Publisher, along with any requirements for unique ads.txt entries to support segregated reporting.
We suggest using the Domain Mapping Template to list your domains
The MediaGrid generates one or more unique ads.txt entries based on your request, and sends them back to you
You then adds these entries to the ads.txt files on the corresponding domains
The MediaGrid Integration Team verifies that all ads.txt entries are correctly set up.
Step 2: Inventory Mapping¶
Ad parameters, including bid floor prices, IAB creative categories, quality rules, traffic types, and allowed creative sizes are defined at the Ad-Unit level. These parameters are passed to The MediaGrid together with the Ad Units, using the Ad Unit Mapping Template.
Ad Units that support both display and video media types are entered twice, once each in the Display and Video tabs of the Mapping Template. You can also add custom IAB category whitelists and blacklists at the Ad-Unit level, in addition to the default The MediaGrid blacklists, e.g. (IAB-25, IAB-26).
All required information must be provided for each Ad Unit to be monetized through The MediaGrid.
Send or share a completed Mapping Template to our Integration Team email@example.com. This mapping table should contain all Ad Units across all domains, or else submit a separate Mapping Templates for each domain
The MediaGrid generates unique Ad Unit IDs based on the spreadsheet, and sends them back to you
You then update your Add Slot mapping configuration with these IDs.
Step 3: Wrapper Update¶
The MediaGrid supports integration with domains using the following header bidding wrappers:
Prebid.js version 1.30.0 or newer
Prebid Server version 0.54.0 or newer
Tag integration is supported on a case-by-case basis. Additional information is available from our Publisher Support Team: firstname.lastname@example.org.
If your existing Prebid.js version is older than 1.30.0, it must be upgraded; the latest version will offer far more functionality and stability
If using an existing Prebid Server version older than 0.54.0, it must be upgraded; the latest version will offer far more available options and updates.
Action Plan for Prebid.js
You configure and download an updated Prebid.js file from Prebid.js Customize and Download. The updated Prebid.js file must include The MediaGrid Bidder Adapter, along with adapters for your other bidding partners, as configured in the original wrapper.
You update the header wrapper with the downloaded file, now with The MediaGrid header bidding adapter code.
Action Plan for Prebid Server
You must ensure that The MediaGrid bidder is added to the s2sConfig object as described in Prebid Server settings
Step 4: Ad Server Setup¶
When setting up the Ad server, we suggest creating separate orders/lines for The MediaGrid bidder to support better reporting and transparency
We recommend making sure that orders are moved to the Ready state when enabling production traffic.
Step 5: Testing and Launch¶
We strongly recommend using test volume traffic to carry out discrepancy checks
You configure a test page or launch test traffic (1% to 10% of production volume), select the test period (we recommend a minimum of two days), and share this with our Integration Team using Jira
Once the test period is complete, you send us your impression and revenue data
The MediaGrid runs a revenue and impressions discrepancy test, and confirms results that are within the acceptable range.
After a successful test, you proceeds with forwarding 100% of live traffic to The MediaGrid.
Step 6: Automated Monitoring¶
We request that you support on-going monitoring of daily revenue and impression discrepancies.
You set up daily reports and share this with The MediaGrid (preferably GAM, but Looker and other tools can also be used).
The reports should contain Impressions and CPM Revenue, associated with The MediaGrid bidder, and should be forwarded to email@example.com.
Post-Launch Monitoring and Support¶
Following a successful launch, The MediaGrid Team will continue to monitor your domains performance, and support you with inventory management, troubleshooting, and yield issues. Feel free to contact us at any time firstname.lastname@example.org