Client-side and Server-side (S2S) Integration

 

 

Client-side Attribution

A client-side attribution is the most common of the mobile attribution integrations. This integration is recommended and allows the advertiser to use their configured destinations in Singular, as well 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 networks' conversion pixel

(2) Ad-Network conversion pixel redirects to Singular attribution tracking URL

(3) Singular Tracks the click and serves a redirect to the app store or deep-link

(4) User downloads and opens the app

(5) Install is tracked by Singular and the last click for the device is awarded the attribution.

(6) Any configured install postback 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 networks' conversion pixel

(2) Ad-Network server receives the click, serves a redirect back to the device and sends Singular notification of a click

(3) Singular tracks the click

(4) User downloads and opens the app

(5) Install is tracked by Singular and the last click for the device is awarded the attribution.

(6) Any configured install postback are distributed.

 

Snip20180819_50.png

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.