|Testing Your SDK Integration|
The SDK console is a tool you can use to test whether your SDK or server-to-server integration is communicating with Singular properly.
After you add a test device to the console (by providing its ID), the console shows you whether your app is sending the information that Singular needs in order to attribute installs, track events, etc.
We recommend using this article to get familiar with the SDK console before you start following the testing guides.
Adding a Test Device
To add a device to the console:
- In the Singular platform, go to Settings > SDK Console.
Click Add Device and select the platform of the device you are adding, and then select the keyspace (i.e., the type of advertising ID):
Platform Possible Keyspaces iOS IDFA Android Google Advertising ID (AIFA)
Android ID (ANDI)
Input the ID from your device and click Add.
Make sure the new device appears in the Tracked Devices list.
The device has to be in enabled mode (the eye icon on the left should not be disabled) for any events from the device to appear in the events log.
You can add a descriptive name for the device in the Device Name column to make sure you don't confuse it with other devices you may be tracking.
Reading the Event Log
After you've registered a device, the events sent from the device start appearing in the event log:
Note: If no events from the device are appearing, make sure the device is enabled in the Tracked Devices list (the eye icon is not disabled):
Click on a row to show the full details of the event as sent from the app:
Removing a Device
To delete a device, hover over the Device ID and click Delete. This will clear all event logs from the screen, but will not clear the attribution.
Resetting a Device and Clearing the Install Attribution
If you want to re-test your SDK integration again with the same device, you have to remove all locally cached data from the device, in addition to clearing the device's attribution in the Singular platform.
Steps for Android Devices
- Close the app and confirm that it is not running (use Force Stop from the Settings menu if you have the option).
- Go to the Settings menu by tapping the wheel icon in your notification window or in the Apps menu.
- Go to Apps, select the app you are testing, long press on the app and select App Info.
- Select Storage and then select Clear Cache and Clear Data.
In the Singular SDK Console, hover over the device row and click Forget to have our system forget this device attribution.
Note: Google Play offers apps that perform this function for you (see example).
Steps for iOS Devices
- Close the app and then uninstall.
Open the SDK Console and click Forget to have our system forget this device attribution.
Note: Testing With Re-engagement Inactivity Windows
The inactivity window is a setting that determines how long the user has to be inactive before they are eligible for re-engagement attribution. If you are testing re-engagement attribution prior to launching campaigns, an inactivity window would make it harder for you. This is why test devices (devices that have been added to the SDK console and have the eye icon enabled) are exempted from the inactivity window.