排解廣告單元問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
啟動廣告檢查器後,您會看到廣告檢查器到達網頁。
這個頁面會列出 Ad Manager 使用者介面中,與 Ad Manager 應用程式 ID 相關聯,且已設定出價或中介服務的廣告單元。如果應用程式在工作階段期間向其他廣告單元請求廣告,廣告檢查器就會顯示這些廣告單元。

必要條件
繼續操作前,請先完成下列事項:
- 完成「必要條件」中的所有項目,建立 Ad Manager 帳戶、設定測試裝置、初始化 Google Mobile Ads SDK,並安裝最新版本。
- 啟動廣告檢查器。
查看廣告單元的刊登序列詳細資料
在「廣告單元」分頁中,輕觸廣告單元即可查看 SDK 請求記錄。SDK 請求記錄會提供廣告請求的刊登序列詳細資料,例如廣告供應時間、供應廣告的廣告來源,或刊登序列結束時未供應廣告。
如要顯示要求的瀑布圖結果,以及錯誤和延遲時間,請使用 keyboard_arrow_down 展開詳細資料清單。
如果是第三方廣告來源,廣告來源會直接傳送錯誤訊息。
如需更多資訊,請洽詢第三方廣告來源。
查看廣告單元的出價詳細資料
在 SDK 請求記錄中,您可以查看廣告請求中呼叫的出價廣告來源。
如要查看出價競價中每個廣告來源的詳細資料,請輕觸 more_vert 並按一下「查看所有出價者」:

出價結果會依據可採取行動的程度排序,由高到低如下:
標籤 |
說明 |
韓元 |
贏得競價的廣告來源。 |
發現問題
|
有問題的廣告來源。
|
未傳回廣告
|
未傳回廣告或未出價的廣告來源。
請參閱廣告來源的整合文件,或直接與第三方廣告來源聯絡。 |
提交的出價
|
提交出價但輸掉出價競價的廣告來源。 |

中介服務瀑布流是多個收益群組爭奪相同廣告空間的結果。最多可為單一收益群組新增十個第三方收益夥伴,包括出價收益夥伴和行動應用程式廣告中介服務收益夥伴。
排解廣告單元問題
如要排解廣告單元問題,請檢查廣告請求和回應,找出失敗原因,或將廣告請求和回應分享給支援團隊。
操作步驟如下:
- 在「SDK 請求記錄」中,輕觸「更多」圖示 more_vert 。系統隨即會顯示選項對話方塊。
- 輕觸「分享廣告請求和回應」,即可匯出完整的廣告請求和回應。
此外,您還可以查看第三方出價參數。在選項對話方塊中,輕觸「第三方出價參數」。這個選項會提供詳細資料,說明哪些第三方出價參數可能存在問題,並協助您排解應用程式問題,或驗證廣告來源是否正在收集信號。
Android
|
iOS
|
如果遇到「未傳回任何廣告」問題,請複製買方產生的資料,並提供給廣告來源尋求協助。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-31 (世界標準時間)。
[null,null,["上次更新時間:2025-08-31 (世界標準時間)。"],[],[],null,["# Troubleshoot ad units\n\nSelect platform: [Android](/ad-manager/mobile-ads-sdk/android/ad-inspector/troubleshoot-ad-units \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/ad-inspector/troubleshoot-ad-units \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/ad-inspector/troubleshoot-ad-units \"View this page for the Unity platform docs.\") [Flutter](/ad-manager/mobile-ads-sdk/flutter/ad-inspector/troubleshoot-ad-units \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\nAfter you launch ad inspector, you see the ad inspector landing page.\n\nThis page contains a list of your ad units in the Ad Manager UI\nassociated with your Ad Manager app ID\nthat have bidding or mediation\nconfigurations . If the app requests ads from other ad units during\na session, ad inspector displays these ad units.\n\nPrerequisites\n-------------\n\nBefore you continue, do the following:\n\n- Complete all items in the initial [Prerequisites](/ad-manager/mobile-ads-sdk/flutter/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/flutter/ad-inspector/launch-ad-inspector).\n\nView waterfall details for an ad unit\n-------------------------------------\n\nIn the **Ad Units** tab, tap on an ad unit to view its SDK request log. The\nSDK request log shares details about the waterfall from the ad request, such\nas when the ad filled, which ad source filled, or if the waterfall ended\nwithout a fill.\n\n\u003cbr /\u003e\n\nTo show the results of the waterfall for a request, along with error and\nlatency, expand the list of details using\nkeyboard_arrow_down.\n\nFor third-party ad sources, an ad source sends the error message directly.\nIf you want more information, consult your third-party ad source.\n\nView bidding details for an ad unit\n-----------------------------------\n\nIn **SDK request log** , you see the bidding ad sources called in an ad request.\nTo view the details of each ad source in the bidding auction, tap\nmore_vert and click\n**View all bidders**:\n\n\u003cbr /\u003e\n\nThe bidding results are sorted from most to least actionable, as follows:\n\n| **Label** | **Description** |\n|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Won** | The ad source that won the auction. |\n| **Issue found** | The ad sources with issues. |\n| **No ad returned** | Ad sources with no returned ads, or did not bid. Refer to the ad source's integration documentation, or contact the third-party ad source directly. |\n| **Submitted bid** | Ad sources that submitted a bid but lost the bidding auction. |\n\nA mediation waterfall is the result of multiple yield groups competing for the\nsame inventory. You can add up to ten third-party yield partners to a single\nyield group, including both bidding yield partners and mediation for mobile\napps yield partners.\n\nTroubleshoot an ad unit\n-----------------------\n\nTo troubleshoot ad units, review the ad request and response to identify a\nfailure, or share the ad request and response with support.\nComplete the following steps:\n\n1. In **SDK request log** , tap more_vert . An options dialog appears.\n2. Tap **Share ad request and response** to export the full ad request and response.\n\n| **Note:** You can export the ad response only after you link your [Android](/ad-manager/mobile-ads-sdk/android/debug#link_your_device) or [iOS](/ad-manager/mobile-ads-sdk/ios/debug#link_your_device) device through debug options menu.\n\n\u003cbr /\u003e\n\nAdditionally, you can view third-party bidding parameters. In the options\ndialog, tap **Third-party bidding parameter**. This option provides details\nabout which third-party bidding parameters might present issues, and helps you\ntroubleshoot your app or validate an ad source is collecting signals.\n\n\u003cbr /\u003e\n\n|---------|-----|\n| Android | iOS |\n\n\u003cbr /\u003e\n\n\nIf you encounter a **No ad returned** issue, copy the buyer generated data and\nshare with the ad sources for assistance."]]