Enable AdMob Mediation on Android

AdMob Android adapter is compatible with Vungle Android SDK 6.12.1 and has been tested for compatibility with Google Android SDK 21.3.0. AdMob adapter supports rewarded interstitial ad (bidding and waterfall). Please contact your Liftoff account manager to enable this functionality.

Documentation for integrating AdMob Mediation with Vungle SDK resides on AdMob's Guide section, Integrating Vungle with Mediation, so use this guide as a supplement for the information about new features that are yet to be covered by the official documentation.

Download AdMob Android Adapter v6.12.1.0 and include Vungle Android SDK 6.12.1. You can add them to your project manually or do Gradle integration through Bintray.

implementation 'com.vungle:publisher-sdk-android:6.12.1'

The instructions for Android Studio integration and manual integration can be found on AdMob's integration guide, Step 3: Import the Vungle SDK and Adapter, at here.


Starting with Vungle SDK v6.10.3, Vungle provides an optional method for you to indicate to the Vungle SDK at the device level whether the user within the given mobile app is under or over the age of 13. The Vungle SDK COPPA configuration respects AdMob's "tag for child-directed treatment."

To learn more about Vungle's tools to assist publishers in complying with COPPA, as well as when to use the SDK COPPA API as opposed to the Dashboard COPPA settings, refer to our COPPA Implementation details.


The COPPA status must be set before calling initializing the AdMob SDK, as shown:

RequestConfiguration configuration = MobileAds.getRequestConfiguration()


As of July 1, 2020, California Consumer Privacy Act (CCPA) will be enforced and publishers must update to Android SDK 6.7.0 and AdMob adapter to comply with CCPA.

To pass CCPA values, you must call the Vungle SDK API directly. This  is the only feature that should be accessed directly through Vungle SDK API. Other optional features such as Android ID and memory settings should use VungleNetworkSettings.

Use Vungle.updateCCPAStatus to set the user’s consent status to specify that the user has opted out by passing Vungle.CCPAStatus.OPTED_OUT. And use Vungle.getCCPAStatus to get the current CCPA status for the particular user.

updateCCPAStatus getCCPAStatus
public static void updateCCPAStatus(@NonNull final Vungle.CCPAStatus status)
Sample Code
// To set the user's CCPA status to opted out:
// To find out what the user's current consent status is:
Vungle.CCPAStatus currentCCPAStatus = Vungle.getCCPAStatus();

Banner Ads

Starting with v6.5.1, Vungle SDK supports AdMob’s banner adsTo display a banner ad in the application, create an MREC or banner placement on Monetize dashboard and configure this to a banner ad unit on AdMob dashboard. Please note that MREC (300dp x 250dp) must have a separate placement reference ID configured as MREC from Monetize dashboard, compared to other banner sizes that is configured as banner.

Supported banner sizes:

Size in dp (WxH) Description AdSize constant
320x50 Banner BANNER
728x90 IAB Leaderboard LEADERBOARD
300x250 IAB Medium Rectangle MEDIUM_RECTANGLE
Provided width x Adaptive height Adaptive banner N/A
Screen width x 32|50|90 Smart banner SMART_BANNER

Sample code:

AdView adView = new AdView(this);


Multiple Banner Load

Vungle Android SDK 6.5.x supports one banner ad to be loaded for a placement ID at any given time and one placement ID is mapped to one AdMob ad unit ID. This limits the ability to successfully load subsequent loadAd requests when a banner ad is already loaded by Vungle SDK. To overcome this limitation, you must pass a unique identifier (which can be a random number generated or simple incremental number) for each banner loadAd so the request can fall back to next ad network in the waterfall when Vungle SDK already has a banner ad loaded.

Sample code:

Bundle extras = new VungleExtrasBuilder(null).setBannerUniqueRequestID("12345").build();
AdRequest adRequest = new AdRequest.Builder().addNetworkExtrasBundle(VungleInterstitialAdapter.class, extras).build();

Rewarded Interstitial Ads

As of AdMob Adapter, we support rewarded interstitial ads. This includes publisher and advertiser settings and controls, and reporting. Contact your Liftoff account manager to enable this feature. Rewarded interstitial ads behave as follows:

A user playing a game has just completed a level. While the next level loads, the user is prompted that an ad will begin in a few seconds and the reward for watching the ad is an extra heart. The user has the option to close the ad.

After a few seconds, the ad begins with a countdown informing the user how of the time left until they receive the reward. If the user clicks to exit the ad, a prompt appears, warning them about the loss of the reward. The user must confirm that they want to exit the ad before the ad closes.

Our support for rewarded interstitial ads includes:

  • Skip ad option
  • Ad autostart (for example, after 5 seconds)
  • A close ad screen similar to what is displayed when a user tries to close a rewarded ad
  • An endcard when the video completes

If you opt to create an introduction screen that displays when an ad is about to play, refer to the Google AdMob documentation for rewarded interstitials.

Network-Specific Parameters

The Vungle AdMob adapter continues to support network specific parameters as shown on AdMob's guide. Starting with v6.5.1, audio setting for video play has been replaced by setStartMuted that takes a boolean and setSoundEnabled has been deprecated. The adapter also supports an additional parameter setAdOrientation to play the ad as per device orientation that takes an AdConfig object with LANDSCAPE, PORTRAIT, AUTO_ROTATE and MATCH_VIDEO configurability. (setAutoRotate has been deprecated)

Sample code:

Bundle localExtras = new VungleExtrasBuilder(null)

For rewarded ads, you will pass VungleAdapter.class on addNetworkExtrasBundle while you will pass VungleInterstitial.class for interstitial ads.

Sample code for loading rewarded ads:

AdRequest adRequest = new AdRequest.Builder()
        .addNetworkExtrasBundle(VungleAdapter.class, localExtras)

RewardedAd.load(this, "AD_UNIT_ID", adRequest, new RewardedAdLoadCallback(){
    public void onAdFailedToLoad(@NonNull LoadAdError loadAdError) { }

    public void onAdLoaded(@NonNull RewardedAd rewardedAd) { }

Sample code for loading interstitial ads:

AdRequest adRequest = new AdRequest.Builder()
        .addNetworkExtrasBundle(VungleInterstitialAdapter.class, localExtras)
InterstitialAd.load(this, "AD_UNIT_ID", adRequest, new InterstitialAdLoadCallback() {
    public void onAdLoaded(@NonNull InterstitialAd interstitialAd) { }
    public void onAdFailedToLoad(@NonNull LoadAdError loadAdError) { }

Memory Settings

Starting with v6.4.11, you can prevent the SDK from requesting ads or even initializing if the storage of your Android phone falls below a predefined threshold. If this happens, you will get an error similar to the following:

There is not enough file system size on the device. 

Sample code:

import com.vungle.mediation.VungleNetworkSettings;

//Integer value sets the required minimum available free storage space to be able to initialize the SDK

//Integer value sets the required minimum available free storage space to be able to request an ad

Android ID

Starting with Vungle Android SDK v6.4.11, publishers can now restrict passing Android ID from the device to the SDK.

Sample code:




Need further assistance, feel free to reach out to us, we’re here to help!

Was this article helpful?