驗證轉接程式整合結果
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁說明如何查看和驗證與廣告來源相關聯的轉接程式。
必要條件
繼續操作前,請先執行下列工作:
- 完成初始「必要條件」列出的所有項目:建立 Ad Manager 帳戶、設定測試裝置、初始化 Google Mobile Ads SDK,以及安裝最新版本。
- 啟動廣告檢查器。
您可以查看與應用程式中所設定廣告來源相關聯的所有轉接程式清單。如要查看清單,請完成下列步驟:
- 在「廣告檢查器」頁面中,按一下「轉接程式」。
展開資訊卡,即可查看初始化狀態,以及轉接程式和第三方 SDK 版本。

如果找不到轉接程式或初始化失敗,請參閱「廣告檢查器 (Beta 版)」一文。
查看自訂事件轉接程式
您也可以查看自訂事件轉接程式。使用自訂事件,即可為 Ad Manager 不支援的廣告來源,設定刊登序列中介服務。在轉接程式清單中,自訂事件會依不重複類別名稱區分。除了提供類別名稱,廣告檢查器也會顯示在 Ad Manager 使用者介面中,指派給這些自訂事件的標籤。如要進一步瞭解自訂事件,請參閱「設定」。
如果自訂事件的導入時間較早 (例如在 Google Mobile Ads SDK 9.0.0 版之前),可能會使用不支援初始化的已淘汰子類別,並在廣告檢查器中傳回「發現問題」。如果看見「Issue found」警告,而自訂事件整合功能運作正常,請檢查應用程式是否使用已淘汰的介面,並將該介面替換為轉接程式類別。詳情請參閱「GADMediationAdapter
」。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-25 (世界標準時間)。
[null,null,["上次更新時間:2025-08-25 (世界標準時間)。"],[],[],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/ad-inspector/verify-adapter-integrations \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/ad-inspector/verify-adapter-integrations \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/ad-inspector/verify-adapter-integrations \"View this page for the Unity platform docs.\") [Flutter](/ad-manager/mobile-ads-sdk/flutter/ad-inspector/verify-adapter-integrations \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\nThis page covers steps on viewing and verifying adapters associated with\nyour ad sources.\n\nPrerequisites\n\nBefore you continue, do the following:\n\n- Complete all items in the initial [Prerequisites](/ad-manager/mobile-ads-sdk/ios/ad-inspector#prerequisites) to create an Ad Manager account, set your test device, initialize Google Mobile Ads SDK, and install the latest version.\n- [Launch ad inspector](/ad-manager/mobile-ads-sdk/ios/ad-inspector/launch-ad-inspector).\n\nYou can view a list of all adapters associated with the ad sources configured\nin your app. To view the list, complete the following steps:\n\n1. In the **Ad inspector** page, click **Adapters**.\n2. Expand the cards to view initialization statuses and adapter and\n third-party SDK versions.\n\n \u003cbr /\u003e\n\nIf the adapter isn't found or fails to initialize, see\n\n[Ad inspector (Beta)](//support.google.com/admanager/answer/7180401#ad-inspector).\n\n\nView custom event adapters\n\nYou can also view custom event adapters. Custom events lets you set up\nwaterfall mediation for an ad source that Ad Manager doesn't support.\nIn the adapter list, Custom events are distinct by unique class names. In\naddition to providing the class name, ad inspector also displays labels\nassigned to those custom events in the Ad Manager UI. For more details\non custom events, see\n\n[Setup](/ad-manager/mobile-ads-sdk/ios/custom-events/overview).\n\n\nEarlier implementations of custom events, such as prior to the Google Mobile Ads SDK\nversion\n\n9.0.0,\n\ncan use deprecated subclasses that don't support\ninitialization and return **Issue found** within ad inspector. If you see the\n**Issue found** warning, and your custom event integration works as expected,\ncheck if your app is using a deprecated interface and replace the interface with\nan adapter class. For details, see\n[GADMediationAdapter](/ad-manager/mobile-ads-sdk/ios/api/reference/Protocols/GADMediationAdapter)."]]