Vungle

• Supported Ad Formats
• Download and Integrate
• Set Up Vungle on the MoPub Dashboard
• Network Reporting and Auto CPM
• Migrate Vungle from Custom Native Setup
• Set Up Reporting
• Test an Ad
• Additional Support

If you plan to use the MoPub SDK to load and display ads from Vungle via mediation, use this article for integration instructions and information unique to the ad network. To learn more about how MoPub mediation works, refer to our MoPub Network Mediation article.

Supported Ad Formats

Vungle currently supports the following ad formats. For support information, visit the Vungle homepage.

Download and Integrate

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

• Download the Vungle SDK for iOS

• Download the Vungle SDK for Android

  • Vungle adapters are released as an Android Archive (AAR) file starting from version 6.3.24.2. The AAR includes any required Manifest data for Vungle. As a result, you no longer need 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 level, or least at the Activity level, using android:hardwareAccelerated="true". Vungle requires this flag to be set to ‘true’ to render medium rectangle ads inside WebView.

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

Set Up Vungle on the MoPub Dashboard

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

Network Reporting and Auto CPM

The following setup is required to take advantage of Auto CPM. To enable Vungle network reporting and Auto CPM:

1. Navigate to the MoPub UI’s Networks tab. (Refer to these additional instructions that provide more detail for the remaining steps.)

2. In the Network settings page for Vungle:

   • enable reporting access

   • provide the Reporting API Key

     To find the Reporting API Key, in the Vungle Publisher dashboard, navigate to My Account and look for the Reporting API Key

     

3. Navigate to the Auto CPM preferences page and turn on 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, make sure that both the old custom native network and the new Vungle network UI are set up for backward compatibility.

Important: During migration, make sure that 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 from the the Reports Page. Contact Vungle tech support for any questions.

Test an Ad

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

With test mode enabled, you can request ads using the ad unit ID you created earlier for this purpose and receive a Vungle test ad. Be sure to disable test mode after testing!

Additional Support

For inquiries and support, email the Vungle mediation team.