We’re excited to announce the launch of new testing features on ad inspector across all platforms for our AdMob and Ad Manager publishers.
Previously, ad inspector tested all ads in context - in other words, you had to fire up your app, navigate to the appropriate screen in the UI, and have your ad load as it would for any other user. While this provides for the most accurate testing scenario, it also puts more work on you as the publisher and tester of your app. You don’t want ads buried in more obscure screens in your app to lose out on the testing attention and care they need!
With our latest update, you can now use test ads to load requests for any ad unit - no matter where it's located in your app. Rather than needing to navigate through your app to test each ad unit, you can execute your tests directly from ad inspector.
How do I use ad inspector’s new testing features?
Beginning with version v10.0.0 on iOS and v21.4.0 on Android of the Google Mobile Ads SDK, ad inspector supports running tests directly from the ad unit detail screen via a “Request test ad” button:
All of your requests made from your app’s UI or within ad inspector will appear in the SDK request log; your requests made from within ad inspector will be differentiated by being labeled with “Requested from ad inspector”. For these special requests you’ll be able to tap the “View” button one time to view the actual ad, see which network filled the slot, and more.
Alongside single ad source testing, these new testing features will allow you to rigorously test each individual ad network integration in your app.
To learn more about how to test your ads with ad inspector, check out our developer guides here:
- Android (AdMob | Ad Manager)
- iOS (AdMob | Ad Manager)
- Flutter (AdMob | Ad Manager)
- Unity (AdMob)
- C++ (AdMob)
If you have any questions or need additional help, please contact us via the developer forum.