Integrate DT Exchange with AdMob Mediation

This guide shows you how to use Google Mobile Ads SDK for React Native 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 React Native app.

Supported integrations and ad formats

The React Native mediation adapter for DT Exchange has the following capabilities:

Integration
Bidding
Waterfall
Formats
App Open
Banner
Interstitial
Rewarded
Rewarded Interstitial
Native

Prerequisites

Before you continue, verify the following:

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 Add App.

Manage Apps

Choose your platform and placements, fill out the rest of the form, and then click Create App.

Android

iOS

Enter the names and select the types for your placements. Then, click Save Placement.

Setup

App ID and Placement ID

Hover over the left navigation bar to open it, then click App Management.

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

Select your app and navigate to the Placements tab. Take note of the Placement ID..

Placement ID

Publisher ID, Consumer Key and Consumer Secret

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

User Profile

Update your app-ads.txt

Authorized Sellers for Apps app-ads.txt is an IAB Tech Lab initiative that helps ensure your app ad inventory is only sold through channels you've identified as authorized. To prevent a significant loss in ad revenue, you'll need to implement an app-ads.txt file. If you haven't done so already, set up an app-ads.txt file for your app.

To implement app-ads.txt for DT Exchange, Add DT to your app-ads.txt file.

Step 2: Set up DT Exchange demand in AdMob UI

Configure mediation settings for your ad unit

Android

For instructions, see step 2 in the guide for Android.

iOS

For instructions, see step 2 in the guide for iOS.

Add DT Exchange to GDPR and US state regulations ad partners list

Follow the steps in European regulations settings and US state regulations settings to add DT Exchange (Fyber Monetization) to the European and US state regulations ad partners list in the AdMob UI.

Step 3: Import the DT Exchange SDK and adapter

In your project's root directory, install the Google Mobile Ads SDK for React Native mediation adapter for DT Exchange. Complete the following:

  1. Copy the Google Mobile Ads SDK for React Native adapter tar file from the gma-sdk-react-native/adapters/dt-exchange/ directory into your project's local_packages/ directory. If you don't have the adapters folder, see Prerequisites.

    mkdir -p local_packages
cp EXTRACT_DIR/gma-sdk-react-native/adapters/dt-exchange/gma-mediation-dtexchange-0.1.0.tgz local_packages/

    Replace EXTRACT_DIR with the path to the directory where you extracted the archive.

  2. Install the adapter package using your preferred package manager:

    npm

    npm install ./local_packages/gma-mediation-dtexchange-0.1.0.tgz

    yarn

    yarn add ./local_packages/gma-mediation-dtexchange-0.1.0.tgz

Step 4: Implement privacy settings on DT Exchange SDK

To comply with the Google EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA), the UK, and Switzerland, and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). You are responsible for verifying that consent is propagated to each ad source in your mediation chain.

DT Exchange React Native adapter version 0.1.0 and later supports passing GDPR consent signals from consent management platforms that integrate with IAB's Transparency and Consent Framework (TCF) to DT Exchange SDK. For more information, see Android and iOS GDPR documentation.

US states privacy laws

US 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 through a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The US 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.

The following sample code demonstrates how to pass consent information to the DT Exchange adapter manually:

import { DTExchangeMediation } from '@google/gma-mediation-dtexchange';
// ...

DTExchangeMediation.setUSPrivacyString('myUSPrivacyString');

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

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

Step 5: Add required code

Android

No additional code is required for DT Exchange integration.

iOS

SKAdNetwork integration

Follow DT Exchange's documentation to add the SKAdNetwork identifiers to your project's Info.plist file.

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 (Bidding) and DT Exchange (Waterfall) ad source(s).

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 SDK loaded an ad but returned an unexpected controller.
106 Ad is not ready to display.
107 Context is not an activity instance.
108 Ad failed to be displayed.
200-399 DT SDK returned an error. See code for more details.

iOS

Error code Reason
0-10 DT 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 SDK returned an initialization error.

Version 0.1.0

  • Initial release.