Integrating the Singular SDK

You can easily integrate the Singular SDK within your app using our SDK documentation.

Find all the tools for building the integration under Settings > SDK Keys.


This key is necessary for the Singular servers to identify your account.


SDK Console

The SDK Console displays calls for session and event data sent by the Singular SDK or direct use of the Singular Server to Server API. It is a tool for application developers to verify if their instrumented events and sessions are being received by the Singular platform.

Adding Devices

To add a device:

  1. Select the Platform and Keyspace of the device that you want to test
  2. Insert the identifier and click "Add"


Once the device is added, the event logs will start collecting data. You can view event logs for multiple devices at once by selecting the Show/Hide Button:


Note: you can add up to 20 devices at once.

Deleting Devices and Clearing Attribution

To delete a device, hover over the Device ID and select the Delete button. This will clear all event logs from the screen, but will not clear the attribution.

To clear a device's attribution, select the Forget button. This will reset the attribution for a specific device so you can retest with the same device.


Using the Console

Once a device is registered, events trigged in the app via the SDK will appear in the console . You can drill down on a specific line item to view more details:


Automatically Tracked Events

Aside from your explicitly tracked sessions and events, there are some events that are tracked automatically by the SDK and may become useful in debugging/understanding the data in some scenarios:

SDK Event Name Description
__installReferrer__ Android Only - This event contains the payload of the Android install referrer (when available). If the Android install referrer is implemented, this event is automatically sent shortly after the Android SDK initialization. This event is used as part of the Singular attribution process.
__iAd_Attribution__ iOS Only - This event contains the payload of the Apple Search Ads API response (when available). This event is sent shortly after the iOS SDK initialization. This event is used as part of the Singular attribution process.


Was this article helpful?
0 out of 0 found this helpful