Display the Debugger

The debugger view can be accessed by calling the following method:

// Objective-C

[[Tapdaq sharedSession] presentDebugViewController];

Be sure not to use the debugger in the production version of the app.

Using the Debugger

Mediate Section

This page allows you to test your integration as it would normally be used.

This allows you to show any type of add you have set up, and it will automatically select a network for you.

Adapters Section

Here is a list of all the networks available and the state they are in, selecting any of them will allow you to directly interact with that network for testing.

  • Green - Ready
  • Grey - Adapter disabled on the dashboard
  • Yellow - Initialising
  • Orange - Failed to initialise or initialisation timed out
  • Red - Wrong version of the adapter is being used

Adapters not included into the project will not appear in the list.

Adapter Page

Here you can directly test each network and see ads from them. Only the ad types appropriate for each network will be available.

  • Load button will request a new ad.
  • Show button will display an ad that has loaded (Load must be called first)

Tapdaq SDK, Adapter and Network SDK versions are also noted, the Tapdaq SDK & Adapter version MUST match.

Adapter Status
  • Ready: Network is Ready to use.
  • No configuration: Adapter is integrated, but has not been initialised or is not enabled on the dashboard.
  • Failed to load config: Failed to initialise for an unknown reason
  • Adapter version mismatch: Failed to initialised because the Adapter version does not match the Tapdaq SDK version.
  • Configuration timed out: Failed to initialise within the set timeframe (60 seconds)
  • Configuring: Adapter is currently initialising.

Network Status

The property networkStatuses will return a list of all supported networks and their current status, as detailed in Adapter Status above. This will state if a network if successfully intergrated and initialised, or if not an error will be provided.

// Objective-C

NSArray *networkStatuses = Tapdaq.sharedSession.networkStatuses;
for (TDNetworkStatus *status in networkStatuses) {
    NSInteger code = 0;
    NSString *errorMessage = @"";
    NSError *adapterError = status.error;
    if (adapterError != nil) {
        code = adapterError.code;
        errorMessage = adapterError.localizedDescription;
    NSLog(@"%@: %@\n   Error:%tu, %@",, status.status, code, errorMessage);


TDLogger has a property logLevel which defines how fine-grained Tapdaq's logs are. This can be set at any point of the application lifecycle. There are five log levels available: Disabled, Error, Warning, Info, Debug.

// Objective-C

TDLogger.logLevel = TDLogLevelDebug;

What's next?

Now that you have successfully tested the ad networks that you wish to mediate, what would you like to do next?