This guide is intended for publishers who want to use the MoPub SDK to load and display ads from AppLovin 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 AppLovin. For the latest support, visit the AppLovin homepage.

  • Banner
  • Interstitial
  • Rewarded Video

Download and Integration

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

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

iOS Download
Android Download
  • Android Integration Help: AppLovin adapters are released as an Android Archive (AAR) file starting from version The AAR includes the required Manifest data for AppLovin. 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 AppLovin must be manually entered into the AndroidManifest.

  • AppLovin SDK Initialization

    Publishers must ensure to initialize the AppLovin SDK at app launch. Doing so helps maximize fill rate for the initial ad request to AppLovin:

      // Android
      // iOS
      [ALSdk initializeSdk];
      // Unity
      // Set SDK key
      // Initialize SDK
  • AppLovin SDK Key

    • Android

      Publishers mediating AppLovin must add their AppLovin SDK key to the app’s AndroidManifest as a child of the <application></application> tag, like so:

      <meta-data android:name="applovin.sdk.key"
                android:value="YOUR_SDK_KEY" />
    • iOS

      Go to your Project Settings. Select Info, click on one of the rows of Custom iOS Properties and click the + to add a new row. The key of the new row key should be AppLovinSdkKey and the value is shown on your AppLovin dashboard.

    • Unity

      To pass the AppLovin SDK Key from Unity, pass it as a <key, value> pair in the NetworkConfiguration Dictionary in C# when initializing MoPub. The name of the key is sdk_key and value is provided by AppLovin. Click here to reference the MoPub sample code.

Set up AppLovin on the MoPub dashboard

  • Package Name is required, while Zone ID is optional
    • Note: Without package name, AppLovin network configuration is considered invalid. Please ensure your app’s package name is added against your app.

Migrate AppLovin from Custom Native Setup

  • Transfer Package Name and Zone ID (if applicable) from the old custom native connection to the supported AppLovin instance.
  • MoPub will initiate the following AppLovin custom event class names to render the ads:
    • iOS
      • AppLovinBannerCustomEvent
      • AppLovinInterstitialCustomEvent
      • AppLovinRewardedVideoCustomEvent
    • Android
      • com.mopub.mobileads.AppLovinBanner
      • com.mopub.mobileads.AppLovinInterstitial
      • com.mopub.mobileads.AppLovinRewardedVideo

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 AppLovin network UI setup for backward compatibility.

Note: During migration, please make sure the custom native network and the AppLovin network are not live at the same time as this may cause revenue-impacting 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 AppLovin’s test ad article for instructions.

For details about available error codes as well as potential resolutions, reference AppLovin’s documentation.

Additional Support

For inquiries and support, please utilize AppLovin’s support center.

Last updated October 16, 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.)