Debugging

Logging

Within the Tapdaq Settings Panel the Debug checkbox will enable verbose logging available via Android's logcat and XCode's console.

Ensure that this setting is disabled before submitting to the store as it can impact performance.

Display the debugger

Tapdaq's debugger enables you to test your SDK integration. You can specify and test different ad types from each ad network you have integrated to ensure you are receiving ads as expected.

Please note, for the debugger to work you will also need to have input the correct ad network keys on the Tapdaq dashboard.

To display the debugger, add the following into a script:

AdManager.LaunchMediationDebugger ();

Export your build and run your application, you should have a popup appear with a list of networks to test.

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.

Android

  • Green - Ready
  • Red - Not Ready (Failed to initialise)

iOS

  • 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

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.

Android Adapter Status
  • Ready: Network is Ready to use.
  • Not Integrated: Adapter is not integrated in the project.
  • Disabled: Adapter is integrated, but has not been initialised or is not enabled on the dashboard.
  • Failed: Failed to initialise for an unknown reason
  • Failed, Adapter version mismatch: Failed to initialised because the Adapter version does not match the Tapdaq SDK version.
  • Failed, Missing Activities in AndroidManifest.xml: Failed to initialised because necessary Activities have not been added to the AndroidManifest.xml
  • Failed, Missing Credentials: Failed to initialise because not all the required credentials have been added to the dashboard.
  • Timed out: Failed to initialise within the set timeframe (60 seconds)
  • Waiting: Adapter is currently initialising.
iOS 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 method GetNetworkStatuses() 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.

List<TDNetworkStatus> networkStatuses = AdManager.GetNetworkStatuses();
foreach(TDNetworkStatus status in networkStatuses) {
    int code = 0;
    String message = "";
    TDAdError adapterError = status.error;
    if (adapterError != null) {
        code = adapterError.code;
        message = adapterError.message;
    }
}

What's next?

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