Before you start running campaigns for our shared customer using Singular Links, you can use a demo / test tracking link (prepared by the Singular team) to test the configuration.
This will let you see what information a user click would send to Singular and from Singular to your servers.
Guide for | Singular Partners |
Prerequisites |
|
Tools |
A mobile device for testing. |
Step by Step
1 |
Reset Your Test Device's Advertising IDIf your mobile device has been used to test Singular attribution before, you have to clear the data before using it again. If this is the first time you are using the device for testing, you can skip this step. To clear the data:
Note: In iOS 14, if you turn IDFA access off for all apps, your global IDFA will be reset. The toggle must be turned back on before performing your test and you must accept the prompt "Allow App to Track" when opening the Singular Device Assist app. This ensures you can share your advertising ID with Singular to check your attribution test. Technically, one app can cause IDFA to reset for the entire device. Assume that only one app called requestTrackingAuthorization got permission to track. See more information here for resetting your advertising ID, if additional help is needed.
|
2 |
Get the New Advertising IDNow that your device has a new advertising ID, you need to find out what it is. There are third-party apps that can help you, such as Singular's Device Assist testing apps for iOS and Android, or you can go into the device settings yourself:
|
3 |
Get the Singular LinkYou should have received a tracking link from the Singular team that looks like the following. Note that the link includes parameters, such as "aifa", "idfa", "cl", and "pcid". The values in {curly braces} are macros - placeholders meant to be replaced with actual values by the ad network when it serves the ad (the macros' names and appearance may vary). Important: you must remove device ID macros from the tracking link that will not populate a value. If macros themselves are sent instead of a value your click may not be logged with Singular and there will be no attribution.
|
4 |
Insert Advertising ID into LinkBefore you can test the link:
Here is an example of what the result should look like (for an Android device):
Note: All the parameters in the link have to be given a valid value or left blank. If you click on a link that still has placeholders in curly braces {}, it may not result in successful attribution. To learn more, see Tracking Link Parameters. |
5 |
Trigger the LinkSend the tracking link to your testing device. Then click the link from the mobile device. You are redirected to the Apple App Store or Google Play Store. |
6 |
Install and Open and Click the App
*Revenue events are events that need to be configured in a postback in order for a revenue amount to also be sent in your postback. Your postback template must contain the macro {AMOUNT} or an equivalent from our documentation in order to receive a revenue value. |
7 |
Verify AttributionTo verify that the install has been attributed correctly by Singular, you can share your AAID/IDFA with the Singular integration engineer. The engineer will share the feedback and the relevant logs of the test. |