Attribution Integrations: Client-Side and Server-Side (S2S) (Guide for Singular Partners)

Learn about the two types of attribution integrations Singular offers. Make sure to read these first: Integrating with Singular: A Guide for Partners and Integrating with Singular Attribution FAQ (Partners).

 

Client-Side Attribution

A client-side integration is the most common (and recommended) way to integrate with Singular's attribution service. It lets the advertiser make full use of Singular smart tags and destinations.

The attribution flow is as follows:

  1. The user clicks on an ad served via an ad network's conversion pixel.
  2. The conversion pixel redirects to Singular's attribution tracking URL.
  3. Singular saves information about the click and redirects the user to the app store or to a deep link destination.
  4. The user downloads and opens the app.
  5. Singular saves information about the install and attributes the install to the last click on the same device (see Understanding Singular Mobile App Attribution to learn more).
  6. Singular sends out any relevant install postbacks that have been set up.

Snip20180820_55.png

Server-Side (Asynchronous) Attribution

An S2S integration with Singular would follow the same flow, except that the ad network itself redirects the user to the app store or the deep link destination, and Singular click notifications are served by an ad network server or from the client (asynchronously).

The attribution flow is as follows:

  1. The user clicks on an ad served via an ad network's conversion pixel.
  2. The ad network server receives the click, serves a redirect, and sends Singular a click notification.
  3. Singular saves information about the click.
  4. The user downloads and opens the app.
  5. Singular saves information about the install and attributes the install to the last click on the same device (see Understanding Singular Mobile App Attribution to learn more).
  6. Singular sends out any relevant install postbacks that have been set up.

Snip20180819_50.png

 To send Singular clicks from the server side, you have to add these parameters:

  • "ip" - the raw IP address.
  • "ve" - the device OS version, e.g., "9.2".

Optional: Appending Google Play Install Referrer (Android Only)

Partners who have a server-to-server integration with Singular's measurement links can append referrer values that can be used in Singular's click-through attribution process.

To enable:

  1. Append and URL-encode the following key-value-pair to the referrer, to served Play Store URLs:  singular_external_click_id=[partner_name]_[uuid]
    • [partner_name]_[uuid] is the recommended format.
    • [partner_name] can be any agreed-upon value and is a static value used to aid debugging
    • [uuid] should be a UUID, unique per click.
    • Other formats for singular_external_click_id are supported as long as the value is guaranteed to be unique for each click and the length is no greater than 50 characters.
    • Other non-Singular key-value-pairs can be appended to the referrer, but be sure to URL encode them properly.
  2. Append the singular_external_click_id value (alongside other existing query parameters in the click URL) via the  sng_ref= query parameter in the asynchronous click to Singular's click URL. For example: https://customer.sng.link/1234/abcd?redirect=false&ip=189.65.238.39&ve=12.5&sng_ref=partnername_e2675724-0e90-4a80-8123-c3b66a681f3e
Was this article helpful?