How do I use S2S Conversion Tracking?

In addition to conversion tracking via a pixel, which must be installed on the advertiser's website, there is now server-to-server conversion tracking as an alternative.

With server-to-server conversion tracking (also known as: Server2Server, S2S Tracking, Postback Conversion Tracking) the pixel is no longer called from the user's browser, but the advertiser's server calls the conversion tag (the "pixel"). Since there are problems with 3rd party cookies in more and more browsers, Postback Conversion Tracking is a good alternative to pixel tracking.

Is S2S tracking relevant to you?


  • No cookies are required
  • Conversions can be tracked more reliably, as pixels are not suppressed by the browser.
  • The request is only sent to AdUp in the event of an actual conversion
  • Downloads from the iOS AppStore or the Google Play Store, as well as in-app events, can be tracked.


  • Effort for the advertiser during implementation
  • View conversions cannot be measured
  • More difficult to test

Requirements and installation

The installation of server-to-server tracking is somewhat more complicated, as technical adjustments must be made. Thus, this form of tracking is only recommended for experienced users.

The following steps are necessary for use:

  • The advertiser must provide a tracking server that stores the transaction_id in the case of the click and retrieves it again in the case of the conversion.
  • The transaction_id must be passed to the final url. For this purpose, there is a placeholder "{transaction_id}", which can be used in the suffix of the final click url in the URL options of the advertiser account. The parameter can be named anything (e.g. t_id={transaction_id}). It must only be able to be processed by the advertiser.
  • The advertiser's server must save this parameter and pass it to AdUp with the conversion request in the event of a conversion.
  • For example: