This guide shows you how to use the Google Mobile Ads SDK to load and display ads from DT Exchange using AdMob 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
Latest Google Mobile Ads SDK
Complete the mediation Get started guide
Step 1: Set up configurations in DT Exchange UI
Add new app and ad placement
Sign up or log in to DT Exchange Console.
Click on the Add App button to add your app.
Select your Platform, fill out the rest of the form, and click Add Placements.
Enter a name for the new placement in the field labeled Name your Placement and select your desired Placement Type from the dropdown list. Finally, click Save Placement.
App ID and Placement ID
Open the left navigation bar by hovering your mouse over it. Then click Apps from the left menu.
On the App Management page, take note of the App ID next to your app.
Select your app, navigate to the Placements tab, and click on the copy icon next to Placement Name. Take note of the Placement ID.
Publisher ID, Consumer Key and Consumer Secret
Click on your username from the left menu and select User Profile.
Take note of the Publisher ID, Consumer Key, and Consumer Secret as these are needed in the next step.
Step 2: Set up DT Exchange demand in AdMob UI
광고 단위에 대한 미디에이션 설정 구성
DT Exchange 를 광고 단위의 미디에이션 구성에 추가해야 합니다.
먼저 AdMob 계정에 로그인합니다. 그런 다음 미디에이션 탭으로 이동합니다. 수정할 기존 미디에이션 그룹이 있는 경우 해당 미디에이션 그룹의 이름을 클릭하여 수정한 후 DT Exchange 광고 소스로 추가로 건너뜁니다.
새 미디에이션 그룹을 만들려면 미디에이션 그룹 만들기를 선택합니다.
광고 형식과 플랫폼을 입력하고 계속을 클릭합니다.
미디에이션 그룹에 이름을 지정하고 타겟팅할 위치를 선택합니다. 미디에이션 그룹 상태를 사용으로 설정한 다음 광고 단위 추가를 클릭합니다.
이 미디에이션 그룹을 하나 이상의 기존AdMob 광고 단위와 연결합니다. 그런 다음 완료를 클릭합니다.
이제 광고 단위 카드가 선택한 광고 단위로 채워진 것을 볼 수 있습니다.
광고 소스로 DT Exchange 추가
광고 소스 섹션의 폭포식 구조 카드에서 광고 소스 추가를 선택합니다. 그런 다음 DT Exchange을 선택합니다.
DT Exchange를 선택하고 최적화 스위치를 사용 설정합니다. 이전 섹션에서 가져온 Publisher ID, Consumer Secret and Consumer Key을 입력하여DT Exchange에 대해 광고 소스 최적화를 설정합니다. 그런 다음DT Exchange 에 eCPM 값을 입력하고 계속을 클릭합니다.이미 DT Exchange에 대한 매핑이 있는 경우 해당 매핑을 선택할 수 있습니다. 그렇지 않으면 매핑 추가를 클릭합니다.
그런 다음 이전 섹션에서 얻은 Application ID and Placement ID를 입력합니다. 그런 다음 완료를 클릭합니다.
Add Fyber to GDPR and US state regulations ad partners list
GDPR 설정 및 미국 주 규정 설정 Fyber 를 AdMob UI의 GDPR 및 미국 주 규정 광고 파트너 목록에 추가합니다.
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.2.0")
implementation("com.google.ads.mediation:fyber:8.2.7.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.
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
Enable test ads
Make sure you register your test device for AdMob.
Verify test ads
To verify that you are receiving test ads from DT Exchange, enable single ad source testing in ad inspector using the DT Exchange (Waterfall) ad source(s).
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 AdMob 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
Next version:
- Pass MobileAds version to DT Exchange SDK.
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
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.
- 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.