Mediation Debugger is a suite of testing tools. These tools help you integrate and launch faster with MAX. You can use them to confirm the validity of network integrations. This ensures that you can successfully load and show ads, among other things.
Mediation Debugger does not support Custom SDK Networks
There are four sections in the Mediation Debugger:
- Integration Status
- Use this to confirm that you have successfully completed the network integration.
- Testing with Test Ads
- Use this to load and show ads from networks by using each network’s test mode.
- Testing with Live Ads
- Use this to load and show ads from networks by using your waterfall configuration.
- Sharing the Mediation Debugger
- Use this to generate a copy of your integration checklist that you can send to reviewers before you launch.
Displaying the Mediation Debugger
To display the Mediation Debugger, make the following call:
Map? configuration = await AppLovinMAX.initialize(your-sdk-key); AppLovinMAX.showMediationDebugger();
The Mediation Debugger displays the integration status of the MAX-mediated network adapters and/or SDKs found in your app. It flags integration issues associated with each network (such as a mismatch between the network SDK and adapter version, or missing SKAdNetwork IDs). It displays the integration status of mediated networks in three sections:
- Completed Integrations
- You have successfully integrated these ad networks into your app.
- Incomplete Integrations
- These ad networks have one or more issues you need to fix before you can integrate them successfully into your app. Tap on the cell for more information. You can find integration instructions in the Preparing Mediated Networks section of this documentation.
- Missing Integrations
- You have not integrated these ad networks into your app.
Testing with Test Ads
After you successfully integrate your mediated networks, AppLovin recommends that you validate your integration by loading and showing those networks’ test ads.
Some mediated networks may have requirements that you must meet before you can load ads. For example, the SDK may require enough time to fully initialize (this is true, for instance, for AdColony, Tapjoy, and Liftoff Monetize). If you do not allow sufficient time, this might cause no-fill errors. AppLovin recommends that you load ads during the window from 2–5 seconds after you initialize the SDK.
To use the Test Ads feature,
- Select a mediated network that you have successfully integrated, under the Completed Integrations section.
- Tap Enable under Test Ad.
- Restart the application so the mediated SDK initializes with test ad credentials.
- Select the mediated network again to enter the test-ads view seen below:
Testing with Live Ads
The Mediation Debugger allows you to view and test ads using your Ad Units’ waterfall configurations.
If you test with live traffic, some networks might flag this as fraudulent activity. You might also experience issues getting filled due to your waterfall configuration or the network’s targeting parameters. AppLovin strongly suggests that you test with live ads when you validate the integration.
To begin, select the View Ad Units cell, which displays the list of Ad Units associated with your app. Select an Ad Unit from that list to view the waterfall configuration from the MAX Ad Unit section.
Country and LAT (Limit Ad Traffic) targeting rules apply to your device when you view and test live Ad Units.
Select an ad unit from the Ad Units list and click the Load button to request an ad for the Ad Unit.
Single Ad Source
You can also select one of the mediated networks for the ad unit to be the only ad source for ad requests. To do so, click one of the networks in the Bidding Networks list for that ad unit. This isolates that network in the list. Next, click the Load button to request an ad from that network for the Ad Unit.
Within the App
You can use the Mediation Debugger to force live ads from selected networks within your app’s natural environment. To begin, select the Select Live Network cell and follow the instructions on the screen.
This feature is not available when test mode is enabled. Several networks consider live ads on test devices to be fraudulent traffic. AppLovin recommends that you use test ads to validate your integration. You can use this feature to monitor live traffic.
Sharing the Mediation Debugger
Quality reviewers may ask you to share a copy of your Mediation Debugger output before you push your apps live. This ensures that your integration is healthy and ready to go live.
To share your Mediation Debugger output, click the share button at the top right of the Mediation Debugger home screen and complete the action using your preferred method.
The Interactive Advertising Bureau created app-ads.txt as a way for app publishers to prove to advertisers that they own the app that originates an ad request. This prevents malicious actors from making fraudulent ad requests.
Starting in SDK version 11.6.0, you can check through the Mediation Debugger whether your app-ads.txt file contains properly formatted entries for AppLovin. For more information on how to set up an app-ads.txt file on your domain with entries for AppLovin, visit this link. The Mediation Debugger displays a row marked app-ads.txt under the MAX section with a ✅ if the app-ads.txt file containing all entries for AppLovin was successfully found under the root domain of your developer website listed on the Google Play Store or Apple App Store.