AppLovin

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 home page.

  • Banner
  • Medium Rectangle
  • Interstitial
  • Rewarded Video

Download and Integration

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

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

Android Integration Help

AppLovin adapters are released as an Android Archive (AAR) file starting from version 9.2.1.1. 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

Initialize the AppLovin SDK at app launch. Doing so helps maximize fill rate for the initial ad request to AppLovin:

```
// Android
AppLovinSdk.initializeSdk(context);

// iOS
[ALSdk initializeSdk];

// Unity
// Set SDK key
AppLovin.SetSdkKey("YOUR_SDK_KEY");
// Initialize SDK
AppLovin.InitializeSdk();

```

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. Without it, the AppLovin network configuration is considered invalid. Make sure your app’s package name is added against your app.

Zone ID is optional.

Network Reporting and Auto CPM

To enable AppLovin network reporting and Auto CPM, you must enter the Report Key.

AppLovin Reporting

To find the Report Key, in the navigation panel, navigate to Account and then Keys, and look for Report key.

This setup is required to take advantage of Auto CPM.

Migrate AppLovin from Custom Native Setup

  1. Transfer Package Name and Zone ID (if applicable) from the old custom native connection to the supported AppLovin instance.

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

    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 custom event class names, have both the old custom native network and the new AppLovin network UI set up for backward compatibility.

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

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 AppLovin’s test ad article.

For details about available error codes and potential resolutions, refer to AppLovin’s documentation.

Additional Support

For inquiries and support, consult AppLovin’s support center.

Last updated March 04, 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.)