Integrate Liftoff Monetize with Mediation

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Liftoff Monetize using mediation, covering both bidding and waterfall integrations. It covers how to add Liftoff Monetize to an ad unit's mediation configuration, and how to integrate the Vungle SDK and adapter into an iOS app.

Supported integrations and ad formats

The AdMob mediation adapter for Liftoff Monetize has the following capabilities:

² For access to this feature, contact your Liftoff Monetize account manager.

Requirements

• iOS deployment target of 11.0 or higher

• [For bidding]: Vungle adapter 6.11.0.1 or higher (latest version recommended)

• Latest Google Mobile Ads SDK

Limitations

• Liftoff Monetize does not support loading multiple ads using the same Placement Reference ID.
  • The Vungle adapter gracefully fails the 2nd request if another request for that placement is loading or waiting to be shown.
• Liftoff Monetize only supports loading 1 banner ad at a time.
  • The Vungle adapter gracefully fails subsequent banner requests if a banner ad is already loaded.

Step 1: Set up Liftoff Monetize

Sign up or log in to your Liftoff Monetize account.

Add your app to the Liftoff Monetize dashboard by clicking the Add Application button.

Fill out the form, entering all the necessary details.

Once your app is created, select your app from the Liftoff Monetize Applications dashboard.

Take note of the App ID.

Add new placements

To create a new placement to be used with AdMob mediation, navigate to the Liftoff Monetize Placements dashboard, click on the Add Placement button and select your app from the drop-down list.

Details for adding new placements are included below:

Specify how to monetize your inventory

Take note of the Reference ID and click Sounds Good.

Locate your Reporting API Key

Step 2: Configure mediation settings for your AdMob ad unit

You need to add Liftoff Monetize 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 Liftoff Monetize 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. 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, as shown below:

Add Liftoff Monetize as an ad source

In the Ad Sources card, select Add Ad Network. Select Liftoff Monetize and enable the Optimize switch. For Reporting API Key, enter the Reporting API Key obtained in the previous section to set up ad source optimization for Liftoff Monetize. Then enter an eCPM value for Liftoff Monetize and click Continue.

If you already have a mapping for Liftoff Monetize, you can simply select it. Otherwise, click Add mapping.

Next, enter a Mapping name, the Application ID and Placement Reference ID obtained in the previous section. Then click Done.

Rewarded ads

In the settings for your rewarded ad unit, provide values for the reward amount and reward type. Then, to ensure you provide the same reward to the user no matter which ad network is served, check the Apply to all networks in Mediation groups box.

If you don't apply this setting, the Vungle adapter defaults to a reward of type vungle with a value of 1. The Vungle SDK does not provide specific reward values for its rewarded ads.

Step 3: Import the Vungle SDK and adapter

Using CocoaPods (recommended)

• Add the following line to your project's Podfile:

  pod 'GoogleMobileAdsMediationVungle'
  

• From the command line run:

  pod install --repo-update
  

Manual integration

• Download the latest version of the Vungle SDK and link VungleSDK.framework in your project.

• Download the latest version of the Vungle adapter from the download link in the Changelog and link VungleAdapter.framework in your project.

• Add the following Frameworks to your project:

  • AdSupport
  • AudioToolbox
  • AVFoundation
  • CFNetwork
  • CoreGraphics
  • CoreMedia
  • libz.tbd
  • MediaPlayer
  • QuartzCore
  • StoreKit
  • SystemConfiguration

Step 4: Add required code

Liftoff Monetize requires a list of all the placements that will be used within your app to be passed to their SDK for initialization. You can provide the list of placements to the adapter using the VungleAdNetworkExtras class's allPlacements property. The following code example shows how to use this class.

import VungleAdapter
// ...

let request = GADRequest()
let extras = VungleAdNetworkExtras()

let placements = ["PLACEMENT_ID_1", "PLACEMENT_ID_2"]
extras.allPlacements = placements
request.register(extras)

#import <VungleAdapter/VungleAdapter.h>
// ...

GADRequest *request = [GADRequest request];
VungleAdNetworkExtras *extras = [[VungleAdNetworkExtras alloc] init];

NSMutableArray *placements = [[NSMutableArray alloc] initWithObjects:@"PLACEMENT_ID_1", @"PLACEMENT_ID_2", nil];
extras.allPlacements = placements;
[request registerAdNetworkExtras:extras];

Step 5: Test your implementation

To enable test ads, go to your Liftoff Monetize dashboard and navigate to Applications.

Select your app for which you would like to enable test ads under the Placement Reference ID section of your app. Test ads can be enabled by selecting Test Mode to Show test ads only under the Status section.

That's it! You now have a working mediation integration with Liftoff Monetize.

Optional steps

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.

In SDK version 6.3.2, Liftoff Monetize added an API that lets you pass consent to the Vungle SDK. The following sample code shows how to pass this consent information to the Vungle SDK. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

import VungleSDK
// ...

VungleSDK.shared().update(VungleConsentStatus.accepted, consentMessageVersion: "1.0.0")

#import <VungleSDK/VungleSDK.h>
// ...

[[VungleSDK sharedSDK] updateConsentStatus:VungleConsentAccepted consentMessageVersion:@"1.0.0"];

See GDPR recommended implementation instructions for more details and the values that can be provided in the method.

Add Liftoff to GDPR ad partners list

Follow the steps in GDPR settings to add Liftoff to the GDPR ad partners list in the AdMob UI.

CCPA

The California Consumer Privacy Act (CCPA) requires giving California state residents the right to opt out of the "sale" of their "personal information" (as the law defines those terms), with the opt-out offered via a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The CCPA preparation guide offers the ability to enable restricted data processing for Google ad serving, but Google is unable to apply this setting to each ad network in your mediation chain. Therefore, you must identify each ad network in your mediation chain that may participate in the sale of personal information and follow guidance from each of those networks to ensure compliance with CCPA.

In SDK version 6.7.0, Liftoff Monetize added an API that lets you pass consent to the Vungle SDK. The following sample code shows how to pass this consent information to the Vungle SDK. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

import VungleSDK
// ...

VungleSDK.shared().update(VungleCCPAStatus.accepted)

#import <VungleSDK/VungleSDK.h>
// ...

[[VungleSDK sharedSDK] updateCCPAStatus:VungleCCPAAccepted];

See CCPA recommended implementation instructions for more details and the values that can be provided in the method.

Add Liftoff to CCPA ad partners list

Follow the steps in CCPA settings to add Liftoff to the CCPA ad partners list in the AdMob UI.

Network-specific parameters

The Vungle adapter supports an additional request parameter which can be passed to the adapter using the VungleAdNetworkExtras class. This class includes the following properties:

muted

Sets whether or not to enable sound when playing video ads.

userId

A string representing Liftoff Monetize's Incentivized User ID.

ordinal

An Integer indicating the order in which this ad was shown in the game session.

flexViewAutoDismissSeconds

An Integer to make Flex view ads dismiss automatically after the specified number of seconds.

playingPlacement

A String representing Liftoff Monetize's placement ID.

allPlacements

An Array consisting of all the Placement ID's in the app (not required for apps implementing Vungle SDK 6.2.0 or higher).

Here's a code example of how to create an ad request that sets these parameters:

#import "VungleAdapter.h"
// ...

let request = GADRequest()
let extras = VungleAdNetworkExtras()
extras.muted = true
extras.userId = "test-user"
// ...
request.register(extras)

#import <VungleAdapter/VungleAdapter.h>
// ...

GADRequest *request = [GADRequest request];
VungleAdNetworkExtras *extras = [[VungleAdNetworkExtras alloc] init];
extras.muted = YES;
extras.userId = @"test_user";
// ...
[request registerAdNetworkExtras:extras];

Native ads rendering

The Vungle adapter returns its native ads as GADNativeAd objects. It populates the following native ads field descriptions for a GADNativeAd.

¹ The Liftoff Monetize adapter does not provide direct access to the main image asset for its native ads. Instead, the adapter populates the GADMediaView with a video or an image.

Error codes

If the adapter fails to receive an ad from Liftoff Monetize, publishers can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following classes:

Here are the codes and accompanying messages thrown by the Liftoff Monetize adapter when an ad fails to load:

Liftoff Monetize iOS Mediation Adapter Changelog

Version 7.0.0.0

• Rebranded adapter name from Vungle to Liftoff Monetize.
• Verified compatibility with Vungle SDK 7.0.0.
• Removed support of the armv7 architecture.
• Added support for the arm64 simulator architecture.
• Now requires minimum iOS version 11.0.
• Now requires Google Mobile Ads SDK version 10.4.0 or higher.

Built and tested with:

• Google Mobile Ads SDK version 10.4.0.
• Vungle SDK version 7.0.0.

Version 6.12.3.0

• Verified compatibility with Vungle SDK 6.12.3.

Built and tested with:

• Google Mobile Ads SDK version 10.2.0.
• Vungle SDK version 6.12.3.

Version 6.12.2.0

• Verified compatibility with Vungle SDK 6.12.2.

Built and tested with:

• Google Mobile Ads SDK version 10.0.0.
• Vungle SDK version 6.12.2.

Version 6.12.1.2

• Now requires Google Mobile Ads SDK version 10.0.0 or higher.

Built and tested with:

• Google Mobile Ads SDK version 10.0.0.
• Vungle SDK version 6.12.1.

Version 6.12.1.1

• Verified compatibility with Vungle SDK 6.12.1.
• Added bidding support for banner ad format.

Built and tested with:

• Google Mobile Ads SDK version 9.14.0.
• Vungle SDK version 6.12.1.

Version 6.12.1.0

• Verified compatibility with Vungle SDK 6.12.1.

Built and tested with:

• Google Mobile Ads SDK version 9.13.0.
• Vungle SDK version 6.12.1.

Version 6.12.0.0

• Verified compatibility with Vungle SDK 6.12.0.
• Added waterfall mediation and bidding support for rewarded interstitial ad format.
• Added bidding support for native ad format.
• Updated the adapter to use the didRewardUser API.
• Removed the ordinal extra in VungleAdNetworkExtras.
• Now requires Google Mobile Ads SDK version 9.8.0 or higher.

Built and tested with:

• Google Mobile Ads SDK version 9.9.0.
• Vungle SDK version 6.12.0.

Version 6.11.0.2

• Added waterfall mediation support for native ad format.

Built and tested with:

• Google Mobile Ads SDK version 9.8.0.
• Vungle SDK version 6.11.0.

Version 6.11.0.1

• Added support for loading multiple ads for the same placement ID in bidding interstitial and rewarded ads.

Built and tested with:

• Google Mobile Ads SDK version 9.6.0.
• Vungle SDK version 6.11.0

Version 6.11.0.0

• Verified compatibility with Vungle SDK 6.11.0.

Built and tested with:

• Google Mobile Ads SDK version 9.4.0.
• Vungle SDK version 6.11.0

Version 6.10.6.1

• Fixed an issue where the ad delegate was removed if the next ad failed to download. This applies to auto-cached setting placements only.
• Removed willPresentFullScreenView and adapterWillPresentFullScreenModal callbacks in banner ads.

Built and tested with:

• Google Mobile Ads SDK version 9.0.0.
• Vungle SDK version 6.10.6

Version 6.10.6.0

• Verified compatibility with Vungle SDK 6.10.6.
• Verified compatibility with Google Mobile Ads SDK version 9.0.0.
• Now requires Google Mobile Ads SDK version 9.0.0 or higher.

Built and tested with:

• Google Mobile Ads SDK version 9.0.0.
• Vungle SDK version 6.10.6

Version 6.10.5.1

• Added bidding support for interstitial and rewarded ad formats.

Built and tested with

• Google Mobile Ads SDK version 8.13.0.
• Vungle SDK version 6.10.5

Version 6.10.5.0

• Verified compatibility with Vungle SDK 6.10.5.

Built and tested with

• Google Mobile Ads SDK version 8.13.0.
• Vungle SDK version 6.10.5

Version 6.10.4.0

• Verified compatibility with Vungle SDK 6.10.4.
• Updated the adapter to respect the mute setting in Vungle's publisher dashboard when the muteIsSet boolean in VungleAdNetworkExtras is not explicitly set.

Built and tested with

• Google Mobile Ads SDK version 8.12.0.
• Vungle SDK version 6.10.4

Version 6.10.3.1

• Fixed a bug where interstitial callbacks were not invoked after the first playback.
• Updated the options dictionary that is passed into playAd method to include the muted property set by the publisher in the extras object.

Built and tested with

• Google Mobile Ads SDK version 8.12.0.
• Vungle SDK version 6.10.3

Version 6.10.3.0

• Verified compatibility with Vungle SDK 6.10.3.
• Now requires minimum iOS version of 10.0.

Built and tested with

• Google Mobile Ads SDK version 8.11.0.
• Vungle SDK version 6.10.3.

Version 6.10.1.0

• Verified compatibility with Vungle SDK 6.10.1.
• Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher.
• Now requires building against Xcode 12.5 or higher.

Built and tested with

• Google Mobile Ads SDK version 8.9.0.
• Vungle SDK version 6.10.1.

Version 6.10.0.0 (rolled back)

• Verified compatibility with Vungle SDK 6.10.0.
• Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher.
• Now requires building against Xcode 12.5 or higher.

Built and tested with

• Google Mobile Ads SDK version 8.4.0.
• Vungle SDK version 6.10.0.

Version 6.9.2.0

• Verified compatibility with Vungle SDK 6.9.2.
• Now requires Google Mobile Ads SDK version 8.3.0 or higher.

Built and tested with

• Google Mobile Ads SDK version 8.3.0.
• Vungle SDK version 6.9.2.

Version 6.9.1.0

• Verified compatibility with Vungle SDK 6.9.1.
• Now requires Google Mobile Ads SDK version 8.1.0 or higher.
• Added standardized adapter error codes and messages.
• Updated the adapter to use the .xcframework format.
• Remove VungleSDKResetPlacementForDifferentAdSize error check for loading Ads.
• Introduce the new SDK delegate callback vungleAdViewedForPlacement: to track impression.

Built and tested with

• Google Mobile Ads SDK version 8.1.0.
• Vungle SDK version 6.9.1.

Version 6.8.1.0

• Verified compatibility with Vungle SDK 6.8.1.
• Now requires Google Mobile Ads SDK version 7.66.0 or higher.

Built and tested with

• Google Mobile Ads SDK version 7.66.0.
• Vungle SDK version 6.8.1.

Version 6.8.0.0

• Verified compatibility with Vungle SDK 6.8.0.
• Now requires Google Mobile Ads SDK version 7.65.0 or higher.

Built and tested with

• Google Mobile Ads SDK version 7.65.0.
• Vungle SDK version 6.8.0.

Version 6.7.1.0

• Verified compatibility with Vungle SDK 6.7.1.
• Now requires Google Mobile Ads SDK version 7.64.0 or higher.
• Fixed an issue where didFailToPresentWithError: was not called when a rewarded ad failed to present.

Built and tested with

• Google Mobile Ads SDK version 7.64.0.
• Vungle SDK version 6.7.1.

Version 6.7.0.0

• Verified compatibility with Vungle SDK 6.7.0.
• Now requires Google Mobile Ads SDK version 7.62.0 or higher.
• Added support for playing multiple banner ads at the same time.
• Clicks now reported when the click happens instead of when the ad is closed.
• Banner and interstitial ads now forward the willLeaveApplication callback.

Built and tested with

• Google Mobile Ads SDK version 7.62.0.
• Vungle SDK version 6.7.0.

Version 6.5.3.0

• Verified compatibility with Vungle SDK 6.5.3.
• Now requires Google Mobile Ads SDK version 7.58.0 or higher.
• Added support for Smart and Adaptive Banner ads.
• Added support for Banner (320x50, 300x50, 728x90) ads.
• Added video orientation option when play ads.
• Fix a bug where failed to call report_ad after the first refresh.
• Fix ad availability delays issue with longer waterfall.
• Remove support for i386 architecture.

Built and tested with

• Google Mobile Ads SDK version 7.58.0.
• Vungle SDK version 6.5.3.

Version 6.4.6.0

• Verified compatibility with Vungle SDK 6.4.6.
• Added support for banner (MREC) ads.
• Fixed a bug where didReceiveInterstitial: callback is called more than once.
• Removed callbacks to adapterWillLeaveApplication, which were previously not invoked at the correct time.

Built and tested with

• Google Mobile Ads SDK version 7.52.0.
• Vungle SDK version 6.4.6.

Version 6.3.2.3

• Fixed a crash in [GADMAdapterVungleRewardedAd adAvailable:].

Version 6.3.2.2

• Fixed a bug where the Vungle adapter would never load rewarded ads if Vungle SDK initialization failed. Now, the adapter will try to re-initialize the Vungle SDK on subsequent rewarded ad requests.
• Now requires Google Mobile Ads SDK version 7.42.2 or higher.

Version 6.3.2.1

• Updated the adapter to use new rewarded API.
• Now requires Google Mobile Ads SDK version 7.41.0 or higher.

Version 6.3.2.0

• Verified compatibility with Vungle SDK 6.3.2.

Version 6.3.0.0

• Verified compatibility with Vungle SDK 6.3.0.
• Updated updateConsentStatus method to updateConsentStatus:consentMessageVersion: in VungleRouterConsent class.

Version 6.2.0.3

• Added adapterDidCompletePlayingRewardBasedVideoAd: callback to the adapter.

Version 6.2.0.2

• Added VungleRouterConsent class which contains updateConsentStatus and getConsentStatus methods.

Version 6.2.0.1

• Updated Vungle SDK initializer correctly.

Version 6.2.0.0

• Verified compatibility with Vungle SDK 6.2.0.

Version 5.4.0.0

• Verified compatibility with Vungle SDK 5.4.0.
• Updated adapter to correctly report clicks to the Google Mobile Ads SDK.

Version 5.3.2.0

• Added two new extras to VungleAdNetworkExtras:
  • ordinal - An integer indicating the order in which this ad was shown in the game session.
  • flexViewAutoDismissSeconds - Sets Flex View ads to automatically close in the specified amount of seconds.
• Verified compatibility with Vungle SDK 5.3.2.

Version 5.3.0.0

• Updated the deployment target to iOS 8.
• Verified compatibility with Vungle SDK 5.3.0.

Version 5.2.0.0

• Verified compatibility with Vungle SDK 5.2.0.

Version 5.1.1.0

• Verified compatibility with Vungle SDK 5.1.1.

Version 5.1.0.0

• Verified compatibility with Vungle SDK 5.1.0.

Earlier versions

• Added support for interstitial and rewarded video ad formats.