Integrar a DT Exchange com a Mediação

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

Supported integrations and ad formats

The mediation adapter for DT Exchange has the following capabilities:

Requirements

• Android API level 21 or higher

• Latest Google Mobile Ads SDK

• Complete the mediation Get started guide

Step 1: Set up configurations in DT Exchange UI

Adicionar novo app e posicionamento do anúncio

Inscreva-se ou faça login no DT Exchange Console.

Clique no botão Add App para adicionar seu aplicativo.

Selecione a plataforma, preencha o restante do formulário e clique em Adicionar canais.

Digite um nome para a nova posição no campo Nomeie sua posição e selecione o Tipo de posição desejado na lista suspensa. Por fim, clique em Salvar posição.

ID do aplicativo e da posição

Abra a barra de navegação à esquerda passando o mouse sobre ela. Em seguida, clique em Apps no menu à esquerda.

Na página Gerenciamento de aplicativos, anote o ID do aplicativo ao lado dele.

Selecione seu aplicativo, navegue até a guia Canais e clique no ícone de cópia ao lado de Nome da posição. Anote o ID da posição.

ID do editor, chave do cliente e segredo do cliente

Clique no seu nome de usuário no menu à esquerda e selecione Perfil de usuário.

Anote o ID do editor, a Chave do cliente e a Chave secreta do cliente, porque eles serão necessários na próxima etapa.

Step 2: Set up DT Exchange demand in Ad Manager UI

Definir as configurações de mediação para seu bloco de anúncios

Faça login na sua conta do Ad Manager.

Acesse Exibição > Grupos de rendimento e clique no botão Novo grupo de rendimento.

Insira um Nome exclusivo para o grupo de rendimento, defina o Status como Ativo, selecione o Formato do anúncio e o Tipo de inventário como App para dispositivos móveis. Na seção Segmentação > Inventário, selecione o bloco de anúncios em Inventário e Aplicativo para dispositivos móveis ao qual você quer adicionar a mediação.

Em seguida, clique no botão Adicionar parceiro de rendimento.

Se você já tiver um Parceiro de rendimento para DT Exchange, selecione-o. Caso contrário, selecione Criar um novo parceiro de rendimento.

Selecione DT Exchange como a Rede de publicidade, insira um Nome exclusivo e ative a Mediação.

Ative a Coleta de dados automática e insira o Publisher ID, Consumer Secret and Consumer Key recebido na seção anterior.

Depois de selecionar o Parceiro de rendimento, 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 ID obtido na seção anterior. Em seguida, insira um valor de CPM padrão.

Clique em Salvar na parte inferior da página quando terminar.

Add Fyber 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 Fyber à lista de parceiros de anúncios do GDPR e das regulamentações estaduais dos EUA na Ad Manager IU.

Step 3: Import the DT Exchange 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 DT Exchange SDK and adapter:

dependencies {
    implementation("com.google.android.gms:play-services-ads:23.3.0")
    implementation("com.google.ads.mediation:fyber:8.3.0.0")
}

Manual integration

• Download the latest version of the DT Exchange SDK for Android and add the following files to your project:
  • ia-mraid-kit-release-x.y.z.aar
  • ia-sdk-core-release-x.y.z.aar
  • ia-video-kit-release-x.y.z.aar
• Navigate to the DT Exchange adapter artifacts on Google's Maven Repository. Select the latest version, download the DT Exchange adapter's .aar file, and add it to your project.

Step 4: Implement privacy settings on DT Exchange 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.

DT Exchange contains an API that lets you forward user consent to their SDK. The following sample code shows how to pass consent information to the DT Exchange SDK manually. Should you choose to pass consent information to the DT Exchange SDK manually, it is recommended that this code is called prior to requesting ads through the Google Mobile Ads SDK.

import com.fyber.inneractive.sdk.external.InneractiveAdManager;
// ...

InneractiveAdManager.setGdprConsent(true);
InneractiveAdManager.setGdprConsentString("myGdprConsentString");

import com.fyber.inneractive.sdk.external.InneractiveAdManager
// ...

InneractiveAdManager.setGdprConsent(true)
InneractiveAdManager.setGdprConsentString("myGdprConsentString")

Visit DT Exchange's GDPR Resource Page and their GDPR implementation guide for more details and the values that may 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.

DT Exchange contains an API that lets you forward user consent to their SDK. The following sample code shows how to pass consent information to the DT Exchange SDK manually. Should you choose to pass consent information to the DT Exchange SDK manually, it is recommended that this code is called prior to requesting ads through the Google Mobile Ads SDK.

import com.fyber.inneractive.sdk.external.InneractiveAdManager;
// ...

InneractiveAdManager.setUSPrivacyString("myUSPrivacyString");

import com.fyber.inneractive.sdk.external.InneractiveAdManager
// ...

InneractiveAdManager.setUSPrivacyString("myUSPrivacyString")

Visit DT Exchange's CCPA Resource Page and their CCPA implementation guide for more details and the values that may be provided in the method.

Step 5: Add required code

No additional code is required for DT Exchange integration.

Step 6: Test your implementation

Ativar anúncios de teste

Registre seu dispositivo de teste em Ad Manager

Verificar anúncios de teste

Para verificar se você está recebendo anúncios de teste do DT Exchange, ative os testes de uma única origem no Ad Inspector usando as DT Exchange (Waterfall) origens de anúncios.

Optional steps

Network-specific parameters

The DT Exchange adapter supports additional request parameters that can be passed to the adapter as an Android Bundle. The adapter looks for the following keys in the bundle:

Here's a code example of how to set these ad request parameters:

Bundle extras = new Bundle();
extras.putInt(InneractiveMediationDefs.KEY_AGE, 10);
extras.putBoolean(FyberMediationAdapter.KEY_MUTE_VIDEO, false);

AdRequest request = new AdRequest.Builder()
   .addNetworkExtrasBundle(FyberMediationAdapter.class, extras)
   .build();

var extras = Bundle()
extras.putInt(InneractiveMediationDefs.KEY_AGE, 10)
extras.putBoolean(FyberMediationAdapter.KEY_MUTE_VIDEO, false)

val request = AdRequest.Builder()
   .addNetworkExtrasBundle(FyberMediationAdapter::class.java, extras)
   .build()

Error codes

If the adapter fails to receive an ad from DT Exchange, you can check the underlying error from the ad response using ResponseInfo.getAdapterResponses() under the following class:

com.google.ads.mediation.fyber.FyberMediationAdapter

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

DT Exchange Android Mediation Adapter Changelog

Version 8.3.0.0

• Added support for passing the Google Mobile Ads SDK version to DT Exchange SDK.
• Verified compatibility with DT Exchange SDK 8.3.0.

Built and tested with:

• Google Mobile Ads SDK version 23.2.0.
• DT Exchange SDK version 8.3.0.

Version 8.2.7.0

• Verified compatibility with DT Exchange SDK 8.2.7.

Built and tested with:

• Google Mobile Ads SDK version 23.0.0.
• DT Exchange SDK version 8.2.7.

Version 8.2.6.1

• Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
• Verified compatibility with DT Exchange SDK 8.2.6.

Built and tested with:

• Google Mobile Ads SDK version 23.0.0.
• DT Exchange SDK version 8.2.6.

Version 8.2.6.0

• Verified compatibility with DT Exchange SDK 8.2.6.

Built and tested with:

• Google Mobile Ads SDK version 22.6.0.
• DT Exchange SDK version 8.2.6.

Version 8.2.5.0

• Verified compatibility with DT Exchange SDK 8.2.5.

Built and tested with:

• Google Mobile Ads SDK version 22.5.0.
• DT Exchange SDK version 8.2.5.

Version 8.2.4.0

• Verified compatibility with DT Exchange SDK 8.2.4.

Built and tested with:

• Google Mobile Ads SDK version 22.3.0.
• DT Exchange SDK version 8.2.4.

Version 8.2.3.0

• 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.
• DT Exchange SDK version 8.2.3.

Version 8.2.2.1

• Added support for passing muteVideo key in mediation extra to mute interstitial ads.

Built and tested with:

• Google Mobile Ads SDK version 21.5.0.
• DT Exchange SDK version 8.2.2.

Version 8.2.2.0

• Verified compatibility with DT Exchange SDK 8.2.2.
• Updated the minimum required Google Mobile Ads SDK version to 21.5.0.

Built and tested with:

• Google Mobile Ads SDK version 21.5.0.
• DT Exchange SDK version 8.2.2.

Version 8.2.1.0

• Rebranded adapter name to "DT Exchange".
• Verified compatibility with DT Exchange SDK 8.2.1.
• Updated the minimum required Google Mobile Ads SDK version to 21.3.0.

Built and tested with:

• Google Mobile Ads SDK version 21.3.0.
• DT Exchange SDK version 8.2.1.

Version 8.2.0.0

• Verified compatibility with Fyber SDK 8.2.0.
• 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.
• Fyber SDK version 8.2.0.

Version 8.1.5.0

• Verified compatibility with Fyber SDK 8.1.5.

Built and tested with:

• Google Mobile Ads SDK version 21.0.0.
• Fyber SDK version 8.1.5.

Version 8.1.4.0

• Verified compatibility with Fyber SDK 8.1.4.

Built and tested with:

• Google Mobile Ads SDK version 21.0.0.
• Fyber SDK version 8.1.4.

Version 8.1.3.1

• Updated compileSdkVersion and targetSdkVersion 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.
• Fyber SDK version 8.1.3.

Version 8.1.3.0

• Verified compatibility with Fyber SDK 8.1.3.
• 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.
• Fyber SDK version 8.1.3.

Version 8.1.2.0

• Verified compatibility with Fyber SDK 8.1.2.
• 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.
• Fyber SDK version 8.1.2.

Version 8.1.0.0

• Verified compatibility with Fyber SDK 8.1.0.

Built and tested with:

• Google Mobile Ads SDK version 20.4.0.
• Fyber SDK version 8.1.0.

Version 7.8.4.1

• Fixed an issue where the adapter would not initialize if there is a duplicate or more than one unique app ID from the mediation configurations.
• Updated the minimum required Google Mobile Ads SDK version to 20.4.0.

Built and tested with:

• Google Mobile Ads SDK version 20.4.0.
• Fyber SDK version 7.8.4.

Version 7.8.4.0

• Verified compatibility with Fyber SDK 7.8.4.
• Updated the minimum required Google Mobile Ads SDK version to 20.3.0.
• Fixed an issue with rewarded display ads, where onVideoComplete() was not called.
• Fyber now requires an Activity context to show ads.

Built and tested with:

• Google Mobile Ads SDK version 20.3.0.
• Fyber SDK version 7.8.4.

Version 7.8.3.0

• Verified compatibility with Fyber SDK 7.8.3.
• Added standardized adapter error codes and messages.
• Updated the minimum required Google Mobile Ads SDK version to 20.1.0.

Built and tested with:

• Google Mobile Ads SDK version 20.1.0.
• Fyber SDK version 7.8.3.

Version 7.8.2.0

• Verified compatibility with Fyber SDK 7.8.2.
• 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.
• Fyber SDK version 7.8.2.

Version 7.8.1.0

• Verified compatibility with Fyber SDK 7.8.1.

Built and tested with:

• Google Mobile Ads SDK version 19.7.0.
• Fyber SDK version 7.8.1.

Version 7.8.0.0

• Verified compatibility with Fyber SDK 7.8.0.
• 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.
• Fyber SDK version 7.8.0.

Version 7.7.4.0

• Verified compatibility with Fyber SDK 7.7.4.
• Fixed an issue where onUserEarnedReward() is forwarded twice for rewarded ads.

Built and tested with:

• Google Mobile Ads SDK version 19.5.0.
• Fyber SDK version 7.7.4.

Version 7.7.3.0

• Verified compatibility with Fyber SDK 7.7.3.

Built and tested with:

• Google Mobile Ads SDK version 19.5.0.
• Fyber SDK version 7.7.3.

Version 7.7.2.0

• Verified compatibility with Fyber SDK 7.7.2.
• 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.
• Fyber SDK version 7.7.2.

Version 7.7.1.0

• Verified compatibility with Fyber SDK 7.7.1.
• 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.
• Fyber SDK version 7.7.1.

Version 7.7.0.0

• Verified compatibility with Fyber SDK 7.7.0.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.7.0.

Version 7.6.1.0

• Verified compatibility with Fyber SDK 7.6.1.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.6.1.

Version 7.6.0.0

• Verified compatibility with Fyber SDK 7.6.0.
• Updated the adapter to support inline adaptive banner requests.
• Updated the minimum required Google Mobile Ads SDK version to 19.3.0.
• Fixed a bug where onAdOpened()/onAdClosed() methods were not being called for banner ads.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.6.0.

Version 7.5.4.0

• Verified compatibility with Fyber SDK 7.5.4.
• Updated the minimum required Google Mobile Ads SDK version to 19.1.0.

Built and tested with:

• Google Mobile Ads SDK version 19.1.0.
• Fyber SDK version 7.5.4.

Version 7.5.3.0

• Verified compatibility with Fyber SDK 7.5.3.

Built and tested with:

• Google Mobile Ads SDK version 19.0.1.
• Fyber SDK version 7.5.3.

Version 7.5.2.0

• Verified compatibility with Fyber SDK 7.5.2.
• 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.
• Fyber SDK version 7.5.2.

Version 7.5.0.0

• Verified compatibility with Fyber SDK 7.5.0.
• Fixed NullPointerException crash during Fyber ad loading.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Fyber SDK version 7.5.0.

Version 7.4.1.0

• Verified compatibility with Fyber SDK 7.4.1.
• Updated the minimum required Google Mobile Ads SDK version to 18.3.0.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Fyber SDK version 7.4.1.

Version 7.3.4.0

• Initial release!
• Supports Banner, Interstitial and Rewarded ads.

Built and tested with:

• Google Mobile Ads SDK version 18.2.0.
• Fyber SDK version 7.3.4.