将 DT Exchange 与中介集成

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

  • Latest Google Mobile Ads SDK
  • Flutter 3.7.0 or higher
  • To deploy on Android
    • Android API level 21 or higher
  • To deploy on iOS
    • iOS deployment target of 12.0 or higher
  • A working Flutter project configured with Google Mobile Ads SDK. See Get Started for details.
  • 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.

Manage Apps

Select your 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 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, 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: Set up DT Exchange demand in AdMob UI

为广告单元配置中介设置

Android

如需了解相关说明,请参阅 Android 指南中的第 2 步。

iOS

如需了解相关说明,请参阅 iOS 指南中的第 2 步。

Add Fyber to GDPR and US state regulations ad partners list

按照 GDPR 设置美国州级法规设置 中的步骤,将 Fyber 添加到 AdMob 界面中的 GDPR 和美国州级法规广告合作伙伴列表中。

Step 3: Import the DT Exchange SDK and adapter

通过 pub.dev 进行集成

将以下依赖项与最新版本的 DT Exchange 软件包的 pubspec.yaml 文件:

dependencies:
  gma_mediation_dtexchange: ^1.0.0

手动集成

下载针对以下指标的最新版 Google 移动广告中介插件: DT Exchange, 将下载的文件解压缩,然后添加提取的插件文件夹 (及其内容)添加到您的 Flutter 项目中。然后,在 pubspec.yaml 文件,通过添加以下依赖项:

dependencies:
  gma_mediation_dtexchange:
    path: path/to/local/package

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.

The Google Mobile Ads mediation plugin for DT Exchange does not support passing consent information to the DT Exchange SDK.

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.

The Google Mobile Ads mediation plugin for DT Exchange does not support passing consent information to the DT Exchange SDK.

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

启用测试广告

请务必为 AdMob。

验证测试广告

如需验证您收到的是来自DT Exchange的测试广告,请使用相应广告来源在广告检查器中启用单一广告来源测试DT Exchange (Waterfall)

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 Flutter Mediation Adapter Changelog

1.0.0

  • Initial release.
  • Verified compatibility with DT Exchange Android adapter version 8.2.7.0.
  • Verified compatibility with DT Exchange iOS adapter version 8.2.8.0.
  • Built and tested with the Google Mobile Ads Flutter Plugin version 5.1.0.