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 Android app.
Supported integrations and ad formats
The mediation adapter for Liftoff Monetize has the following capabilities:
Integration | |
---|---|
Bidding | 1 |
Waterfall | |
Formats | |
App Open | |
Banner | |
Interstitial | |
Rewarded | |
Rewarded Interstitial | 3 |
Native | 2 |
1 Bidding integration is in open beta.
2 Bidding integration for this format is in closed beta.
3 Rewarded
interstitial requires assistance to set up. Reach out to your account
manager at Liftoff Monetize or monetize@liftoff.io
.
Requirements
Android API level 21 or higher
Latest Google Mobile Ads SDK
Complete the mediation Get started guide
Step 1: Set up configurations in Liftoff Monetize UI
Inscreva-se ou faça login na sua conta da Liftoff Monet.
Adicione seu app ao painel da Liftoff Monetize clicando no botão Add Application (Adicionar aplicativo).
Preencha o formulário com todos os detalhes necessários.
Depois que seu app for criado, selecione-o no painel Liftoff Monetize Applications (link em inglês).
Anote o ID do app.
Adicionar novos canais
Para criar uma nova posição a ser usada com a mediação Ad Manager, acesse o painel de posições "Liftoff Monetize respectivo", clique no botão Adicionar posição e selecione seu app na lista suspensa.
Confira abaixo os detalhes para adicionar novos canais:
Banner
Selecione Banner, insira um Nome de posição e preencha o restante do formulário. [Somente lances] Em Monetização, alterne a chave Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a posição.
Banner de 300 x 250
Selecione MREC, insira um nome da posição e preencha o restante do formulário. [Somente lances] Em Monetização, alterne a chave Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a posição.
Intersticial
Selecione Intersticial, insira um Nome de posição e preencha o restante do formulário. [Somente lances] Em Monetização, alterne a chave Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a posição.
Premiado
Selecione Premiado, insira um Nome da posição e preencha o restante do formulário. [Somente lances] Em Monetização, alterne a chave Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a posição.
Intersticial premiado
Selecione Premiado. Insira o Nome da posição, ative a opção Pulável e preencha o restante do formulário. [Somente lances] Em Monetização, mude a opção Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a colocação.
Nativo
Selecione Nativo, insira um nome de posição e preencha o restante do formulário. [Somente lances] Em Monetização, alterne a chave Lances no app para Ativado. Clique no botão Continuar na parte inferior da página para criar a posição.
Anote o ID de referência e clique em Tudo certo.
Banner
Banner de 300 x 250
Intersticial
Premiado
Intersticial premiado
Nativo
Localize sua chave da API Reporting
Lances
Esta etapa não é necessária para integrações de lances.
Cascata
Além do ID do app e do ID de referência, você também vai precisar da chave da API Reporting da Liftoff Monetize para configurar o Ad Manager ID do bloco de anúncios. Acesse o painel de relatórios do Liftoff Monetize e clique no botão Chave da API Reporting para visualizar a chave da API Reporting.
Ativar modo de teste
Para ativar anúncios de teste, acesse o painel da Liftoff Monetize e acesse Aplicativos.
Selecione o aplicativo para o qual você quer ativar os anúncios de teste na seção ID de referência da posição do seu aplicativo. Para ativar os anúncios de teste, selecione Modo de teste como Exibir somente anúncios de teste na seção Status.
Step 2: Set up Liftoff Monetize demand in Ad Manager UI
Faça login na sua conta do Ad Manager.
Adicionar Liftoff Monetize em "Empresas"
Lances
Esta etapa não é necessária para integrações de lances.
Cascata
Acesse Administrador > Empresas e clique no botão Nova empresa na guia Todas as empresas. Selecione Rede de publicidade.
Selecione Liftoff Monetize como a Rede de publicidade, insira um Nome exclusivo e ative a Mediação. Ative a Coleta automática de dados e insira o Reporting API Key recebido na seção anterior.
Não é necessário digitar um Nome de usuário ou uma Senha. Clique em Salvar quando concluir.
Ativar o compartilhamento de indicador seguro
Lances
Acesse Administrador > Configurações globais. Acesse a guia Configurações da conta do Ad Exchange, revise e ative a opção Compartilhamento de indicador seguro. Clique em Salvar.
Cascata
Essa etapa não é necessária para integrações em hierarquia.
Configurar Liftoff Monetize lances
Lances
Navegue até Exibição > Bidders e clique em Novo bidder na guia Lances do SDK.
Selecione Liftoff Monetize como bidder.
Ative a opção Adicionar a biblioteca de indicadores deste bidder à lista de indicadores permitidos e Permitir que os indicadores sejam compartilhados com este bidder. Em seguida, clique em Continuar.
Clique em Continuar.
Clique em Concluído.
Cascata
Essa etapa não é necessária para integrações em hierarquia.
Configurar o mapeamento de blocos de anúncios
Lances
Navegue até Exibição > Bidders e selecione a empresa para Liftoff Monetize na guia Lances do SDK.
Acesse a guia Mapeamento de bloco de anúncios e clique em Novo mapeamento de bloco de anúncios.
Escolha Bloco de anúncios específico. Selecione um bloco de anúncios e um formato, App para dispositivos móveis como o Tipo de inventário e seu Aplicativo para dispositivos móveis. Em seguida, digite o Application ID and Placement Reference ID obtido na seção anterior. Por fim, clique em Salvar.
.Cascata
Navegue até Exibição > Grupos de rendimento e clique no botão Novo grupo de rendimento. Selecione seu Aplicativo para dispositivos móveis.
Role para baixo e clique em Adicionar parceiro de rendimento.
Selecione a empresa que você criou para Liftoff Monetizena seção anterior. Escolha Mediação do SDK para dispositivos móveis como o Tipo de integração, Android como Plataforma e Ativo como o Status.
Insira o Application ID and Placement Reference IDobtido na seção anterior e o valor de CPM padrão. Clique em Salvar.
Observação: a coleta de dados automática leva alguns dias para coletar dados antes de calcular com precisão um valor de CPM dinâmico para uma rede de mediação. Assim que o eCPM for calculado, ele será atualizado automaticamente.
Add Liftoff to GDPR and US state regulations ad partners list
Siga as etapas em Configurações do GDPR e Configurações das regulamentações estaduais dos EUA para adicionar Liftoff à lista de parceiros de anúncios do GDPR e das regulamentações estaduais dos EUA na Ad Manager IU.
Step 3: Import the Vungle SDK and adapter
Android Studio integration (recommended)
In your app-level build.gradle.kts
file, add the following implementation
dependencies and configurations. Use the latest versions of the Vungle SDK
and adapter:
dependencies {
implementation("com.google.android.gms:play-services-ads:23.3.0")
implementation("com.google.ads.mediation:vungle:7.4.0.1")
}
Manual integration
Download the latest Vungle Android SDK and extract the
.jar
files under thelibs
folder and add it to your project.Navigate to the Liftoff Monetize adapter artifacts on Google's Maven Repository. Select the latest version, download the Vungle adapter's
.aar
file, and add it to your project.
Step 4: Implement privacy settings on Liftoff Monetize SDK
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.
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.
Java
import com.vungle.ads.VunglePrivacySettings;
// ...
VunglePrivacySettings.setGDPRStatus(true, "v1.0.0");
Kotlin
import com.vungle.ads.VunglePrivacySettings
// ...
VunglePrivacySettings.setGDPRStatus(true, "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.
Java
import com.vungle.ads.VunglePrivacySettings;
// ...
VunglePrivacySettings.setCCPAStatus(true);
Kotlin
import com.vungle.ads.VunglePrivacySettings
// ...
VunglePrivacySettings.setCCPAStatus(true)
See CCPA implementation for more details and the values that can be provided in the method.
Step 5: Add required code
No additional code required for Liftoff Monetize integration.
Step 6: Test your implementation
Ativar anúncios de teste
Registre seu dispositivo de teste em Ad Manager e ative o modo de teste na Liftoff Monetize interface.
Verificar anúncios de teste
Para verificar se você está recebendo anúncios de teste do Liftoff Monetize, ative os testes de uma única origem no Ad Inspector usando as Liftoff Monetize (Bidding) and Liftoff Monetize (Waterfall) origens de anúncios.
Optional steps
Network-specific parameters
The Liftoff Monetize adapter supports the following additional request parameters which can be passed to the adapter:
userId
- A string representing Liftoff Monetize's Incentivized User ID.
adOrientation
- An integer specifying the presentation orientation for full-screen ads.
Here's a code example of how to create an ad request that sets these parameters:
Java
Bundle extras = new Bundle();
extras.putString(VungleConstants.KEY_USER_ID, "myUserID");
extras.putInt(VungleConstants.KEY_ORIENTATION, 1);
AdManagerAdRequest request = new AdManagerAdRequest.Builder()
.addNetworkExtrasBundle(VungleAdapter.class, extras) // Rewarded.
.addNetworkExtrasBundle(VungleInterstitialAdapter.class, extras) // Interstitial.
.build();
Kotlin
val extras = Bundle()
extras.putString(VungleConstants.KEY_USER_ID, "myUserID")
extras.putInt(VungleConstants.KEY_ORIENTATION, 1)
val request = AdManagerAdRequest.Builder()
.addNetworkExtrasBundle(VungleAdapter::class, extras) // Rewarded.
.addNetworkExtrasBundle(VungleInterstitialAdapter.class, extras) // Interstitial.
.build()
Native ads rendering
The Liftoff Monetize adapter returns its native ads as
NativeAd
objects. It populates the following
fields
for a
NativeAd
.
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
MediaView
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
ResponseInfo.getAdapterResponses()
under the following classes:
Format | Class name |
---|---|
Banner | com.vungle.mediation.VungleInterstitialAdapter |
Interstitial | com.vungle.mediation.VungleInterstitialAdapter |
Rewarded | com.vungle.mediation.VungleAdapter |
Here are the codes and accompanying messages thrown by the Liftoff Monetize adapter when an ad fails to load:
Error code | Domain | Reason |
---|---|---|
0-100 | com.vungle.warren | Vungle SDK returned an error. See document for more details. |
101 | com.google.ads.mediation.vungle | Invalid server parameters (e.g. app ID or placement ID). |
102 | com.google.ads.mediation.vungle | The requested banner size does not map to a valid Liftoff Monetize ad size. |
103 | com.google.ads.mediation.vungle | Liftoff Monetize requires an Activity context to request ads. |
104 | com.google.ads.mediation.vungle | The Vungle SDK cannot load multiple ads for the same placement ID. |
105 | com.google.ads.mediation.vungle | The Vungle SDK failed to initialize. |
106 | com.google.ads.mediation.vungle | Vungle SDK returned a successful load callback, but Banners.getBanner() or Vungle.getNativeAd() returned null. |
107 | com.google.ads.mediation.vungle | Vungle SDK is not ready to play the ad. |
Liftoff Monetize Android Mediation Adapter Changelog
Version 7.4.0.1
- Added custom ad size support for bidding and waterfall banner ads.
Built and tested with:
- Google Mobile Ads SDK version 23.2.0.
- Vungle SDK version 7.4.0.
Version 7.4.0.0
- Extended the
VungleInterstitialAdapter
class fromVungleMediationAdapter
to add waterfall support for the app open ad format on Google Ad Manager. - Verified compatibility with Vungle SDK 7.4.0.
Built and tested with:
- Google Mobile Ads SDK version 23.2.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 23.0.0.
- Vungle SDK version 7.3.2.
Version 7.3.1.0
- Verified compatibility with Vungle SDK 7.3.1.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Vungle SDK version 7.3.1.
Version 7.3.0.0
- Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
- Verified compatibility with Vungle SDK 7.3.0.
- Added waterfall and bidding support for app open ad format.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Vungle SDK version 7.3.0.
Version 7.1.0.0
- Verified compatibility with Vungle SDK 7.1.0.
Built and tested with:
- Google Mobile Ads SDK version 22.3.0.
- Vungle SDK version 7.1.0.
Version 7.0.0.1
- Fixed an issue where Google Mobile Ads SDK was not recording impressions for bidding native ads.
- Reverted the adapter to depend on Google Mobile Ads SDK version 22.3.0.
Built and tested with:
- Google Mobile Ads SDK version 22.3.0.
- Vungle SDK version 7.0.0.
Version 7.0.0.0
- Added support to load multiple ads with the same placement ID for all waterfall ad formats.
- Rebranded adapter name from Vungle to Liftoff Monetize.
- Verified compatibility with Vungle SDK 7.0.0.
Built and tested with:
- Google Mobile Ads SDK version 22.4.0.
- Vungle SDK version 7.0.0.
Version 6.12.1.1
- Updated adapter to use new
VersionInfo
class. - Updated the minimum required Google Mobile Ads SDK version to 22.0.0.
Built and tested with:
- Google Mobile Ads SDK version 22.0.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 21.4.0.
- Vungle SDK version 6.12.1.
Version 6.12.0.1
- Added bidding support for banner ad format.
- Verified compatibility with Vungle SDK 6.12.0.
- Updated the minimum required Google Mobile Ads SDK version to 21.4.0.
Built and tested with:
- Google Mobile Ads SDK version 21.4.0.
- Vungle SDK version 6.12.0.
Version 6.12.0.0
- Added waterfall mediation and bidding support for rewarded interstitial ad format.
- Added bidding support for native ad format.
Built and tested with:
- Google Mobile Ads SDK version 21.1.0.
- Vungle SDK version 6.12.0.
Version 6.11.0.3
- Added waterfall mediation support for native ad format.
- Updated the minimum required Google Mobile Ads SDK version to 21.1.0.
Built and tested with:
- Google Mobile Ads SDK version 21.1.0.
- Vungle SDK version 6.11.0.
Version 6.11.0.2
- Added support for loading multiple ads for the same placement ID in rewarded bidding ads.
Built and tested with:
- Google Mobile Ads SDK version 21.0.0.
- Vungle SDK version 6.11.0.
Version 6.11.0.1
- Updated
compileSdkVersion
andtargetSdkVersion
to API 31. - Updated the minimum required Google Mobile Ads SDK version to 21.0.0.
- Updated the minimum required Android API level to 19.
Built and tested with:
- Google Mobile Ads SDK version 21.0.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 20.6.0.
- Vungle SDK version 6.11.0.
Version 6.10.5.0
- Verified compatibility with Vungle SDK 6.10.5.
- Updated the minimum required Google Mobile Ads SDK version to 20.6.0.
Built and tested with:
- Google Mobile Ads SDK version 20.6.0.
- Vungle SDK version 6.10.5.
Version 6.10.4.0
- Verified compatibility with Vungle SDK 6.10.4.
Built and tested with:
- Google Mobile Ads SDK version 20.5.0.
- Vungle SDK version 6.10.4.
Version 6.10.3.0
- Verified compatibility with Vungle SDK 6.10.3.
Built and tested with:
- Google Mobile Ads SDK version 20.5.0.
- Vungle SDK version 6.10.3.
Version 6.10.2.1
- Verified compatibility with Vungle SDK 6.10.2.
- Added bidding support for interstitial and rewarded ad formats.
- Updated the minimum required Google Mobile Ads SDK version to 20.5.0.
Built and tested with:
- Google Mobile Ads SDK version 20.5.0.
- Vungle SDK version 6.10.2.
Version 6.10.2.0
- Verified compatibility with Vungle SDK 6.10.2.
- Fixed an adapter issue by replacing parameter
serverParameters
, withmediationExtras
to obtain Vungle network-specific parameters, when requesting Banner and Interstitial ads.
Built and tested with:
- Google Mobile Ads SDK version 20.3.0.
- Vungle SDK version 6.10.2.
Version 6.10.1.0
- Verified compatibility with Vungle SDK 6.10.1.
- Updated the minimum required Google Mobile Ads SDK version to 20.3.0.
- MREC Ads are now supported with Vungle's banner API.
- Updated standardized error codes and messages.
Built and tested with:
- Google Mobile Ads SDK version 20.3.0.
- Vungle SDK version 6.10.1.
Version 6.9.1.1
- Updated the minimum required Google Mobile Ads SDK version to 20.0.0.
Built and tested with:
- Google Mobile Ads SDK version 20.0.0.
- Vungle SDK version 6.9.1.
Version 6.9.1.0
- Verified compatibility with Vungle SDK 6.9.1.
- Added support for OMSDK.
- Various bug fixes.
- Rewarded Ad Support for Vungle onAdViewed callback.
- Updated the minimum required Google Mobile Ads SDK version to 19.7.0.
Built and tested with:
- Google Mobile Ads SDK version 19.7.0.
- Vungle SDK version 6.9.1.
Version 6.8.1.1
- Updated the minimum required Google Mobile Ads SDK version to 19.6.0.
Built and tested with:
- Google Mobile Ads SDK version 19.6.0.
- Vungle SDK version 6.8.1.
Version 6.8.1.0
- Verified compatibility with Vungle SDK 6.8.1.
- Updated the minimum required Google Mobile Ads SDK version to 19.5.0.
Built and tested with:
- Google Mobile Ads SDK version 19.5.0.
- Vungle SDK version 6.8.1.
Version 6.8.0.0
- Verified compatibility with Vungle SDK 6.8.0.
- Updated the adapter to not forward
onAdClosed()
when banner ads are refreshed or destroyed. - Remove
FlexFeed
andFlexView
(deprecated in Vungle 6.8.0). - Updated the minimum required Google Mobile Ads SDK version to 19.4.0.
Built and tested with:
- Google Mobile Ads SDK version 19.4.0.
- Vungle SDK version 6.8.0.
Version 6.7.1.0
- Verified compatibility with Vungle SDK 6.7.1.
- Fixed a bug where ads wouldn't load if an ad was loaded using an application context.
- Updated
targetSdkVersion
to API 29. - Updated the minimum required Google Mobile Ads SDK version to 19.3.0.
Built and tested with:
- Google Mobile Ads SDK version 19.3.0.
- Vungle SDK version 6.7.1.
Version 6.7.0.0
- Verified compatibility with Vungle SDK 6.7.0.
- Updated the adapter to support inline adaptive banner requests.
- Interstitial and rewarded ads are now unmuted by default.
- Interstitial ads now forward the
onAdLeftApplication()
callback when clicked. - Updated the minimum required Google Mobile Ads SDK version to 19.2.0.
Built and tested with:
- Google Mobile Ads SDK version 19.2.0.
- Vungle SDK version 6.7.0.
Version 6.5.3.0
- Verified compatibility with Vungle SDK 6.5.3.
- Add support for the newly-introduced Vungle's Banner format.
- Updated the minimum required Google Mobile Ads SDK version to 19.0.1.
Built and tested with:
- Google Mobile Ads SDK version 19.0.1.
- Vungle SDK version 6.5.3.
Version 6.4.11.1
- Fixed an issue where banner ads failed to refresh.
Version 6.4.11.0
- Verified compatibility with Vungle SDK 6.4.11.
- Added support for banner ads.
- Migrated the adapter to AndroidX.
- Updated the minimum required Google Mobile Ads SDK version to 18.2.0.
Version 6.3.24.1
- Updated adapter to support new open-beta Rewarded API.
- Updated the minimum required Google Mobile Ads SDK version to 17.2.0.
Version 6.3.24.0
- Verified compatibility with Vungle SDK 6.3.24.
Version 6.3.17.0
- Verified compatibility with Vungle SDK 6.3.17.
Version 6.3.12.0
- Verified compatibility with Vungle SDK 6.3.12.
Version 6.2.5.1
- Updated the adapter to invoke the
onRewardedVideoComplete()
ad event.
Version 6.2.5.0
- Verified compatibility with Vungle SDK 6.2.5.
Version 5.3.2.1
- Updated adapter to correctly report clicks to the Google Mobile Ads SDK.
Version 5.3.2.0
- Verified compatibility with Vungle SDK 5.3.2.
- Updated the Adpater project for Android Studio 3.0.
- Added the following methods to Bundle builder class.
setOrdinalViewCount
: This field is used to pass the mediation ordinal, whenever Publisher receives the ordinal data reports from Vungle.setFlexViewCloseTimeInSec
: This option is used to make flex view ads dismiss on their own after the specified number of seconds.
Version 5.3.0.0
- Verified compatibility with Vungle SDK 5.3.0.
Version 5.1.0.0
- Updated the adapter to make it compatible with Vungle SDK 5.1.0.
- Changed the version naming system to [Vungle SDK version].[adapter patch version].
Earlier versions
- Added support for interstitial and rewarded video ad formats.