排查广告单元问题
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
启动广告检查器后,您会看到广告检查器着陆页。
此页面包含 AdMob 界面中与您的 AdMob 应用 ID 相关联的广告单元列表。如果应用在会话期间从其他广告单元请求广告,广告检查器会显示这些广告单元。

前提条件
在继续之前,请执行以下操作:
- 完成初始前提条件中的所有项目,以创建 AdMob 账号、设置测试设备、初始化 Google 移动广告 SDK 并安装最新版本。
- 启动广告检查器。
查看广告单元的瀑布流详细信息
在 Ad Units(广告单元)标签页中,点按某个广告单元,即可查看其 SDK 请求日志。SDK 请求日志会显示有关广告请求的瀑布流的详细信息,例如广告填充时间、填充广告的广告来源,或者瀑布流是否以无任何广告填充而结束。
如需显示请求的瀑布流结果以及错误和延迟,请使用 keyboard_arrow_down 展开详细信息列表。
对于第三方广告来源,错误消息会直接从广告来源发送。如需了解详情,请咨询您的第三方广告来源。
查看广告单元的出价详细信息
在 SDK 请求日志中,您可以看到广告请求中调用的出价广告来源。如需查看出价竞价中每个广告来源的详细信息,请点按 more_vert ,然后点击查看所有出价方:
出价结果按可操作性由高到低排序,如下所示:
标签 |
说明 |
赢得 |
在竞价中胜出的广告来源。 |
发现了问题
|
存在问题的广告来源。
如需了解问题排查步骤,请参阅出价常见问题解答。 |
未返回广告
|
未返回广告或未出价的广告来源。
请参阅广告来源的集成文档,或直接与第三方广告来源联系。 |
已提交的出价
|
提交了出价但出价竞价失败的广告来源。 |

系统会根据赢得竞价的广告来源的有效每千次展示费用值将其放置在瀑布流链中。如需详细了解使用瀑布流的出价,请参阅:
排查广告单元问题
如需排查广告单元问题,请查看广告请求和响应以找出失败原因,或与支持团队分享广告请求和响应。
请完成以下步骤:
- 在 SDK 请求日志中,点按 more_vert 。系统会显示一个选项对话框。
- 点按共享广告请求和响应,以导出完整的广告请求和响应。
此外,您还可以查看第三方出价参数。在选项对话框中,点按第三方出价参数。此选项可提供有关哪些第三方出价参数可能存在问题的详细信息,并帮助您排查应用问题或验证广告来源是否正在收集信号。
Android
|
iOS
|
如果您遇到未返回广告问题,请复制买方生成的数据并与广告来源分享,以寻求帮助。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):2025-08-31。"],[],[],null,["# Troubleshoot ad units\n\nSelect platform: [Android](/admob/android/ad-inspector/troubleshoot-ad-units \"View this page for the Android platform docs.\") [iOS](/admob/ios/ad-inspector/troubleshoot-ad-units \"View this page for the iOS platform docs.\") [Unity](/admob/unity/ad-inspector/troubleshoot-ad-units \"View this page for the Unity platform docs.\") [Flutter](/admob/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 AdMob UI\nassociated with your AdMob app ID\n. 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](/admob/flutter/ad-inspector#prerequisites) to create an AdMob account, set your test device, initialize Google Mobile Ads SDK , and install the latest version.\n- [Launch ad inspector](/admob/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\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\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. For troubleshooting steps, see [Bidding FAQ](//support.google.com/admob/answer/9360574#biddingissue&zippy=%2Ci-found-an-issue-when-testing-in-ad-inspector-what-does-this-mean). |\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\nThe ad source that won the auction is placed in the waterfall chain according\nto their eCPM value. For details on bidding with waterfall,\nsee:\n\n- [Example 2: Bidding and waterfall ad sources in a mediation group](//support.google.com/admob/answer/9234488#example2).\n- [Example 3: Bidding and waterfall ad sources in a mediation group](//support.google.com/admob/answer/9234488#example3).\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 [add your test device in the AdMob UI](/admob/flutter/test-ads#add_your_test_device_in_the_admob_ui).\n\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."]]