Ad inspector is a new feature included with the latest Google Mobile Ads SDK (7.68.0 or later for iOS). It provides useful serving insights and third-party ad source testing in real time. No coding required.
With a simple gesture, such as a shake or flick of your test device, ad inspector is displayed on top of your apps as an overlay. Using ad inspector, you can:
- Inspect your ad units
- Check whether your ads are filling as expected
- Identify errors and view details about how to resolve
- View the mediation waterfall details per request
- Test individual third-party waterfall ad sources
- Verify that you’ve correctly configured the ad source for mediation
- Check how each of your ad sources are performing per ad unit
How it works
Ad inspector automatically begins inspecting your app’s ad serving once you’ve opened your app on a registered test device.
You’ll need to interact with your app to make sure there are enough ad requests for you to analyze. Note that you may see a set of ad requests even on app start if your app prefetches ads.
After you invoke ad inspector on your test device using a gesture or a custom API call, you’ll see your app’s ad units in the order of latest activity (whether they’ve shown an ad or not).
Note: We recommend initializing the Google Mobile Ads SDK before using ad inspector. You won’t be able to see the full list of your ad units until you’ve initialized the SDK. Learn more about initializing the Google Mobile Ads SDK (Android, iOS).
Additionally, if your app contains ad units that are not associated with your AdMob app ID, the ad unit will only appear if at least one request has been completed for that ad unit.
Tap an ad unit to view its SDK request log, which details the mediation waterfall until the ad was filled (or the waterfall ended without a fill) for the latest ad requests. From here, you can expand each ad source that did not fill an ad to view details about the no fill error.
For third-party ad sources, the error messages are sent directly from the ad source. If you need more information, refer to your third-party ad source.
Testing single ad sources
With ad inspector, you can test the setup of a single, third-party waterfall ad source. This allows you to verify that you’ve correctly implemented the third-party mediation adapter and that the ad source is serving as expected.
To start a single ad source test, toggle Single ad source test at the bottom of the app. Then, select the ad source you’d like to test. When ad inspector is enabled for a single ad source test, all future ad requests will attempt to return ads from the selected ad source.
In a single ad source test, you can tap an ad unit to view its SDK request log. This lets you know whether the ad source filled the ad requests made after single ad source testing is enabled. If the ad source did not fill an ad request, you’ll see an error message with details about what caused the no fill error.
If you’ve added multiple instances of the selected ad source to a mediation waterfall, you’ll see each instance of the call to the ad source in the waterfall until the ad was either filled or the waterfall ended without a fill.
Note that single ad source testing automatically expires after 60 minutes.
When you turn on single ad source testing, you’ll need to force restart your app. Because some apps cache ads at startup, restarting your app ensures that the single source test applies to every ad request in the testing session.
For Android devices, you can usually force restart an app through your phone’s Settings app. Settings can vary by phone. For more information, refer to your device manufacturer.
Learn how to force restart an app for iOS devices.
To use ad inspector, you must:
- Install and initialize the latest Google Mobile Ads SDK version 7.68.0 or later for iOS.
Currently, ad inspector can be used with iOS devices. Support for Android devices is coming soon.
- Set up a test device and select the gesture you’d like to use to invoke ad inspector on your device. Learn how.
- On your test device, open your app and begin interacting with the app. This ensures that there are enough ad requests for you to analyze. Note that you may see a set of ad requests even on app start if you've implemented ad caching on your app.
- After interacting with your app on your test device, invoke ad inspector by using the gesture you selected in Step 2.
You can also activate ad inspector on your test device through an API call. Learn more for iOS.