Skip to content
English
More support
  • There are no suggestions because the search field is empty.

Server-to-Server (S2S) Tracking

Getting Started with Server-to-Server Tracking

Server-to-server tracking (S2S), also known as postback URL tracking, works by generating and storing a unique identifier of some kind when a user clicks a tracking link, like our click IDs. When the same user later makes a conversion, the click ID is matched back to the user. This is done by posting that same unique identifier back to the tracking server.

We usually recommend using server-to-server tracking for advertisers whose websites can send a signal back to FlexOffers through their code. This process is also known as firing a postback and is more reliable than other tracking methods.

Instructions for S2S Tracking

When a user lands on your page, you need to capture the reference ID (RefID), which is a unique identifier for each visit. You can capture the RefID from a query string parameter that we place in the URL when we send users to the destination.

Example: https://examplesite.com?refid=110097545FOF41509727756072518

How to Save the Unique Reference ID

There are several ways you can store the RefID. One method is to generate a cookie on the landing page that carries through the duration of the transaction. Another method is to log the transaction ID as a hidden variable. A third method is to continue carrying the transaction ID as a URL parameter until the conversion completes. 

Using the example URL provided earlier, you would capture the RefID value and add it to the server-to-server URL. The URL should be changed in a programmatic process to look like the example below and then fired:

https://track.flexlinks.com/da.ashx?advertiserid=XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX&clickid=[refid]&orderamount=&ordernumber=&coupon=&currency=&geo=&commissionid=

  • Fill in the "ordernumber" parameter with an order number. It should be unique with each fire.
  • Fill in the "orderamount" parameter with a sale amount. It should update dynamically with each fire. If you’re running a cost-per-lead (CPL) campaign, you can put in "orderamount=0".

Note: The required parameters are order amount and order number. The optional parameters are coupon, currency, geo, and commission ID.

After everything is implemented, we need two tests to ensure all processes are working properly.

Articles in this section