Test Mode

The Tapdaq SDK does not have a test mode, however many networks do and will enable ads to show reliably for test purposes. To enable SDK level test mode (for networks which support it), enable debug logging like so:

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.

AdColony

Set via the AdColony dashboard on a Zone level

AdMob

Full documentation available in their Android Documentation and iOS Documentation

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

Retrieving Test Device IDs

Use adb logcat or Android Studio's console to view the applications logs, devices ID's will be printed when loading an ad from AdMob, they look like this:

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

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

AppLovin

Set via the AppLovin dashboard on an App level. Note it is not immediate and will only be enabled for a few hours

Chartboost

Set via the Chartboost dashboard on an App level. Note it will only be enabled for a set time period

Facebook Audience Network

Two options are detailed in their documentation

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

Server Side

Uses IDFA/GAID to identify test devices, set via their Monetisation Manager dashboard

Client Side

A device id can be obtained from the logs and set via the Tapdaq interface.

Due to a bug in Android Facebook Audience Network 5.6.0, used in Tapdaq 7.4.0 - the device id does not appear in the logs, it's recommended to use to server side solution. This does not affect iOS.

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

Retrieving Test Device IDs

Use adb logcat or Android Studio's console to view the applications logs, devices ID's will be printed when loading an ad from Facebook, they look like this:

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

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

InMobi

Set via the InMobi dashboard on a Placement level

IronSource

Set via the IronSource dashboard on an App/Ad Unit level

Maio

Set via the SDK, enable Tapdaq Debug mode for testing.

Mintegral

No test mode available.

Tapjoy

Full details in their documentation

Set via the Tapjoy dashboard, IDFA/GAID's can be added to enable ads on specific devices

UnityAds

Set via the UnityAds dashboard on an App/Project level

Vungle

Set via the Vungle dashboard on an App level

YouAppi

Set via the YouAppi dashboard on an App level

ZPlay

Some test credentials are available in their Android Documentation and iOS Documentation