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 homepage.

  • Medium Rectangle
  • Interstitial
  • Rewarded Video

Download and Integration

To download the Vungle adapters, navigate to the Mediation Integration Tool. You will also need to download the Vungle SDK, which can be found below.

For the latest download and integration instructions, ensure that you have consulted Vungle’s tutorials before you integrate the SDK and adapters.

iOS Download
Android Download
  • Android Integration Help: Vungle adapters are released as an Android Archive (AAR) file starting from version The AAR includes the required Manifest data for Vungle if any. As a result, publishers no longer have to update their 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.

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 needed to initialize Vungle.

Migrate Vungle from Custom Native Setup

  • Transfer Application ID and Placement ID (if applicable) from the old custom native connection to the supported Vungle instance.
  • MoPub will initiate the following Vungle custom event class names to render the ads:
    • iOS
      • VungleInterstitialCustomEvent
      • VungleRewardedVideoCustomEvent
    • Android
      • com.mopub.mobileads.VungleBanner
      • com.mopub.mobileads.VungleInterstitial
      • com.mopub.mobileads.VungleRewardedVideo

Note: If you are manually entering the above-mentioned class names, migrate to the new network setup and pause the “custom native network”. If you are using your own custom event class names, you should have both the old custom native network setup & the new Vungle network UI setup for backward compatibility.

Note: During migration, please make sure the custom native network and the Vungle network are not live at the same time as this may cause revenue-impacting issues.

Set Up Reporting

You can obtain your reporting API Key using the Reports Page. Please reach out to if you have any issues.

Test Ad

While testing your SDK integrations and network setups, it is recommended that you leverage test ad placements for a consistent fill rate. To set up test mode, please reference Vungle’s test ad article for instructions.

Additional Support

For inquiries and support, please email

Last updated November 19, 2019

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.

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