[null,null,["最后更新时间 (UTC):2025-08-31。"],[],[],null,["Select 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\nBefore you continue, do the following:\n\n- Complete all items in the initial [Prerequisites](/ad-manager/mobile-ads-sdk/android/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/android/ad-inspector/launch-ad-inspector).\n\nView waterfall details for an ad unit\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\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\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 device](/ad-manager/mobile-ads-sdk/android/debug#link_your_device) through the 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\nIf you encounter a **No ad returned** issue, copy the buyer generated data and\nshare with the ad sources for assistance."]]