Skip to main content

Digital Turbine

This guide is intended for publishers who want to use the Google Mobile Ads SDK to load and display ads from Digital Turbine (DT Exchange / Fyber) via mediation. 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 AIR app.

Step 1: Set up configurations in DT Exchange UI​

https://developers.google.com/admob/android/mediation/dt-exchange#step_1

Step 2: Set up DT Exchange demand in AdMob UI​

https://developers.google.com/admob/android/mediation/dt-exchange#step-2

Step 3: Import the DigitalTurbine mediation ANE​

The simplest way to install and manage your AIR native extensions and libraries is to use the AIR Package Manager (apm). We highly recommend using apm, as it will handle downloading all required dependencies and manage your application descriptor (Android manifest additions, iOS info additions etc).

However you can choose to install it manually, as you would have done in the past.

Add the Extension​

info

Note: All of the commands below should be run in a terminal / command prompt in the root directory of your application, generally the level above your source directory.

If you don't have an APM project setup, expand the guide below to setup an APM project before installing the extension.

Setup APM

Install APM​

If you haven't installed apm follow the install guide on airsdk.dev.

Setup an APM project​

You will need an APM project for your application.

There are many ways to do this and for more options see the APM documentation. Here we will just initialise a new empty project:

apm init

Check your github token​

We use github to secure our extensions so you must have created a github personal access token and configured apm to use it.

To do this create a token using this guide from github and then set it in your apm config using:

apm config set github_token ghp_XXXXXXXXXXXXXXXXXXXXXXXXXXXX

If you don't do this correctly you may find the install will fail.

Install the extension​

Install the extension by running: 

apm install com.distriqt.admob.DigitalTurbine

This will download and install the extension, required assets, and all dependencies.

Once complete apm will have created something like the following file structure: 

.
|____ assets
| |____ android 
| | |____ [android assets]
| |____ ios 
| | |____ Frameworks
| | | |____ [dynamic frameworks]
|____ ane
| |____ com.distriqt.admob.DigitalTurbine.ane   # DigitalTurbine AdMob mediation extension
| |____ [dependencies]
|____ apm_packages                  # cache directory - ignore
|____ project.apm                   # apm project file

  • Add the ane directory to your IDE. See the tutorials located here on adding an extension to your IDE.

  • You may have an assets directory that contains required assets for the installed extensions. You must add the files in the assets/android folder to the root of your Android application package and the assets/ios folder to the root of your iOS application package (contains the Frameworks folder with required dynamic frameworks). If these folders don't exist there are no required assets for that platform.

info

We suggest you use the locations directly in your builds rather than copying the files elsewhere. The reason for this is if you ever go to update the extensions using apm that these updates will be pulled into your build automatically.

Application Descriptor​

Updating your application descriptor will insert the required extensionID's and generate the manifest and info additions for your application.

You update your application descriptor by running:

apm generate app-descriptor src/MyApp-app.xml

Change the path (src/MyApp-app.xml) to point to your application descriptor.

caution

This will modify your application descriptor replacing the manifest additions and info additions with the ones generated from apm.

You should backup your application descriptor before running this command to ensure you don't lose any information.

If you need to insert custom data into these sections see the guides for Android and iOS

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.

DigitalTurbine.instance.setGDPRConsent( true );
DigitalTurbine.instance.setGDPRConsentString( "myGdprConsentString" );

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.

DigitalTurbine.instance.setUSPrivacyString( "myUsPrivacyString" );

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

Further information​

See the Google Mediation guide:

https://developers.google.com/admob/android/mediation/dt-exchange