AppLovin

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

If you plan to use the MoPub SDK to load and display ads from AppLovin 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

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

† Advanced Bidding not supported.

Download and Integrate

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

• Download AppLovin SDK for iOS

• Download AppLovin SDK for Android

  For Android, AppLovin adapters are released as an Android Archive (AAR) file starting with version 9.2.1.1. The AAR includes the required Manifest data for AppLovin. 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 AppLovin must be manually entered into the AndroidManifest.

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

Initialize the AppLovin SDK

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];
```

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, as shown:

    <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. Refer to 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. To find your Zone ID, in the AppLovin dashboard go to App Discovery > Zones > view or create your Zone ID.

Network Reporting and Auto CPM

The following setup is required to take advantage of Auto CPM. To enable AppLovin 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 AppLovin:

   • enable reporting access

   • provide the the Report Key

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

     

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

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

Test an Ad

We recommend that you test your AppLovin 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 AppLovin 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 AppLovin Side

AppLovin supports test mode, which you can enable by using AppLovin test mode SDK methods in your code. Refer to AppLovin’s instructions for setting up test mode and to AppLovin’s troubleshooting tips.

Make sure to verify parity across the device ID details you enter on the MoPub UI side and the AppLovin SDK methods.

AppLovin test mode is only available for iOS and Android native integrations. At this time, there are no test mode capabilities for Unity integrations, but an adapter will be released in the future.

Additional Support

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