Vungle

• Supported Ad Formats
• Download and Integrate
• Set Up Vungle on the MoPub Dashboard
• Advanced Bidding Initialization
• Network Reporting and Auto CPM
• Migrate Vungle from Custom Native Setup
• 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 Reference ID are required.

• To find your Application ID navigate to the applications tab and copy it from the App ID column.
• TO find your Placement Reference ID navigate to the applications tab > click under the Placements column > copy your Placement Reference ID. -Placement IDs (pids) are deprecated starting with Vungle’s latest SDK release (Android and iOS), and are no longer required to initialize Vungle.

Advanced Bidding Initialization

Vungle requires pre-initialization in order to serve Advanced Bidding ads. To initialize, follow these steps:

Initialize on Android

import com.mopub.mobileads.VungleAdapterConfiguration;

// Declare your Vungle app ID and config bundle
final Map<String, String> vungleConfigs = new HashMap<>();
snapConfigs.put("appId", "YOUR_VUNGLE_APP_ID");

final SdkConfiguration.Builder configBuilder = new SdkConfiguration.Builder("A_VALID_AD_UNIT_ID_FROM_YOUR_APP");

configBuilder.withAdditionalNetwork(VungleAdapterConfiguration.class.getName()); // only needed for MoPub 5.14.0 and earlier
configBuilder.withMediatedNetworkConfiguration(VungleAdapterConfiguration.class.getName(), vungleConfigs);

// Initialize the MoPub SDK
MoPub.initializeSdk(this, configBuilder.build(), null);

Initialize on iOS

// Declare your Vungle app ID and config bundle
NSMutableDictionary *vungleConfigs = [NSMutableDictionary new];
[snapConfigs setObject:@"YOUR_VUNGLE_APP_ID" forKey:@"appId"];

MPMoPubConfiguration *sdkConfig = [[MPMoPubConfiguration alloc] initWithAdUnitIdForAppInitialization:@"AD_UNIT_ID"];

sdkConfig.additionalNetworks = @[VungleAdapterConfiguration.class]; // only needed for MoPub 5.7.0 and earlier
sdkConfig.mediatedNetworkConfigurations = [@{@"VungleAdapterConfiguration":vungleConfigs} mutableCopy];

// Initialize the MoPub SDK
[[MoPub sharedInstance] initializeSdkWithConfiguration:sdkConfig completion:^{
}];

Initialize on Unity

Option 1. Use the MoPub Manager

Attach the Vungle Network Configuration script to your MoPub Manager Prefab, enable the script, and populate the appId information. Refer to the Network Configuration (Mediation) topic for an example.

Option 2. Initialize Manually

MoPub.InitializeSdk(new MoPub.SdkConfiguration {
  // Define the Vungle app ID you want to initialize with
  MediatedNetworks = new MoPub.MediatedNetwork[]
  {
    new MoPub.MediatedNetwork
    {
      // Specify the class name that implements the AdapterConfiguration interface.
      #if UNITY_ANDROID
        AdapterConfigurationClassName = "com.mopub.mobileads.VungleAdapterConfiguration",
      #else // UNITY_IOS
        AdapterConfigurationClassName = "VungleAdapterConfiguration",
      #endif

      NetworkConfiguration = new Dictionary<string, string> {
          { "appId", "YOUR_VUNGLE_APP_ID"},
      },
    }
  },
});

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, in the upper right hand corner 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.

Test an Ad

We recommend that you test your Vungle integration using MoPub mediation test mode to verify that the adapter works as expected. Test mode must be set up on both the MoPub side and the Vungle side.

Set Up Test Mode on the MoPub Side

Refer to our Mediation Test Mode article for complete details on using this mode.

Set Up Test Mode on the Vungle Side

The Vungle UI supports a global test mode, which you can enable for each platform, and target to specific test devices. Refer to the Vungle instructions for enabling test mode.

Enter your test device details in the Vungle UI to ensure that test ads are delivered only to your test device. Refer to the Vungle instructions for setting up test devices

Early Initialization to Test Advanced Bidding

To test Advanced Bidding, Vungle requires that you initialize the network SDK early (before the MoPub SDK even), and that you initialize it manually, without waiting for the MoPub server to trigger Vungle to initialize. To do this, you must include the Vungle-specific App ID key in your initialization code for both iOS and Android, as well as for Unity Prefabs.

If your Vungle test environment is under a different App ID key, then you must update these test keys in your initialization code for iOS, Android, and Unity Prefabs before you test, so that Vungle initializes not only for your production account details, but for your testing account details as well. (This is not a concern if you use the same App ID for your Vungle production and testing environments.)

Additional Support

For inquiries and support, email the Vungle mediation team.