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.

Adding Test Devices

To add any test devices, add your device in the Tapdaq Settings Panel:

Window>Tapdaq>Edit Settings

Then add your Device IDs for AdMob and Facebook, like so:

Window>Tapdaq>Edit Settings

Export your build and run your application, you will now see test ads for AdMob and Facebook.

Retrieving Test Device IDs

Devices ID's can be found in your logs when loading an ad from AdMob and Facebook, they look like this:

// Android AdMob
I/Ads: Use AdRequest.Builder.addTestDevice("4D32C4G30407EPC0EBB847E0E2694ACE") to get test ads on this device.

// Android Facebook
D/AdSettings: Test mode device hash: 441g39532c1fy296e2840753c9c217b0

// iOS AdMob
<Google> To get test ads on this device, call: request.testDevices = @[ @"d3fsh152gbac80cbcf774dd4520a4696" ];

// iOS Facebook
[FBAudienceNetworkLog/FBAdSettings:133 thread:1] Test mode device hash: 0aaea61262f466eedc5efacf191bd33a321e676c

When testing Facebook Audience Network, the test device should have the Facebook app installed and logged in

What's next?

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