This guide is intended for publishers who want to use the Google Mobile Ads SDK to load and display ads from AppLovin Ads via mediation. It covers how to add AppLovin to an ad unit's mediation configuration , how to set up Ad Network Optimization (ANO), and how to integrate the AppLovin SDK and adapter into an iOS app.
Supported ad formats and features
The AdMob mediation adapter for AppLovin has the following capabilities:
|Ad Network Optimization (ANO)|
- Xcode 7.0 or higher
- iOS Deployment target of 7.0 or higher
- Minimum required Google Mobile Ads SDK 7.14.0
Step 1: Set up AppLovin
To set up your AdMob ad unit, you'll need your AppLovin SDK Key and Report Key. To find them, go to the AppLovin Dashboard and click on the Account tab. In the dropdown list under Account, select Keys to see both values.
Select app for mediation
On the AppLovin dashboard, select Manage Apps under the Monetize section to get to your registered apps. Select the app you'd like to use with mediation from the list of available apps. If you do not see your app in the list, it is not registered. See the note below to get it registered.
On the AppLovin dashboard, select Zones under the Monetize section to get to your registered Zone IDs. If you have already created the required Zones for your app, skip ahead to Step2. To create a new Zone ID, click on Create Zone.
Enter the name of Zone ID , select iOS as the Platform, and desired Ad Type.
For Pricing, select either Flat CPM with the drop-down to select specific countries for CPM zones or Optimized by AppLovin for non CPM Zones. Then, click Save.
Once the Zone is created, the Zone ID can be found under the Zone ID column.
Step 2: Configure mediation settings for your AdMob ad unit
You need to add AppLovin to the mediation configuration for your ad unit.
First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add AppLovin as an ad source.
To create a new mediation group, select Create Mediation Group.
Enter your ad format and platform, then click Continue.
Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and then click Add Ad Units.
Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.
You should now see the ad units card populated with the ad units you selected:
Add AppLovin as an ad source
In the Ad Sources card, select Add Ad Network.
Select AppLovin and enable the Optimize switch. Enter the Report Key obtained in the previous section to set up ANO for AppLovin. Then enter an eCPM value for AppLovin and click Continue.
Enter the Bundle ID of your app along with the Zone ID and the SDK Key obtained in the previous section.
Using rewarded video ads
In the settings for your rewarded video ad unit, check the Override reward settings from third-party ad networks when using AdMob mediation so that you provide the same reward to the user no matter which ad network is served.
If you don't override the reward, the AppLovin adapter passes back the reward specified in the AppLovin dashboard when creating the placement.For more information on setting reward values for AdMob ad units, see Create an ad unit.
Step 3: Import the AppLovin SDK and adapter
Using CocoaPods (recommended)
Add the following line to your project's Podfile:
From the command line run:
pod install --repo-update
Download the latest version of the AppLovin iOS SDK and link
ApplovinSDK.frameworkin your project.
Download the latest version of the ApplovinAdapter and link
ApplovinAdapter.frameworkin your project.
Add the following frameworks to your project:
Step 4: Additional code required
No additional code required.
Step 5: Test your implementation
AppLovin recommends that test ads should be used during development if you cannot get live ads.
To enable test ads, go to the Manage Apps page by clicking on your app's name in the AppLovin dashboard and navigate to the Test Mode section. Toggle the Test Mode switch to ON.
Test Mode may take up to 30 mins to take effect. It will also automatically reset to OFF after two hours.
EU consent and GDPR
Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.
The section below shows you how to enable or disable personalized ads for AppLovin.
In SDK version
5.0.1, AppLovin added the
setIsAgeRestrictedUser methods. The following sample code shows how to pass
consent information to the AppLovin SDK. It is recommended that you call these
methods prior to requesting ads via the Google Mobile Ads SDK.
#import <AppLovinSDK/AppLovinSDK.h> // … [ALPrivacySettings setHasUserConsent:YES];
Additionally, if the user is known to be in an age-restricted category, you can
set the following flag to
See AppLovin's privacy settings for more details.
The AppLovin adapter supports
muteAudio, an optional extra to disable audio on
video ads. This parameter can be passed to the adapter using the
GADMAdapterAppLovinExtras class and must be set on every ad request.
Here's how to set it:
let request = GADRequest() let extras = GADMAdapterApplovinExtras() extras.muteAudio = false request.register(extras)
GADRequest *request = [GADRequest request]; GADMAdapterApplovinExtras * extras = [[GADMAdapterApplovinExtras alloc] init]; extras.muteAudio = NO; [request registerAdNetworkExtras:extras];
[ALSdk initializeSdk]; to your
AppDelegate provides AppLovin the
ability to track events as soon as the app starts.