Cómo integrar DT Exchange con Mediación

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 iOS 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

  • iOS deployment target of 12.0 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

Cómo configurar la mediación para tu unidad de anuncios

Accede a tu cuenta de Ad Manager.

Navega a Publicación > Grupos de rendimiento y haz clic en el botón Nuevo grupo de rendimiento.

Ingresa un Nombre único para tu grupo de rendimiento, establece el Estado en Activo, selecciona el Formato del anuncio y establece el Tipo de inventario en Aplicación para dispositivos móviles. En la sección Segmentación > Inventario, selecciona la unidad de anuncios en Inventario y Aplicación para dispositivos móviles a la que deseas agregar la mediación.

Luego, haz clic en el botón Agregar socio de rendimiento.

Si ya tienes un socio de rendimiento paraDT Exchange, puedes seleccionarlo. De lo contrario, selecciona Crear un socio de rendimiento nuevo.

Selecciona DT Exchange como la Red de publicidad, ingresa un Nombre único y habilita la Mediación.

Activa Recopilación de datos automática y, luego, ingresa el Publisher ID, Consumer Secret and Consumer Key obtenido en la sección anterior.

Una vez que hayas seleccionado el Socio de rendimiento, elige Mediación del SDK para dispositivos móviles como el Tipo de integración, iOS como la Plataforma y Activo como el Estado. Ingresa elApplication ID and Placement ID obtenido en la sección anterior. Luego, ingresa un valor de CPM predeterminado.

Haz clic en Guardar en la parte inferior de la página cuando termines.

Add Fyber to GDPR and US state regulations ad partners list

Sigue los pasos que se indican en Configuración del GDPR y Configuración de las reglamentaciones estatales de EE.UU. para agregar Fyber a la lista de socios publicitarios de las reglamentaciones estatales de EE.UU. y el GDPR en la Ad Manager IU.

Step 3: Import the DT Exchange SDK and adapter

Add the following line to your project's Podfile:

pod 'GoogleMobileAdsMediationFyber'

From the command line run:

pod install --repo-update

Manual integration

  • Download the latest version of the DT Exchange SDK for iOS and link the following frameworks to your project:
    • IASDKCore.framework
    • IASDKMRAID.framework
    • IASDKVideo.framework
  • Download the latest version of the DT Exchange adapter from the download link in Changelog and link FyberAdapter.framework in your project.
  • Add the following frameworks to your project:
    • libxml2.2.tbd

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.

Swift

import IASDKCore
// ...

IASDKCore.sharedInstance().gdprConsent = IAGDPRConsentType.given
IASDKCore.sharedInstance().gdprConsentString = "myGdprConsentString"

Objective-C

#import <IASDKCore/IASDKCore.h>
// ...

[IASDKCore.sharedInstance setGDPRConsent:YES];
[IASDKCore.sharedInstance 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.

Swift

import IASDKCore
// ...

IASDKCore.sharedInstance().ccpaString = "myCCPAConsentString"

Objective-C

#import <IASDKCore/IASDKCore.h>
// ...

[IASDKCore.sharedInstance setCCPAString:@"myCCPAConsentString"];

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

SKAdNetwork integration

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

Step 6: Test your implementation

Habilitar anuncios de prueba

Asegúrate de registrar tu dispositivo de prueba en Ad Manager.

Cómo verificar los anuncios de prueba

Para verificar que recibes anuncios de prueba deDT Exchange, habilita las pruebas de fuentes de anuncios individuales en el inspector de anuncios mediante la DT Exchange (Waterfall) fuente de anuncios.

Optional steps

Network-specific parameters

The DT Exchange adapter supports additional request parameters that can be passed to the adapter using the GADMAdapterFyberExtras(). The adapter looks for the following keys in the bundle:

Request parameters and values
setUserData
The age, gender and zip code of the user.		 IAUserData
setMuteAudio Boolean. Mute or unmute video

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

Swift 

let userData = IAUserData.build({ builder in
  builder.age = 23
  builder.gender = IAUserGenderType.male
  builder.zipCode = "1234"
}];

let request = GADRequest()
let extras = GADMAdapterFyberExtras()
extras.userData = userData
extras.muteAudio = true
request.register(extras)

Objective-C 

IAUserData *userData = [IAUserData build:^(id<IAUserDataBuilder> _Nonnull builder) {
    builder.age = 23;
    builder.gender = IAUserGenderTypeMale;
    builder.zipCode = @"1234";
}];

GADRequest *request = [GADRequest request];
GADMAdapterFyberExtras *extras = [[GADMAdapterFyberExtras alloc] init];
extras.userData = userData;
extras.muteAudio = YES;
[request registerAdNetworkExtras:extras];

Consult the DT Exchange integration guide for more information.

Error codes

If the adapter fails to receive an ad from DT Exchange, you can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following class:

GADMediationAdapterFyber

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

Error code Reason
0-10 DT Exchange SDK returned an error. See documentation for more details.
101 DT Exchange server parameters configured in the Ad Manager 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 iOS Mediation Adapter Changelog

Version 8.3.1.0

  • Verified compatibility with DT Exchange SDK version 8.3.1.

Built and tested with:

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

Version 8.3.0.0

  • Verified compatibility with DT Exchange SDK version 8.3.0.

Built and tested with:

  • Google Mobile Ads SDK version 11.5.0.
  • DT Exchange SDK version 8.3.0.

Version 8.2.8.0

  • Verified compatibility with DT Exchange SDK version 8.2.8.

Built and tested with:

  • Google Mobile Ads SDK version 11.3.0.
  • DT Exchange SDK version 8.2.8.

Version 8.2.7.0

  • Verified compatibility with DT Exchange SDK version 8.2.7.

Built and tested with:

  • Google Mobile Ads SDK version 11.2.0.
  • DT Exchange SDK version 8.2.7.

Version 8.2.6.1

  • Added didFailToPresentWithError callbacks in rewarded ad.
  • Added IAAdDidExpire delegate method in interstitial and rewarded ads.
  • Now requires minimum iOS version 12.0.
  • Now requires Google Mobile Ads SDK version 11.0 or higher.
  • Included Info.plist in the frameworks within DTExchangeAdapter.xcframework.

Built and tested with:

  • Google Mobile Ads SDK version 11.0.1.
  • DT Exchange SDK version 8.2.6.

Version 8.2.6.0

  • Verified compatibility with DT Exchange SDK version 8.2.6.
  • Removed the deprecated willBackgroundApplication delegate methods from the banner and interstitial ad implementations.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • DT Exchange SDK version 8.2.6.

Version 8.2.5.0

  • Verified compatibility with DT Exchange SDK version 8.2.5.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • DT Exchange SDK version 8.2.5.

Version 8.2.4.0

  • Verified compatibility with DT Exchange SDK version 8.2.4.

Built and tested with:

  • Google Mobile Ads SDK version 10.9.0.
  • DT Exchange SDK version 8.2.4.

Version 8.2.3.0

  • Verified compatibility with DT Exchange SDK version 8.2.3.

Built and tested with:

  • Google Mobile Ads SDK version 10.7.0.
  • DT Exchange SDK version 8.2.3.

Version 8.2.2.0

  • Verified compatibility with DT Exchange SDK version 8.2.2.

Built and tested with:

  • Google Mobile Ads SDK version 10.5.0.
  • DT Exchange SDK version 8.2.2.

Version 8.2.1.0

  • Verified compatibility with DT Exchange SDK version 8.2.1.
  • Removed support of the armv7 architecture.
  • Now requires minimum iOS version 11.0.
  • Now requires Google Mobile Ads SDK version 10.4.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 10.4.0.
  • DT Exchange SDK version 8.2.1.

Version 8.2.0.0

  • Verified compatibility with DT Exchange SDK version 8.2.0.

Built and tested with:

  • Google Mobile Ads SDK version 10.2.0.
  • DT Exchange SDK version 8.2.0.

Version 8.1.9.1

  • Now requires Google Mobile Ads SDK version 10.0.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 10.0.0.
  • DT Exchange SDK version 8.1.9.

Version 8.1.9.0

  • Removed use of deprecated gender, birthday and location mediation APIs.
  • Verified compatibility with DT Exchange SDK version 8.1.9.

Built and tested with:

  • Google Mobile Ads SDK version 9.14.0.
  • DT Exchange SDK version 8.1.9.

Version 8.1.7.0

  • Verified compatibility with DT Exchange SDK version 8.1.7.
  • Adapter is rebranded to "DT Exchange".

Built and tested with:

  • Google Mobile Ads SDK version 9.13.0.
  • DT Exchange SDK version 8.1.7.

Version 8.1.6.0

  • Added support for passing muteAudio extra in GADMAdapterFyberExtras class.
  • Updated the adapter to use the didRewardUser API.
  • Now requires Google Mobile Ads SDK version 9.8.0 or higher.
  • Verified compatibility with Fyber Marketplace SDK version 8.1.6.

Built and tested with:

  • Google Mobile Ads SDK version 9.11.0.
  • Fyber Marketplace SDK version 8.1.6.

Version 8.1.5.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.5.

Built and tested with:

  • Google Mobile Ads SDK version 9.5.0.
  • Fyber Marketplace SDK version 8.1.5.

Version 8.1.4.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.4.
  • Added support for the arm64 simulator architecture.

Built and tested with:

  • Google Mobile Ads SDK version 9.1.0.
  • Fyber Marketplace SDK version 8.1.4.

Version 8.1.3.1

  • Verified compatibility with Google Mobile Ads SDK version 9.0.0.
  • Now requires Google Mobile Ads SDK version 9.0.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 9.0.0.
  • Fyber Marketplace SDK version 8.1.3.

Version 8.1.3.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.3.

Built and tested with:

  • Google Mobile Ads SDK version 8.13.0.
  • Fyber Marketplace SDK version 8.1.3.

Version 8.1.2.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.2.

Built and tested with:

  • Google Mobile Ads SDK version 8.13.0.
  • Fyber Marketplace SDK version 8.1.2.

Version 8.1.1.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.1.

Built and tested with:

  • Google Mobile Ads SDK version 8.12.0.
  • Fyber Marketplace SDK version 8.1.1.

Version 8.1.0.0

  • Verified compatibility with Fyber Marketplace SDK version 8.1.0.

Built and tested with:

  • Google Mobile Ads SDK version 8.12.0.
  • Fyber Marketplace SDK version 8.1.0.

Version 8.0.0.0

  • Verified compatibility with Fyber Marketplace SDK version 8.0.0.

Built and tested with:

  • Google Mobile Ads SDK version 8.12.0.
  • Fyber Marketplace SDK version 8.0.0.

Version 7.9.0.0

  • Verified compatibility with Fyber Marketplace SDK version 7.9.0.

Built and tested with:

  • Google Mobile Ads SDK version 8.11.0.
  • Fyber Marketplace SDK version 7.9.0.

Version 7.8.9.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.9.

Built and tested with:

  • Google Mobile Ads SDK version 8.10.0.
  • Fyber Marketplace SDK version 7.8.9.

Version 7.8.8.1

  • Moved ad event didEndVideo to rewarded ad callback IAAdDidReward.

Built and tested with:

  • Google Mobile Ads SDK version 8.9.0.
  • Fyber Marketplace SDK version 7.8.8.

Version 7.8.8.0

  • Now requires minimum iOS version 10.0.
  • Verified compatibility with Fyber Marketplace SDK version 7.8.8.

Built and tested with:

  • Google Mobile Ads SDK version 8.9.0.
  • Fyber Marketplace SDK version 7.8.8.

Version 7.8.7.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.7.

Built and tested with:

  • Google Mobile Ads SDK version 8.8.0.
  • Fyber Marketplace SDK version 7.8.7.

Version 7.8.6.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.6.

Built and tested with:

  • Google Mobile Ads SDK version 8.5.0.
  • Fyber Marketplace SDK version 7.8.6.

Version 7.8.5.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.5.
  • Now requires building against Xcode 12.5 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 8.5.0.
  • Fyber Marketplace SDK version 7.8.5.

Version 7.8.1.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.1.
  • Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher.
  • Added standardized adapter error codes and messages.
  • Updated the adapter to use the .xcframework format.

Built and tested with:

  • Google Mobile Ads SDK version 8.0.0.
  • Fyber Marketplace SDK version 7.8.1.

Version 7.8.0.0

  • Verified compatibility with Fyber Marketplace SDK version 7.8.0.

Built and tested with:

  • Google Mobile Ads SDK version 7.69.0.
  • Fyber Marketplace SDK version 7.8.0.

Version 7.7.3.0

  • Verified compatibility with Fyber Marketplace SDK version 7.7.3.
  • Now requires Google Mobile Ads SDK version 7.69.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 7.69.0.
  • Fyber Marketplace SDK version 7.7.3.

Version 7.7.2.0

  • Verified compatibility with Fyber Marketplace SDK version 7.7.2.
  • Now requires Google Mobile Ads SDK version 7.67.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 7.67.0.
  • Fyber Marketplace SDK version 7.7.2.

Version 7.7.1.0

  • Verified compatibility with Fyber Marketplace SDK version 7.7.1.
  • Now requires Google Mobile Ads SDK version 7.66.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 7.66.0.
  • Fyber Marketplace SDK version 7.7.1.

Version 7.6.4.0

  • Verified compatibility with Fyber Marketplace SDK version 7.6.4.
  • Now requires Google Mobile Ads SDK version 7.65.0 or higher.
  • Added GADMAdapterFyberExtras class, enabling publishers to pass keywords and userData to Fyber Marketplace SDK.

Built and tested with:

  • Google Mobile Ads SDK version 7.65.0.
  • Fyber Marketplace SDK version 7.6.4.

Version 7.6.3.0

  • Verified compatibility with Fyber Marketplace SDK version 7.6.3.

Built and tested with:

  • Google Mobile Ads SDK version 7.64.0.
  • Fyber Marketplace SDK version 7.6.3.

Version 7.6.2.0

  • Verified compatibility with Fyber Marketplace SDK version 7.6.2.
  • Now requires Google Mobile Ads SDK version 7.64.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 7.64.0.
  • Fyber Marketplace SDK version 7.6.2.

Version 7.6.0.0

  • Verified compatibility with Fyber Marketplace SDK version 7.6.0.
  • Now requires Google Mobile Ads SDK version 7.62.0 or higher.
  • Updated the adapter to support inline adaptive banner requests.
  • Added support for rewarded HTML.
  • Added new reward callback: IAAdDidReward (for both rewarded video and rewarded HTML). IAVideoCompleted is no longer used for rewarding.

Built and tested with:

  • Google Mobile Ads SDK version 7.62.0.
  • Fyber Marketplace SDK version 7.6.0.

Version 7.5.6.1

  • Temporarily removed Fyber Marketplace SDK-specific logging.

Built and tested with:

  • Google Mobile Ads SDK version 7.60.0.
  • Fyber Marketplace SDK version 7.5.6.

Version 7.5.6.0

  • Verified compatibility with Fyber Marketplace SDK version 7.5.6.
  • Updated the minimum required Google Mobile Ads SDK version to 7.60.0.

Built and tested with:

  • Google Mobile Ads SDK version 7.60.0.
  • Fyber Marketplace SDK version 7.5.6.

Version 7.5.5.0

  • Verified compatibility with Fyber Marketplace SDK version 7.5.5.
  • Updated the minimum required Google Mobile Ads SDK version to 7.59.0.

Built and tested with:

  • Google Mobile Ads SDK version 7.59.0.
  • Fyber Marketplace SDK version 7.5.5 .

Version 7.5.4.0

  • Verified compatibility with Fyber Marketplace SDK version 7.5.4.
  • Removed support for the i386 architecture.

Built and tested with:

  • Google Mobile Ads SDK version 7.57.0.
  • Fyber Marketplace SDK version 7.5.4.

Version 7.5.3.0

  • Verified compatibility with Fyber Marketplace SDK version 7.5.3.

Built and tested with:

  • Google Mobile Ads SDK version 7.55.0.
  • Fyber Marketplace SDK version 7.5.3.

Version 7.5.1.0

  • Verified compatibility with Fyber Marketplace SDK version 7.5.1.
  • Fixed a crash that occurred when initializing the Fyber SDK.

Built and tested with:

  • Google Mobile Ads SDK version 7.55.0.
  • Fyber Marketplace SDK version 7.5.1.

Version 7.5.0.0 (Deprecated)

  • This version has been removed. Please use version 7.5.1.0 or higher.
  • Verified compatibility with Fyber Marketplace SDK version 7.5.0.
  • Adapter will now initialize the Fyber SDK before making an ad request if the Fyber SDK has not been initialized yet.

Built and tested with:

  • Google Mobile Ads SDK version 7.53.0.
  • Fyber Marketplace SDK version 7.5.0.

Version 7.4.0.0

  • Initial release!
  • Added support for banner, interstitial and rewarded ad formats.

Built and tested with:

  • Google Mobile Ads SDK version 7.52.0.
  • Fyber Marketplace SDK version 7.4.0.