Liftoff Monetize를 미디에이션과 통합

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Liftoff Monetize using AdMob 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 mediation adapter for Liftoff Monetize has the following capabilities:

Integration
Bidding
Waterfall
Formats
App Open 1, 3
Banner 2
Interstitial
Rewarded
Rewarded Interstitial 2
Native 2

1 Bidding integration for this format is in closed beta.

2 Bidding integration for this format is in open beta.

3 Waterfall integration for this format is in closed beta.

Requirements

Step 1: Set up configurations in Liftoff Monetize UI

注册或登录您的 Liftoff Monetize 帐号。

点击添加应用按钮，将您的应用添加到 Liftoff Monetize 信息中心。

填写表单，输入所有必填的详细信息。

创建应用后，从 Liftoff Monetize Applications 信息中心选择您的应用。

记下应用 ID。

添加新的展示位置

如需创建要与 AdMob中介结合使用的新展示位置，请前往 Liftoff“Monetize Placement”信息中心，点击添加展示位置按钮，然后从下拉列表中选择您的应用。

有关添加新展示位置的详情，请参见下文：

打开应用

选择插页式，然后输入展示位置名称。然后，针对可跳过选择是，并填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮以创建展示位置。

选择横幅，输入展示位置名称，然后填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮创建展示位置。

300 x 250 横幅

选择 MREC，输入展示位置名称，然后填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮创建展示位置。

插页式广告

选择 插页式广告，输入展示位置名称，然后填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮以创建展示位置。

已奖励

选择激励广告，输入展示位置名称并填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮创建展示位置。

插页式激励广告

选择激励广告。输入展示位置名称，启用可跳过并填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮以创建展示位置。

原生

选择原生，输入展示位置名称，然后填写表单的其余部分。[仅出价] 在创收下，将应用内出价开关切换为已启用。点击页面底部的继续按钮创建展示位置。

记下参考 ID，然后点击听起来不错。

打开应用

300 x 250 横幅

插页式广告

已奖励

插页式激励广告

原生

找到您的 Reporting API 密钥

出价

出价集成不需要执行此步骤。

瀑布

除了应用 ID 和参考 ID 之外，您还需要 Liftoff Monetize Reporting API 密钥才能设置AdMob 广告单元 ID。前往 Liftoff Monetize Reports 信息中心，然后点击 Reporting API Key 按钮，查看您的 Reporting API Key。

开启测试模式

如需启用测试广告，请转到 Liftoff Monetize 信息中心并导航到 Applications。

在应用的展示位置参考 ID 部分下，选择要启用测试广告的应用。在状态部分下，将测试模式选为仅显示测试广告即可启用测试广告。

Step 2: Set up Liftoff Monetize demand in AdMob UI

광고 단위에 대한 미디에이션 설정 구성

Liftoff Monetize 를 광고 단위의 미디에이션 구성에 추가해야 합니다.

먼저 AdMob 계정에 로그인합니다. 그런 다음 미디에이션 탭으로 이동합니다. 수정할 기존 미디에이션 그룹이 있는 경우 해당 미디에이션 그룹의 이름을 클릭하여 수정한 후 Liftoff Monetize 광고 소스로 추가로 건너뜁니다.

새 미디에이션 그룹을 만들려면 미디에이션 그룹 만들기를 선택합니다.

광고 형식과 플랫폼을 입력하고 계속을 클릭합니다.

미디에이션 그룹에 이름을 지정하고 타겟팅할 위치를 선택합니다. 미디에이션 그룹 상태를 사용으로 설정한 다음 광고 단위 추가를 클릭합니다.

이 미디에이션 그룹을 하나 이상의 기존AdMob 광고 단위와 연결합니다. 그런 다음 완료를 클릭합니다.

이제 광고 단위 카드가 선택한 광고 단위로 채워진 것을 볼 수 있습니다.

광고 소스로 Liftoff Monetize 추가

입찰

광고 소스 섹션의 입찰 카드에서 광고 소스 추가를 선택합니다. 그런 다음 Liftoff Monetize을 선택합니다.

파트너십 계약을 체결하는 방법을 클릭하고Liftoff Monetize과(와) 입찰 파트너십을 설정합니다.

확인 및 동의를 클릭한 다음 계속을 클릭합니다.

이미 Liftoff Monetize에 대한 매핑이 있는 경우 해당 매핑을 선택할 수 있습니다. 그렇지 않으면 매핑 추가를 클릭합니다.

그런 다음 이전 섹션에서 얻은 Application ID and Placement Reference ID를 입력합니다. 그런 다음 완료를 클릭합니다.

중요: Application ID 는Liftoff Monetize UI에서와 같이 타겟팅된 앱과 연결되어야 합니다.

폭포

광고 소스 섹션의 폭포식 구조 카드에서 광고 소스 추가를 선택합니다. 그런 다음 Liftoff Monetize을 선택합니다.

Liftoff Monetize를 선택하고 최적화 스위치를 사용 설정합니다. 이전 섹션에서 가져온 Reporting API Key을 입력하여Liftoff Monetize에 대해 광고 소스 최적화를 설정합니다. 그런 다음Liftoff Monetize 에 eCPM 값을 입력하고 계속을 클릭합니다.

이미 Liftoff Monetize에 대한 매핑이 있는 경우 해당 매핑을 선택할 수 있습니다. 그렇지 않으면 매핑 추가를 클릭합니다.

그런 다음 이전 섹션에서 얻은 Application ID and Placement Reference ID를 입력합니다. 그런 다음 완료를 클릭합니다.

Add Liftoff to GDPR and US state regulations ad partners list

GDPR 설정 및 미국 주 규정 설정 Liftoff 를 AdMob UI의 GDPR 및 미국 주 규정 광고 파트너 목록에 추가합니다.

Step 3: Import the Vungle SDK and adapter

  • 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 Liftoff Monetize adapter from the download link in the Changelog and link LiftoffMonetizeAdapter.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: Implement privacy settings on Liftoff Monetize SDK

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.

Liftoff Monetize includes 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.

Swift

import VungleAdsSDK
// ...

VunglePrivacySettings.setGDPRStatus(true)
VunglePrivacySettings.setGDPRMessageVersion("v1.0.0")

Objective-C

#import <VungleAdsSDK/VungleAdsSDK.h>
// ...

[VunglePrivacySettings setGDPRStatus:YES];
[VunglePrivacySettings setGDPRMessageVersion:@"v1.0.0"];

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

US states privacy laws

U.S. states privacy laws require giving users 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 U.S. states privacy laws compliance 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.

Liftoff Monetize includes 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.

Swift

import VungleAdsSDK
// ...

VunglePrivacySettings.setCCPAStatus(true)

Objective-C

#import <VungleAdsSDK/VungleAdsSDK.h>
// ...

[VunglePrivacySettings setCCPAStatus:YES];

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

Step 5: Add required code

SKAdNetwork integration

Follow Liftoff Monetize's documentation to add the SKAdNetwork identifiers to your project's Info.plist file.

Step 6: Test your implementation

테스트 광고 사용 설정

AdMob 용 테스트 기기를 등록하고 Liftoff Monetize UI에서 테스트 모드를 사용 설정해야 합니다.

테스트 광고 확인

Liftoff Monetize에서 테스트 광고를 수신하고 있는지 확인하려면 광고 검사기에서 Liftoff Monetize (Bidding) and Liftoff Monetize (Waterfall) 광고 소스를 사용하여 단일 광고 소스 테스트를 사용 설정하세요.

Optional steps

Network-specific parameters

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

userId
A string representing Liftoff Monetize's Incentivized User ID.
nativeAdOptionPosition
An integer specifying the privacy icon position for native ads.

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

Swift

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

let request = GADRequest()
let extras = VungleAdNetworkExtras()
extras.userId = "myUserID"
extras.nativeAdOptionPosition = 1
// ...
request.register(extras)

Objective-C

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

GADRequest *request = [GADRequest request];
VungleAdNetworkExtras *extras = [[VungleAdNetworkExtras alloc] init];
extras.userId = @"myUserID";
extras.nativeAdOptionPosition = 1;
// ...
[request registerAdNetworkExtras:extras];

Native ads rendering

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

Field Assets always included by Liftoff Monetize adapter
Headline
Image 1
Media view
Body
App icon
Call to action
Star rating
Store
Price

1 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:

Format Class name
Banner GADMAdapterVungleInterstitial
Interstitial GADMAdapterVungleInterstitial
Rewarded GADMAdapterVungleRewardBasedVideoAd

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

Error code Domain Reason
1-100 Sent by Vungle SDK Vungle SDK returned an error. See code for more details.
101 com.google.mediation.vungle Liftoff Monetize server parameters configured in the AdMob UI are missing/invalid.
102 com.google.mediation.vungle An ad is already loaded for this network configuration. Vungle SDK cannot load a second ad for the same placement ID.
103 com.google.mediation.vungle The requested ad size does not match a Liftoff Monetize supported banner size.
104 com.google.mediation.vungle Vungle SDK could not render the banner ad.
105 com.google.mediation.vungle Vungle SDK only supports loading 1 banner ad at a time, regardless of placement ID.
106 com.google.mediation.vungle Vungle SDK sent a callback saying the ad is not playable.

Liftoff Monetize iOS Mediation Adapter Changelog

Next version

  • Added custom size banner ad support.

Version 7.4.0.0

  • Verified compatibility with Vungle SDK 7.4.0.

Built and tested with:

  • Google Mobile Ads SDK version 11.6.0.
  • Vungle SDK version 7.4.0.

Version 7.3.2.0

  • Verified compatibility with Vungle SDK 7.3.2.

Built and tested with:

  • Google Mobile Ads SDK version 11.3.0.
  • Vungle SDK version 7.3.2.

Version 7.3.1.1.0

  • Verified compatibility with Vungle SDK 7.3.1.1.

Built and tested with:

  • Google Mobile Ads SDK version 11.3.0.
  • Vungle SDK version 7.3.1.1.

Version 7.3.1.0

  • Verified compatibility with Vungle SDK 7.3.1.

Built and tested with:

  • Google Mobile Ads SDK version 11.3.0.
  • Vungle SDK version 7.3.1.

Version 7.3.0.0

  • Verified compatibility with Vungle SDK 7.3.0.
  • Fixed an issue where the adapter cannot be imported in Swift.
  • Added waterfall and bidding support for app open ad format.

Built and tested with:

  • Google Mobile Ads SDK version 11.2.0.
  • Vungle SDK version 7.3.0.

Version 7.2.2.1

  • Now requires minimum iOS version 12.0.
  • Now requires Google Mobile Ads SDK version 11.0 or higher.
  • Included Info.plist in the frameworks within LiftoffMonetizeAdapter.xcframework.

Built and tested with:

  • Google Mobile Ads SDK version 11.0.1.
  • Vungle SDK version 7.2.2.

Version 7.2.2.0

  • Verified compatibility with Vungle SDK 7.2.2.
  • Now requires minimum iOS version of 12.0.

Built and tested with:

  • Google Mobile Ads SDK version 11.0.0.
  • Vungle SDK version 7.2.2.

Version 7.2.1.1

  • Updated the MREC matching to be any size that can fit an MREC instead of being an exact match.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • Vungle SDK version 7.2.1.

Version 7.2.1.0

  • Verified compatibility with Vungle SDK 7.2.1.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • Vungle SDK version 7.2.1.

Version 7.2.0.0

  • Verified compatibility with Vungle SDK 7.2.0.
  • Removed the deprecated willBackgroundApplication delegate methods from the banner and interstitial ad implementations.
  • Replaced the deprecated childDirectedTreatment method with the GADMobileAds.sharedInstance.requestConfiguration.tagForChildDirectedTreatment property.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • Vungle SDK version 7.2.0.

Version 7.1.0.0

  • Verified compatibility with Vungle SDK 7.1.0.

Built and tested with:

  • Google Mobile Ads SDK version 10.10.0.
  • Vungle SDK version 7.1.0.

Version 7.0.1.0

  • Added watermark support for bidding ads.
  • Verified compatibility with Vungle SDK 7.0.1.

Built and tested with:

  • Google Mobile Ads SDK version 10.7.0.
  • Vungle SDK version 7.0.1.

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.