Ad inspector beta

Ad inspector is an in-app overlay that enables authorized devices to perform realtime analysis of ad requests directly within a mobile app.

It enables you to:

  • Determine the recent fill status of each ad unit in your app.
  • Find the ad source that filled each request, or the error if it was a no fill.
  • For each request, discover the mediation waterfall and request status for each ad network, up until an ad fill occurs.
  • Isolate testing of a single mediation ad network within the context of your app.


In order to use ad inspector, you need to:

Launching Ad Inspector

There are two different ways to launch ad inspector.

  1. Use the gesture selected in the AdMob UI when registering a test device.
  2. Programmatically using the provided API.

Launching using gestures

No changes are needed to your app to launch ad inspector with a gesture. Simply perform the gesture (double flick or shake) that you configured in the AdMob UI for that test device. Learn more.

Launching programmatically

Ad inspector can also be launched programmatically using the following API:

[GADMobileAds.sharedInstance presentInspectorFromViewController:viewController
                         completionHandler:^(NSError *error) {
 // error will be non-nil if there was an issue and the inspector was not displayed.

This API works for devices registered programmatically or in the AdMob UI. Learn how to register a test device.

Ad inspector can be launched from anywhere in your app.

Viewing recent ad request results by ad unit

Once launched, the main screen of ad inspector appears, containing a list of all ad units in the AdMob UI associated with your AdMob app ID:

app id screen

Ad units are ordered chronologically with most recently completed requests first. As shown above, known ad units with no requests completed are dimmed.

Viewing ad request details for an ad unit

Ad inspector enables you to drill down into specific ad requests for each ad unit and view the mediation waterfall that is used for each ad request. For the given waterfall, the results of the request to each individual ad source are displayed.

To access this information, click through to any ad unit in the recent ad requests list. This shows a list of ad requests for the given ad unit and the status of that request.

Each request can be expanded using the disclosure indicator to show the results of the mediation waterfall that was used for that request, with any error and latency that was applicable for that request.

request log

Testing a single ad source

Ad inspector has a feature to restrict ad requests in your app to only serve ads from a single third-party ad source. Note the current release supports testing waterfall ad sources only.

To enable this feature, toggle the Single ad source test switch at the bottom of the ad units list screen. This displays the following ad source selection dialog:

ad source 1 ad source 2 ad source 3

You can then select a single ad source to test. Once an ad source is selected, the following screen appears:

restart screen

The single ad source setting will still apply to any future requests in the same session, but won't apply to any previously cached ads. Force restarting your app is recommended when applying a single source test in order to invalidate any cached ads that may be served instead of your chosen ad source receiving a request.

After restarting your app, assuming a successful request, the ad unit placement will show an ad from the selected network.

Launching ad inspector when a single source test is active will show the active test ad source:

ad source 4

When this test is on, ad units that have a mediation waterfall containing the selected ad source will only request ads from the selected ad source. If the associated waterfall for an ad unit does not contain the selected ad source, the request will result in "No Fill".

Stopping a single source ad test

To stop the test, toggle the switch to off:

stop test

A confirmation message then appears over the following restart screen:

restart screen

We recommend a force restart of your app after stopping the test in order to invalidate any cached ads for the ad source that was tested. Single ad source testing will then automatically expire after 1 hour.