Mediation Debugger

Open the CloudX Mediation Debugger on a test device, read what it shows about your integration, and use it to check adapters, ad units, test mode and single bidders.

The Mediation Debugger is a screen inside the CloudX SDK that shows the state of the integration on the device you’re testing. Your developer adds it to the QA build, usually behind a debug menu or a gesture. Use it alongside the dashboard tests: the dashboard shows what CloudX received, and the debugger shows what the app has installed and configured.

Open the Mediation Debugger

Your developer opens it with one call after the SDK finishes initializing. Before that, the call returns false and nothing opens. It’s meant for development and QA builds. See the Mediation Debugger section of your guide: iOS, Android, Unity, Flutter, React Native.

On a registered test device with iOS SDK 3.13.0, Android SDK 4.13.0, Unity 4.13.0, Flutter 3.13.0 or React Native 3.13.0 and later, it also opens without code: turn the phone face down and back up twice within 3 seconds, then hold the CloudX button that appears for 10 seconds.

The gesture works only after the SDK has started. If the app is Inactive, turn on Test traffic for the device: an Inactive app serves test requests only, so with Test traffic off the SDK doesn’t start on that device and the gesture isn’t available.

What it shows

  • Every installed network adapter, with its version and status: completed, incomplete, missing, or not configured
  • The SDK configuration your app received from CloudX
  • The privacy state, such as the consent signals the SDK found
  • Your ad units

Use it for testing

Check adapters before you test networks

For SDK-based networks, open the debugger and check that each required adapter shows as completed. If an adapter is missing or incomplete, contact your developer to add or finish it. SDK-less partners such as illumin and zMaticoo use CloudX’s built-in renderer and do not require a separate partner adapter; validate them through their setup guides and auction results instead.

Load a test ad for an ad unit

Pick an ad unit in the debugger and load a test ad for it. On Android, iOS and Unity you can also show the ad. This checks one ad unit without going through the app’s own ad flow.

Request test mode

You can request test mode from the debugger instead of registering the device in the dashboard first. The request takes effect the next time the SDK starts, so close and reopen the app. CloudX decides whether that session runs in test mode.

Test one bidder at a time

On a registered test device, pick one bidder in the debugger. On iOS, test mode also allows it. Every CloudX load then uses only that bidder, until you pick All bidders or restart the app. You don’t need a separate QA ad unit for each network.

Available from iOS SDK 3.13.0, Android SDK 4.13.0, Unity 4.13.0, Flutter 3.13.0 and React Native 3.13.0.

Share a report with CloudX

Share the whole report as text from the debugger, and attach it to your support request along with any downloaded auctions.