The Testing Console (Developer Tools > Testing Console) helps you make sure you have implemented your SDK/S2S integration 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.
For a detailed guide on using the Testing Console to test your integration, see How to Test Your Singular SDK Integration.
If you have registered a test device and are following the guide to test your SDK integration, but no rows are showing up in the Events Log, double-check the following:
- Make sure you opened the app on the test device (to see a user session).
- Make sure you created some in-app events (if you want to test your events).
- The Testing Console only shows events live (it does not look for historical events from the device).
- Make sure you've selected your device from the dropdown:
- Look for the COLLECTING REAL TIME DATA message above the Events Log. If the message is displayed, it means that Singular is currently checking for events from at least one device. If no events are appearing in the log, this may indicate that they are not being sent properly by the SDK in your app.
Starting from Singular SDK 12.0.0, you don't need to test the _InstallReferrer event. Once your app is pushed to the store, our SDK will place the _InstallReferrer data in the first session. You only need to see if the session appears in the Testing Console.
If you are using older versions of the Android SDK, you will still need to check the _InstallReferrer event in the Testing Console.
To add a device to the console:
- In the Singular platform, go to Developer Tools > Testing Console.
Click Add Device.
Select the platform of the device you are adding, and then select the keyspace (i.e., the type of advertising ID), e.g. IDFA or Google Advertising ID.
Input the ID from your device and click Add.
- For iOS devices, we recommend using the IDFV if you have access to it. You can use the IDFA, but then you won't be able to make the console "forget" your device's data (see step 5).
- Your device's GAID or IDFA should be available in your device's Settings menu. Singular also offers a Device Assist application that you can install on your test devices to help you acquire the device IDs. Download our app for iOS or for Android.
- See also: Types of Device IDs.
Important: Make sure the new device appears in 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.
Tip: For a detailed guide on using the Testing console to test your integration, see How to Test Your Singular SDK Integration.
After you've registered a device, sent some events, and waited around 1 minute, the events start appearing in the event log on the Testing Console page.
Click on a row to show the full details of the event as sent from the app.
Click Clear Log to empty the Events Log when it gets too long.
Tip: If you don't click Clear Log, the log retains the last 500 events from each of the tracked devices.
Deleting a Device
To delete a device from the Tracking List, click the Edit icon, and on the shelf that appears, click Delete Device. This will clear all event logs from the screen, and Singular will delete internal data about the device's 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 Testing Console, select the device from the dropdown and click the Edit (Pencil) icon. On the shelf that opens, click Delete Device to have our system delete this device attribution.
Tip: Google Play offers apps that perform this function for you (see example).
Steps for iOS Devices
- Close the app and then uninstall.
Open the Testing Console, find your device in the dropdown, and click the Edit icon. On the shelf that opens, click Delete Device to have our system delete this device attribution.
Tip: 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 Testing Console and have the eye icon enabled) are exempted from the inactivity window.