Vungle

This guide is intended for publishers who want to use the MoPub SDK to load and display ads from Vungle via mediation. Below, you will find information about the ad network, integration/setup instructions, and more. For more information about how MoPub mediation works, visit this guide.

Supported Ad Formats

The following ad formats are currently supported by Vungle. For the latest support, visit the Vungle home page.

  • Banner
  • Medium Rectangle
  • Interstitial
  • Rewarded Video

Download and Integration

To download the Vungle adapters, navigate to the Mediation Integration Tool. You must also download the Vungle SDK:

For the latest download and integration instructions, consult Vungle’s tutorials before you integrate the SDK and adapters.

Android Integration Help

Vungle adapters are released as an Android Archive (AAR) file starting from version 6.3.24.2. The AAR includes the required Manifest data for Vungle if any. As a result, you no longer have to update your AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by Vungle must be manually entered into the AndroidManifest.

If you are building your apps from Unity, make sure to export the Android project and enable Hardware Acceleration at the Application or least the Activity level using android:hardwareAccelerated="true". In order to be able to render medium rectangle ads inside WebView, Vungle needs this flag to be true.

Set Up Vungle on the MoPub Dashboard

  • Application ID and Placement ID are required.
  • Placement IDs (pids) has been deprecated per Vungle’s latest SDK release (Android and iOS), and is no longer required to initialize Vungle.

Network Reporting and Auto CPM

To enable Vungle network reporting and Auto CPM, you must enter the Reporting API Key.

Vungle reporting 1

To find the Reporting API Key, navigate to My Account and look for the Reporting API Key.

This setup is required to take advantage of Auto CPM.

Migrate Vungle from Custom Native Setup

  1. Transfer Application ID and Placement ID (if applicable) from the old custom native connection to the supported Vungle instance.

  2. MoPub will initiate the following Vungle mediation adapter class names to render the ads:

    • iOS

      • VungleInterstitialCustomEvent
      • VungleRewardedVideoCustomEvent
    • Android

      • com.mopub.mobileads.VungleBanner
      • com.mopub.mobileads.VungleInterstitial
      • com.mopub.mobileads.VungleRewardedVideo

    If you are manually entering these class names, migrate to the new network setup and pause the “Custom Native Network.” If you are using your own mediation adapter class names, have both the old custom native network and the new Vungle network UI set up for backward compatibility.

Important: During migration, make sure the custom native network and the Vungle network are not both live at the same time, because this may impact your revenue.

Set Up Reporting

You can obtain your Reporting API Key using the Reports Page. Contact Vungle tech support for any questions.

Test Ad

While testing your SDK integrations and network setups, we recommend that you leverage test ad placements for a consistent fill rate. To set up test mode, follow the instructions in Vungle’s test ad article.

Additional Support

For inquiries and support, email the Vungle mediation team.

Last updated June 09, 2020

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.

© 2020 MoPub (a division of Twitter, Inc.)