Attribution Integrations: Client-Side and Server-Side (S2S)

Client-Side Attribution

A client-side attribution is the most common of the mobile attribution integrations. This is the recommented integration method with Singular. It allows the advertiser to use their configured destinations in Singular and enables full use of Singular SmartTag and destinations.

The attribution flow is as follows:

  1. User clicks on an ad which served via an ad network's conversion pixel.
  2. The ad network conversion pixel redirects to Singular's attribution tracking URL.
  3. Singular tracks the click and serves a redirect to the app store or a deep-link.
  4. User downloads and opens the app.
  5. The install is tracked by Singular and the last click for the device is awarded the attribution.
  6. Any configured install postbacks are distributed.

Snip20180820_55.png

Server-Side Attribution

An S2S integration has the same flow as a client-side attribution, with the exception that the ad network performs the app store or deep-link redirect, and Singular click notifications are served by an ad network server.

The attribution flow is as follows:

  1. User clicks on an ad which served via an ad network's conversion pixel.
  2. The ad network server receives the click, serves a redirect back to the device, and sends Singular a click notification.
  3. Singular tracks the click.
  4. User downloads and opens the app.
  5. The install is tracked by Singular and the last click for the device is awarded the attribution.
  6. Any configured install postbacks are distributed.

Snip20180819_50.png

 In order to send Singular clicks from server-side it is mandatory to append IP address and OS version using these parameters:

  • "ip" - raw IP address
  • "ve" - version of the OS on the device ( e.g 9.2)

Always append "&redirect=false" to the tracking link.

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