Share your feedback and help shape the Google Mobile Ads SDK roadmap. Take the Google Mobile Ads SDK Annual Survey for 2023 before it closes on May 5th, 2023.

Integrate DT Exchange with Mediation

Stay organized with collections Save and categorize content based on your preferences.

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 a Unity app.

Supported integrations and ad formats

The AdMob mediation adapter for DT Exchange has the following capabilities:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded

Requirements

  • Unity 4 or higher
  • Latest Google Mobile Ads SDK
  • To deploy on Android
    • Android API level 19 or higher
  • To deploy on iOS
    • iOS deployment target of 10.0 or higher
  • A working Unity project configured with Google Mobile Ads SDK. See Get Started for details.

Step 1: Set up DT Exchange

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.

Manage Apps

Select a platform under Platform, fill out the rest of the form, and click Add Placements.

Android

iOS

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.

Setup

App ID and Placement ID

Open up the left navigation bar by hovering your mouse over it. Then click Apps from the left menu.

Menu

On the App Management page, take note of the App ID next to your app.

App ID

Select your app and navigate to the Placements tab, and click on the copy icon next to Placement Name. Take note of the Placement ID.

Placement ID

Publisher ID, Consumer Key and Consumer Secret

Click on your username from the left menu and select User Profile.

User Profile Menu

Take note of the Publisher ID, Consumer Key, and Consumer Secret as these are needed in the next step.

User Profile

Step 2: Configure mediation settings for your AdMob ad unit

You need to add DT Exchange to the mediation configuration for your ad unit.

If you're deploying your Unity app to both Android and iOS, you need two AdMob ad units, one for each platform.

Android

First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it and skip ahead to Add DT Exchange as an ad source.

To create a new mediation group, select Create Mediation Group.

AdMob mediation tab

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and click Add Ad Units.

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

You should now see the ad units card populated with the ad units you selected.

iOS

First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add DT Exchange as an ad source.

To create a new mediation group, select Create Mediation Group.

AdMob mediation tab

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and then click Add Ad Units.

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

You should now see the ad units card populated with the ad units you selected.

Add DT Exchange as an ad source

In the Waterfall card, select Add Ad Source.

Select DT Exchange and it should take you to Add ad source: DT Exchange

Ad source

Enable the Optimize switch. Then, enter the Publisher ID, Consumer Key, and Consumer Secret obtained in the previous section. Review and check the Authorization checkbox to set up ad source optimization for DT Exchange. Enter an eCPM value for DT Exchange and click Continue.

Ad source

Enter the Application ID and Placement ID, obtained from the previous step, and click Done.

Android

iOS

Rewarded ads

In the settings for your rewarded ad unit, provide values for the reward amount and reward type. To provide the same reward to the user no matter which ad network is served, select the Apply to all networks in Mediation groups box.

Rewarded

If you don't apply this setting, the DT Exchange adapter passes back the reward specified in the DT Exchange dashboard when creating the placement.

For more information on setting reward values for AdMob ad units, see Create an ad unit.

Step 3: Import the DT Exchange SDK and adapter

Download the latest version of Google Mobile Ads mediation plugin for DT Exchange from the download link in the Changelog and extract GoogleMobileAdsFyberMediation.unitypackage from the zip file.

In your Unity project editor, select Assets > Import Package > Custom Package and find the GoogleMobileAdsFyberMediation.unitypackage file you downloaded. Make sure all the files are selected and click Import.

Then, select Assets > Play Services Resolver > Android Resolver > Force Resolve. The Unity Play Services Resolver library will perform dependency resolution from scratch and copy the declared dependencies into the Assets/Plugins/Android directory of your Unity app.

Optional steps

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.

The section below shows you how to enable or disable personalized ads for DT Exchange.

The Google Mobile Ads mediation plugin for DT Exchange version 1.1.0 added the Fyber class with the SetGDPRRequired() and SetGDPRConsentString() methods, letting you pass consent information to DT Exchange manually. The following sample code demonstrates how to pass these parameters to the DT Exchange adapter:

using GoogleMobileAds.Api.Mediation.Fyber;
// ...

Fyber.SetGDPRConsent(true);
Fyber.SetGDPRConsentString("myGDPRConsentString");

Visit DT Exchange's GDPR article for more information and the values that can be provided in the method.

Add DT Exchange to GDPR ad partners list

Follow the steps in GDPR settings to add DT Exchange to the GDPR ad partners list in the AdMob UI.

CCPA

The California Consumer Privacy Act (CCPA) requires giving California state residents 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 CCPA preparation 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 with CCPA.

The Google Mobile Ads mediation plugin for DT Exchange version 3.1.1 added the Fyber class with the SetCCPAString() method, letting you pass consent information to DT Exchange manually. The following sample code demonstrates how to pass these parameters to the DT Exchange adapter:

using GoogleMobileAds.Api.Mediation.Fyber;
// ...

Fyber.SetCCPAString("myCCPAConsentString");

// You can also clear CCPA consent information using the following method:
Fyber.ClearCCPAString();

Visit DT Exchange's CCPA Open Source article for more information and the values that can be provided in the method.

Error codes

If the adapter fails to receive an ad from DT Exchange, publishers can check the underlying error from the ad response using ResponseInfo under the following class:

Android

com.google.ads.mediation.fyber.FyberMediationAdapter

iOS

GADMediationAdapterFyber

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

Android

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.

iOS

Error code Reason
0-10 DT Exchange SDK returned an error. See documentation for more details.
101 DT Exchange server parameters configured in the AdMob UI are missing/invalid.
102 The requested ad size does not match a DT Exchange supported banner size.
103 Failed to show ad because ad object has already been used.
104 Failed to show DT Exchange ads due to ad not ready.
105 DT Exchange SDK returned an initialization error.

DT Exchange Unity Mediation Plugin Changelog

Version 3.1.4

Version 3.1.3

Version 3.1.2

Version 3.1.1

Version 3.1.0

Version 3.0.2

Version 3.0.1

Version 3.0.0

Version 2.0.0

Version 1.6.1

Version 1.6.0

Version 1.5.2

Version 1.5.1

Version 1.5.0

Version 1.4.0

Version 1.3.0

Version 1.2.3

Version 1.2.2

Version 1.2.1

Version 1.2.0

Version 1.1.0

Version 1.0.0