整合 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 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

  • Latest Google Mobile Ads SDK
  • Unity 4 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 Unity 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

新增應用程式和廣告刊登位置

註冊或登入 DT Exchange 主控台。

按一下「Add App」按鈕來新增應用程式。

管理應用程式

選取您的「平台」，填寫表單的其他部分，然後按一下「新增刊登位置」。

Android

iOS

在「為刊登位置命名」欄位中，輸入新刊登位置的名稱，然後從下拉式清單中選取所需的「刊登位置類型」。最後按一下「Save Placement」。

設定

應用程式 ID 和刊登位置 ID

將滑鼠遊標懸停在左側導覽列上，開啟左側導覽列。按一下左選單中的「應用程式」。

選單

在「應用程式管理」頁面上，記下應用程式旁邊的應用程式 ID。

應用程式 ID

選取您的應用程式，前往「刊登位置」分頁，再按一下「刊登位置名稱」旁的複製圖示。記下「刊登位置 ID」。

刊登位置 ID

發布商 ID、用戶端金鑰和用戶端密鑰

點選左選單中的使用者名稱，然後選取「使用者個人資料」。

使用者設定檔選單

請記下「Publisher ID」(發布者 ID)、「Consumer Key」(用戶端金鑰) 和「Consumer Secret」(用戶端密鑰)，因為這是下個步驟的必要步驟。

使用者個人資料

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 設定 和 美國州級法規設定 ，在 AdMob UI 和美國州級法規廣告合作夥伴清單中新增 Fyber。

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.

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.

This section shows 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.

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

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 Unity Mediation Plugin Changelog

Version Next

  • Renamed DummyClient to PlaceholderClient.

Version 3.2.1

Version 3.2.0

Version 3.1.12

Version 3.1.11

Version 3.1.10

Version 3.1.8

Version 3.1.7

Version 3.1.6

Version 3.1.5

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