Testing Basic Integration Functionality

 

Testing Initialization

The first thing to test is whether your integration is initializing and sending information to Singular. This already allows Singular to start tracking attribution for this app! To check, look for user sessions in the event log.

To test initialization:

  1. Register a test device in the SDK console (see instructions).
  2. On your device, open the app.
  3. Make sure the event log shows a session row for the device:

    image10.png

If this row does not show up, check the user-level logs for the session event. It is possible you opened the app before the SDK console finished processing the registration of the new device.

Testing Google Play Install Referrer/Apple iAd Referrer

Both Google Play and the Apple App Store provide some data that can help determine the attribution of an app install. The Singular SDK collects this data automatically and sends it to Singular to help in the attribution process.

In this step, you will validate that the data has been sent to Singular successfully.

[ANDROID] Validating Google Play Referrer

On Android devices, Singular should be receiving the Android install referrer. To validate it, after you have added the device to the SDK console, open the app on your device. In the SDK console, make sure you see an “__installReferrer” event.

image3.png

If you don't see the __installReferrer event, reset the device (see instructions) and try this test again.

[iOS] Validating Apple Search Ads Attribution

On iOS devices, Singular should be receiving the iAd Attribution data. To validate it, after having added a device to the console and installed the app on it, check the SDK console and confirm that “__iAd_Attribution__” event shows up.

image15.png

Notes:

  • This event shows up soon after the app is installed. To test it on an older device on which the app has been installed for a while, follow the instructions to reset the device and then add the device again to the console and re-install the app on it.
  • If the event does not show up, it is possible the app was opened before the device was completely registered in the SDK console. If you integrated the Singular static library, make sure you are importing iAD.framework (if you are using CocoaPods it is already included).

Testing the Custom User ID

If your SDK integration sends a custom user ID to Singular, here's how to test it.

  1. Register the device in the SDK console.
  2. Open the app.
  3. If needed, in your app, trigger an action that sends the user ID (such as logging in). The nature of the action depends on your implementation.
  4. In the next event sent to Singular, expand the event details in the SDK console and check that the details include a value for "custom_user_id".

    image6.png

If the user ID does not show up:

  • Check that the method that sets the user ID is actually being called in your app when you want it to be.
  • You may want to add a Singular SDK event and call it “setting custom user id” so that the event shows up in the SDK Console.

 

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