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 App（添加应用）按钮添加您的应用。
选择您的平台，填写表单的其余部分，然后点击添加展示位置。
Android
iOS
在标记为 Name your Placement 的字段中输入新展示位置的名称，然后从下拉列表中选择所需的展示位置类型。最后，点击 Save Placement（保存展示位置）。
应用 ID 和展示位置 ID
将鼠标悬停在左侧导航栏上，将其打开。然后，点击左侧菜单中的应用。
在应用管理页面上，记下您应用旁边的应用 ID。
选择您的应用，前往展示位置标签页，然后点击展示位置名称旁边的复制图标。记下展示位置 ID。
发布商 ID、使用方键值和使用方密钥
点击左侧菜单中的用户名，然后选择用户个人资料。
记下发布商 ID、使用方键值和使用方密钥，因为下一步中会用到这些信息。
Step 2: Set up DT Exchange demand in AdMob UI
調整廣告單元中介服務設定
Add Fyber to GDPR and US state regulations ad partners list
請按照 GDPR 設定 和 美國州級法規設定 ，在 AdMob UI 和美國州級法規廣告合作夥伴清單中新增 Fyber。
Step 3: Import the DT Exchange SDK and adapter
透過 pub.dev 整合
使用最新版本的
DT Exchange 套件中的 SDK 和轉接程式
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
EU Consent and GDPR
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.