Understand Advanced Bidding
- Advanced Bidding Integration Components
- Advanced Bidding Request and Response Flow
- Sample Validation Reports
Advanced Bidding is the complete re-imagination of header bidding for the mobile app environment. It’s designed to level the playing field while increasing inventory access and auction efficiency for all ad sources by replacing the traditional ad waterfall with simultaneous real-time bidding (RTB) from ad networks and DSPs. Advanced Bidding is only availale to publishers participating in MoPub’s [Network Mediation Program[(/publishers/mediation/mopub-network-mediation/).
If you are interested in participating with MoPub as an Advanced Bidding Network:
- Visit the Advanced Bidding page on the MoPub website. Its overview video is a good place to start understanding the concepts.
- Understand the Advanced Bidding integration components.
- Understand the Advanced Bidding request and response flow.
- Reach out to our mediation team if you are interested in becoming an Advanced Bidder. In your email, include any relevant information, such as your top geos, formats, and your timeline to start bidding.
Advanced Bidding Integration Components
The Advanced Bidding integration consists of 3 required components:
|Network Bidder||Network||MoPub Advanced Bidding Spec
||The MoPub team recommends reviewing the sample bid requests & responses first, and leveraging the complete spec for any questions on specific fields.|
|SDK Adapter||MoPub||The MoPub team will direct you to sample code||The MoPub Solutions Engineering team will work with you to make the necessary updates to the adapters to support Advanced Bidding. The network will resume maintenance of each version from that point forward.|
|Validation Reporting||Network||Sample daily report
Sample monthly report
|MoPub requires all Advanced Bidders to provide daily and monthly reports, which are used for troubleshooting and billing validation purposes.|
Advanced Bidding Request and Response Flow
The Advanced Bidding Overview diagram shows the big picture with all the participants.
Figure 1. Advanced Bidding Overview
- The publisher app requests an ad from the MoPub SDK.
- The MoPub SDK requests bid tokens from the network SDKs via the network adapters.
- Network SDKs submit tokens back to the MoPub SDK.
- The MoPub SDK requests an ad from the MoPub ad server.
- The MoPub ad server requests bids from the MoPub Exchange.
- The MoPub Exchange requests bids from two types of third parties, passing the relevant tokens:
- Advanced Bidding networks (passing the relevant tokens)
- Advanced Bidding networks and other demand sources respond with bids.
- The MoPub Exchange collects all received bids and returns them to the MoPub ad server.
- The MoPub ad server resolves the auction between eligible bidders and non-bidding demand sources (according to the publisher’s waterfall).
- The MoPub ad server responds to the MoPub SDK with the winning ad source.
- The publisher app displays the ad. Depending on the winning demand source, the MoPub SDK either
- Displays the creative, or
- Passes control to the network SDK for playback
Client-Side Ad Request
Advanced Bidding is triggered when the publisher makes an ad request to the MoPub SDK. Typically, network SDKs have already been initialized at this point.
Figure 2. Publisher Makes an Ad Request to the MoPub SDK
The MoPub SDK then asks all Advanced Bidding network SDKs for a token. Providing a token is optional. If provided, the token is included in the bid request to the network’s bidder, so that the network can use it to communicate between the SDK and the bidder.
Figure 3. The MoPub SDK Asks Advanced Bidding Network SDKs for a Token
The token should be encoded or encrypted so that it is not readable by MoPub.
Finally, the MoPub SDK makes an ad request to the MoPub server, and includes any tokens it has collected.
Figure 4. The MoPub SDK Makes an Ad Request to the MoPub Server, Including Tokens
Server-Side Bid Request
The MoPub Exchange makes a bid request to all eligible network bidders, in accordance with the MoPub Advanced Bidding Specification.
Figure 5. The MoPub Exchange Makes a Bid Request to Eligible Network Bidders and DSPs
Refer to these sample bid requests.
Server-Side Bid Response
Figure 6. Bidders Respond with a Bid
In OpenRTB, the
adm field is typically used for passing the ad markup (creative content), but has increased flexibility for Advanced Bidding. MoPub uses the
adm field to pass content from the winning bidder back down to the winning network’s SDK. This content can be any data that the winning network bidder wishes to relay to the network’s SDK. The content is often metadata referencing the creative to fetch, but use of this field is not required at all.
Refer to these sample bid responses.
Client-Side Ad Response and Ad Rendering
The MoPub SDK instructs the winning ad source to load an ad. If this winning ad source was an Advanced Bidding network, then the contents of the
adm field are passed to the network SDK through the adapters.
Figure 7. The MoPub SDK Instructs the Winning Ad Source to Load an Ad
Depending on the ad format, the publisher app may now instruct the MoPub SDK to show an ad. The step only applies to interstitial and rewarded ad formats. MoPub’s banner and native ads currently have no ‘show’ method, and for them, the rendering of the ad should immediately follow a successful ad load without the intermediate ‘show’ step.
Figure 8. The Publisher App Instructs the MoPub SDK to Show Ad
This step has no requirements specific to Advanced Bidding. It is identical to any standard mediation interface between MoPub and a supported network.
Lastly, and again depending on the ad format, MoPub may instruct the winning demand source to show the ad. This step, too, applies only to interstitial and rewarded ad formats because MoPub’s banner and native ads currently have no ‘show’ method. Here again, there are no requirements specific to Advanced Bidding.
Figure 9. The MoPub SDK Instructs the Winning Demand Source to Show Ad
Advanced Bidding Test Mode
MoPub’s Mediation Test Mode makes it easy for publishers to quickly test their Advanced Bidding integrations. To indicate that Mediation Test Mode is being used, MoPub will pass “test”:1 in the bid request for any given test impressions, as noted in the Advanced Bidding 2.5 Spec. MoPub requires Advanced Bidders to return a test bid price of $99.00 and a test bid creative whenever the “test”:1 flag is present in the bid request.
Sample Validation Reports
Sample Daily Validation Report
|2019-03-01||818754181479601||Pub name text||Uncrossed||iOS||Interstitial||284673||207249||41043||36017||3.02233||376.7435077|
|2019-03-01||181360805703034||Pub name text||胴上げ祭り||iOS||Interstitial||35502||13360||587||73467||42.42857||7.792958566|
|2019-03-01||818754181479601||Pub name text||Test App||iOS||Banner||2580278||1828115||211704||34563456||3.02233||64.88535385|
|2019-03-01||1630733693809559||Pub name text||FocusedMan||Android||Interstitial||248579||189135||35783||345||42.42857||71.26034276|
|2019-03-01||10152593451449604||Pub name text||MLB Tap Sports Baseball 2019||iOS||Rewarded Ad||104451||78749||17311||8678||4.98709||119.3469861|
|2019-03-01||818754181479601||Pub name text||Uncrossed||Android||Rewarded Ad||83905||67491||40727||45322||4.62086||310.035646|
|2019-03-01||10152593451449604||Pub name text||CookOff||Android||Native||0||0||0||225546||2.94031||71.26034276|
|2019-03-01||818754181479601||Pub name text||Uncrossed||Android||Native||0||0||0||6345||3.02233||0|
Sample Monthly Validation Report
|862258100463574||Pub name text||4 Pics 1 Word||iOS||Interstitial||4139178||3122202||36017||71751||3.02233||173.63375|
|818754181479601||Pub name text||Wordscapes Uncrossed||Android||Native||4139178||3122202||73467||0||42.42857||34.12000|
|10152129083228034||Pub name text||FreeCell||Banner||4139178||3122202||52837||166||3.02233||0.00005|
|10152593451449604||Pub name text||Design Home||Android||Native||4139178||3122202||35720||0||42.42857||0.00079|
|899156253477457||Pub name text||AN Video - Metro UK||iOS||Native||4139178||3122202||77037||4.98709|
|1150448308370833||Pub name text||Golf Orbit||Android||Native||4139178||3122202||52787||0||4.62086||0.00138|
|1150448308370833||Pub name text||Terrarium||Rewarded Ad||4139178||3122202||44780||12||2.94031||0.00000|
|1178573945502671||Pub name text||PicsArt Photo Studio||iOS||Native||4139178||3122202||77037||3.02233|
|1150448308370833||Pub name text||Emoji Craft !||Android||Rewarded Ad||4139178||3122202||77037||0||42.42857||0.00000|
How can we make this article better for you?
Last updated September 30, 2021
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2021 MoPub (a division of Twitter, Inc.)