Open Bidding Mediation Beta

This guide is intended to help you integrate Open Bidding mediation into your Android app.


Open Bidding exchanges

There are two types of open bidding integrations: those that require a third-party SDK and those that don't.

The open bidding partners listed below do not require a separate third-party SDK or adapter library. These integrations can be enabled without additional changes to your app code.

Exchanges Banner Interstitial Rewarded Video

The rest of this guide explains what's needed to enable open bidding integrations that do require an SDK.

Update your AndroidManifest.xml

Google Mobile Ads SDK versions 18.1.1 and 18.2.0 require that you explicitly enable Open Bidding in your AndroidManifest.xml file. Add the following <meta-data> tag shown below.

        <!-- Sample AdMob App ID: ca-app-pub-3940256099942544~3347511713 -->

Initialize the Mobile Ads SDK

Before an open bidding adapter can participate in an ad request, it must first be initialized. The MobileAds.initialize(Context, OnInitializationCompleteListener) method initializes open bidding adapters and calls back the completion listener once all adapters complete initialization (or after a 30 second timeout).

Call this method as early as possible, ideally in the onCreate() method of your main Activity.


public class MainActivity extends AppCompatActivity {

    protected void onCreate(Bundle savedInstanceState) {

        MobileAds.initialize(this, new OnInitializationCompleteListener() {
            public void onInitializationComplete(InitializationStatus initializationStatus) {
                Map<String, AdapterStatus> statusMap = initializationStatus.getAdapterStatusMap();
                for (String adapterClass : statusMap.keySet()) {
                    AdapterStatus status = statusMap.get(adapterClass);
                    Log.d("MyApp", String.format(
                            "Adapter name: %s, Description: %s, Latency: %d",
                            adapterClass, status.getDescription(), status.getLatency()));

                // Start loading ads here...

We recommend waiting to load ads until some point after the completion handler is called in order to ensure full participation from every ad network on the first ad request. If ads are loaded before some adapters have finished initializing, these adapters may not be ready to service ad requests and won't participate in that request.

Choose your open bidding networks

For each open bidding partner, you'll need to make changes in these places:

Third-party ad network UI
Sign up for the third-party ad network and create a placement in their UI.
AdMob UI
Update your ad unit's mediation settings to include the ad network.
App code
Update your app to include the third-party ad network's SDK, and an adapter library that communicates between Google and the third-party ad network to request and serve ads.

The ad network guides linked below walk you through each of these steps. Select an ad network below to get started.

Ad Network Banner Interstitial Rewarded Video Native Advanced


The presence of the a3p parameter in the ad request to Google indicates that at least one open bidding network is properly integrated into your app. If a3p isn't in the ad request, here are potential reasons why:

  • You did not initialize the mobile ads SDK using the new initialization method.
  • You forgot to update your AndroidManifest.xml.
  • You loaded the ad before the third-party ad network's SDK was initialized. To ensure all open bidding partners can participate, we recommend waiting to load an ad until after your OnInitializationCompleteListener gets called.
  • Your AdMob ad unit doesn't target a mediation group that has an open bidding entry configured for that third-party ad network.
  • Your AdMob ad unit belongs to a different AdMob app than the one you updated in your AndroidManifest.xml file. When initialization occurs, the Google Mobile Ads SDK only pulls down information about the ad units associated with this AdMob app ID.