미디에이션에 DT Exchange 통합

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:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded
Native

Requirements

  • Android API level 21 or higher

Step 1: Set up configurations in DT Exchange UI

添加新的应用和广告展示位置

注册或登录 DT Exchange 控制台。

点击 Add App（添加应用）按钮添加您的应用。

管理应用

选择您的平台，填写表单的其余部分，然后点击添加展示位置。

在标记为 Name your Placement 的字段中输入新展示位置的名称，然后从下拉列表中选择所需的展示位置类型。最后，点击 Save Placement（保存展示位置）。

初始设置

应用 ID 和展示位置 ID

将鼠标悬停在左侧导航栏上，将其打开。然后，点击左侧菜单中的应用。

菜单

在应用管理页面上，记下您应用旁边的应用 ID。

应用 ID

选择您的应用，前往展示位置标签页，然后点击展示位置名称旁边的复制图标。记下展示位置 ID。

展示位置 ID

发布商 ID、使用方键值和使用方密钥

点击左侧菜单中的用户名，然后选择用户个人资料。

用户个人资料菜单

记下发布商 ID、使用方键值和使用方密钥，因为下一步中会用到这些信息。

用户个人资料

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

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

Ad Manager 계정에 로그인합니다.

게재 > 수익 그룹으로 이동하여 새 수익 그룹 버튼을 클릭합니다.

수익 그룹의 고유한 이름을 입력하고 상태를 활성으로 설정한 후 광고 형식을 선택하고 인벤토리 유형을 모바일 앱으로 설정합니다. 타겟팅 > 인벤토리 섹션에서 미디에이션을 추가할 인벤토리 및 모바일 애플리케이션 아래의 광고 단위를 선택합니다.

그런 다음 수익 파트너 추가 버튼을 클릭합니다.

DT Exchange에 대한 수익 파트너가 이미 있는 경우 이를 선택할 수 있습니다. 그렇지 않은 경우 새 수익 파트너 만들기를 선택합니다.

DT Exchange을 광고 네트워크로 선택하고 고유한 이름을 입력한 다음 미디에이션을 사용 설정합니다.

자동 데이터 수집을 사용 설정하고 이전 섹션에서 확인한Publisher ID, Consumer Secret and Consumer Key 을 입력합니다.

수익 파트너가 선택되면 모바일 SDK 미디에이션을 통합 유형으로, Android를 플랫폼으로, 활성을 상태로 선택합니다. 이전 섹션에서 가져온Application ID and Placement ID 를 입력합니다. 그런 다음 기본 CPM 값을 입력합니다.

완료되면 페이지 하단의 저장을 클릭합니다.

Add Fyber to GDPR and US state regulations ad partners list

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

Step 3: Import the DT Exchange SDK and adapter

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

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.

Java

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

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

Kotlin

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.

Java

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

InneractiveAdManager.setUSPrivacyString("myUSPrivacyString");

Kotlin

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

테스트 광고 사용 설정

Ad Manager

테스트 광고 확인

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

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:

Request parameters and values
InneractiveMediationDefs.KEY_AGE Integer. The age of the user
FyberMediationAdapter.KEY_MUTE_VIDEO Boolean. Mute or unmute video

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

Java 

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();

Kotlin 

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:

Error code Reason
101 DT Exchange server parameters configured in the Ad Manager UI are missing/invalid.
103 The requested ad size does not match a DT Exchange supported banner size.
105 DT Exchange SDK loaded an ad but returned an unexpected controller.
106 Ad is not ready to display.
200-399 DT Exchange SDK returned an error. See code for more details.

DT Exchange Android Mediation Adapter Changelog

Version 8.3.1.0

  • Verified compatibility with DT Exchange SDK 8.3.1.

Built and tested with:

  • Google Mobile Ads SDK version 23.3.0.
  • DT Exchange SDK version 8.3.1.

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.