Early Access - Integrating AdMob + Vungle SDK v 6.5.0 (Android)

AdMob Android adapter 6.5.0.0 is compatible with Vungle Android SDK 6.5.0. Documentation for integrating AdMob Mediation with Vungle SDK (Android) resides on AdMob's Guide section, Integrating Vungle with Mediation.

Download AdMob Android Adapter v6.5.0.0 and include Vungle Android SDK 6.5.0, then add them to your project manually. Or you can do Gradle integration.

'com.github.vungle:vungle-android-sdk:6.5.0'

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 https://developers.google.com/admob/android/mediation/vungle#step_3_import_the_vungle_sdk_and_adapter.

Use this guide as a supplement to AdMob's integration documentation as it has information about new features that are are yet to be covered by the official documentation. AdMob Android adapter 6.5.0 is compatible with Vungle Android SDK 6.5.0 and is tested for compatibility with Google SDK 18.2.0

If you are updating to Vungle Android SDK v6 using the Google Mobile Ads SDK, you must use Google Play Services Ads 12.0.0 or higher because we have added the onRewardedVideoCompleted() callback method to RewardedVideoAdListener. For more information, refer to the Google Mobile Ads SDK Release Notes.

Ad Format

Starting with v6.5.0, Vungle SDK supports AdMob’s banner ads in 3 sizes. To display a banner ad in the application, create an MREC or banner placement on Vungle dashboard and configure this to a banner ad unit on AdMob dashboard.

Supported banner sizes:

Size in dp (WxH) Description AdSize constant
320x50 Banner BANNER
728x90 IAB Leaderboard LEADERBOARD
300x250 IAB Medium Rectangle MEDIUM_RECTANGLE

AdMob allows publishers to use same ad unit ID in multiple places at the same time but Vungle SDK supports only one instance of Banner for a given AdMob ad unit ID at any given time. Please do not attempt to use same Vungle Banner placement reference ID in multiple AdMob ad unit ID since adapter is not designed to handle such case and will lead to unexpected behavior. If you wish to have multiple Vungle Banner instances simultaneously at a given time using Vungle AdMob adapter, we would advise you to create separate ad unit IDs, pointing to different Vungle placements within one Vungle app ID.

Sample code:

AdView adView = new AdView(this);
adViews.add(adView);
adView.setAdSize(AdSize.MEDIUM_RECTANGLE);
adView.setAdUnitId(<AdUnit>);

Network Specific Parameters 

The Vungle AdMob adapter continues to support network specific parameters and v6.4.11 and above will support an additional parameter setAutoRotateEnabled(bool) to play the ad as per device orientation.

Sample code:

Bundle extras = new VungleExtrasBuilder(placements)
         
.setSoundEnabled(false)
         
.setUserId("test_user")
.setAutoRotateEnabled(true)
         
.build();
AdRequest request =  new AdRequest.Builder()
         
.addNetworkExtrasBundle(VungleAdapter.class, extras)             // Rewarded video.
         
.addNetworkExtrasBundle(VungleInterstitialAdapter.class, extras) // Interstitial.
         
.build();

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
VungleNetworkSettings.setMinSpaceForInit(<INTEGER_VALUE>);

//Integer value sets the required minimum available free storage space to be able to request an ad
VungleNetworkSettings.setMinSpaceForAdLoad(<INTEGER_VALUE>);

Android ID

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

Sample code:

VungleNetworkSettings.setAndroidIdOptOut(true);

New Rewarded API

As documented in AdMob instruction guide, v17.2.0 and higher supports caching multiple rewarded ads at the same time. Since Vungle does not support this feature, the ad request for the second load attempt won't be filled by Vungle, rather it will be passed to the next ad network in the waterfall.

We recommend that you use cache optimized placement if you want to have more than one ad cached since ad request will be automatically made at the time of ad play, then next ad is highly likely to be ready to be played by the time previous ad experience ends.

Was this article helpful?

Questions?

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