Generating Tracking Links

Tracking links are used for attributing an install for the relevant click. In addition to the basic attribution data they contain, it is possible to include other properties, which eventually will be displayed in your Singular reports. This data will help providing you a deeper view of your marketing efforts and results.

Using Singular you can create two types of tracking links:

  1. Regular Tracking Links - for integrated partners like AdColony & Chartboost
  2. Smart Links - for custom marketing sources like email & sms campaigns

Please note that Self Attributing Networks do not require tracking links, please refer to the Special Partners documents to configure these sources.


Understanding Tracking Links

In the process of attribution, the tracking links are taking part on the click itself - once a potential user clicks on an Ad, the tracking link is being sent to the Singular server. The data included in it, is being saved, and later, when an install occurs by that user, the Singular attribution service is able to match the install to that click, based on the data collected using the tracking link, and the data sent to Singular once the install occurred. For more information on the attribution methods, click here. image1.png 

Tracking Links Format

While basic format of a tracking link should be:[link_id]&h=[link_hash]

The Tracking link properties can be ‘fixed’ properties (such as campaign name), or macros which are equivalent to variables. The Macros are uniquely provided by each Source (Ad Network). Both the macros and Fixed properties will automatically be added to the Tracking links while being generated. In case you find that a tracking link is missing a Macro known for a specific source, please contact and report the missing Macro.

Below is an example of an Android Tracking Link along with relevant tracking macros:[RAW_UDID]&and1=[SHA1_ANDROID_ID]&aifa=[GOOGLE_AD_ID]&s=[APP_ID]&idfa=[IDFA]&odin=[ODIN1]&udi1=[UDID]&api_key=d4636d565f59e217801b5721af716eac&product_id=[PRODUCT_ID]&ip=[IP_ADDRESS]&ve=[OS_VERSION]&cl=[CLICK_ID]&pc=[RAW_AD_CAMPAIGN_ID]&h=99ebf893909cc390843b2cabc6c4f7eccb567676


Creating Regular Tracking Links

Used to track mobile app installs campaigns with integrated partners such as AdColony, Chartboost. These tracking links ensures that the partner will receive a postback for every attributed install.

  1. From the Attribution menu on the left, click on ‘Create link’.
  2. Select the App, Site and Destination URL. If you are missing a site or destination URL in the drop down lists, please refer to the Apps screen to update the missing data.
  3. If you have selected a deeplink (or Universal Link for iOS), you can optionally mark that to also be used as a deferred deeplink.  If your deeplink value is "myapp://page?id=1", then the value received in the SDK callback will be "myapp://page?id=1".
  4. Start typing the Source name and select it from the optional list of sources.
    In case the selected source was not configured yet, it will appear with an Orange message: “Please configure this source”
    In that case, click on the Configure link to configure that source.
    Note that each source may have different configuration options.
    Click here for additional information on source configuration, Lookback Window and Events Postbacks.
  5. Type campaign name and click the Generate Link button.
  6. That’s it. Your tracking link is ready to go. Copy the link using the Copy button.

Creating Smart Links

Smart Links allow you to create a single tracking link that, when clicked, will redirect the user to different destinations depending on their device (iOS, Android, other). These tracking links are useful for tracking Email, SMS or any campaign with a non integrated source.

For example, you might want to serve a tracking link in an Email campaign with the following redirect behavior:

  • iOS - take the user to the iTunes app store
  • Android - take the user to the Google Play Store
  • Other - take the user to your web site.



  1. From the Attribution menu on the left, click on ‘Create Smart Link’.
  2. Select the App
  3. Select one of the channels or choose “Custom”
  4. Type the campaign name
  5. Choose the destinations and deeplinks for each platform (iOS, Android, other). Note: To enable the deferred deeplink select the checkbox.  If your deeplink value is "myapp://page?id=1", then the value received in the SDK callback will be "myapp://page?id=1".
  6. Click the Generate Link button and copy the link!

Tracking Link Parameters

Reserved Parameters

Reserved parameters are parameters that are the standard or common parameters used by the Singular attribution engine, to properly perform and report attribution with integrated channels and partners.





Required Field - Generated Singular Tag ID coded to your application, channel/partner, and Singular Campaign Name



Required Field - Generated Singular security hash.  Matches to Singular Tag ID



Publisher application or site



Click ID assigned by Ad Network



Campaign ID assigned by Ad Network



Optional override for Singular Campaign Name.  Appending this while override the original Singular Campaign Name used when generating the tracking link.



Creative name assigned by the Ad Network



Re-engagement Tracking. Should be set to '1' if tracking re-engagement



Advertising Identifier in RAW format - iOS only



SHA1 of IDFA - iOS only



MD5 of IDFA - iOS only



Android ID - Android only.  Fallback if Android Advertising ID is not available on the device



SHA1 of Android ID



MD5 of Android ID



Android Advertising ID



SHA1 of Android Advertising ID



MD5 of Android Advertising ID



OS version. Required for server-to-server partners.



IP of the click / impression. Required for server-to-server partners.



Redirect flag. Append redirect=false to disable redirect for tracking link.  Required for server-to-server partners.



Non-Reserved Parameters (Passthroughs)

Occasionally you may see parameters in tracking links which is not a reserved parameter.  These parameters are generally used with specific integrations with partners, in order to "pass through" these values to the partner in the attributed postback.  While they enable other more advanced use-cases for postbacks, they are not common.


 For questions and additional information, please contact

Have more questions? Submit a request


Please sign in to leave a comment.