This repository was archived by the owner on Nov 7, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Debugging
Dominic Roberts edited this page Dec 4, 2017
·
7 revisions
To start the Tapdaq debugger:
_tapdaq.startDebugger();Google Ad Mob and Facebook Audience Network ad services both allow developers to specify test devices, these will serve test ads before you have your account fully set up.
To add test devices simply specify the network and the device IDs:
config.addTestDevices(TapdaqAdapter.AD_MOB, ["0000000000000000000000000000"]);
config.addTestDevices(TapdaqAdapter.FACEBOOK, ["0000000000000000000000000000"]);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
If you are having any problems integrating, feel free to contact us on support@tapdaq.com and we will be more than happy to help.
Now that you have successfully tested the ad networks that you wish to mediate, what would you like to do next?