Skip to main content
All CollectionsFAQ
S2S Postback Configuration
S2S Postback Configuration

What the S2S Postback is and how to use it to track conversations and ROI

David Martínez avatar
Written by David Martínez
Updated over 5 years ago

What is the S2S Postback?

The S2S postback also referred to as a server-side, server call, server 2 server and sometimes mistakenly as server pixel tracking (that's something else). This is the signal from the advertiser's servers back to the Pushground servers signifying that there has been a conversion. This method is independent of the user’s browser. Postback tracking can be thought of as two separate processes: what happens when a user clicks on an offer and what happens upon conversion.

Leading up to the conversion:

  1. User sees an offer.

  2. User clicks on the offer.

  3. Click goes to a Pushground server. The server records the click, then generates and records the ID for that session (in this case the click_id).

  4. Pushground immediately directs the user to the offer’s landing page, including ID for that session in the offer URL (click_id)

  5. User sees the offer’s page on the advertiser’s site. 

When the user converts on that offer:

  1. The advertiser’s server sends a signal to Pushground (a.k.a. fires a postback) that includes the click_id that Pushground initially supplied and amount or the payout of the offer. The user is not directed back to Pushground in any way.

  2. Pushground records the conversion for that session.

The  S2S Postback is important so we can display the health of your campaigns and help to optimize your revenue.  The click_id tells us which user converted so you can optimize towards that supply source and towards the creative they saw. The amount (payout) allows us to show you the profitability of your campaigns so you can quickly and effectively manage your campaigns. 

Implementation

Your tracking offer URL would then look something like this:

http://advertiser.com/?your_paramater={click_id}&amount={payout}

After Pushground fills in values for the macros, the user is directed to a URL that looks similar to this:

http://advertiser.com/?your_parameter=push_71872t38713891u12u0313&amount=5

When a user completes a conversion on an advertiser’s site, the advertiser needs to tell Pushground about the conversion. We call this “firing a postback”. The advertiser’s site does this by sending a signal to our servers that uses three elements:

3 Elements of the Postback

  • Postback URL: 

  • The click_id for that session

  • The amount of the payout

The postback URL is: (REPLACE WITH PARAMETER YOU ARE USING FOR CLICK_ID AND THE PAYOUT FOR THE PAYOUT OF THE OFFER)

https://lupush.com/conversion?click_id={your_paramater}&amount={payout}

In the above URL, the advertiser replaces click_id with the click_id that they stored for that session and the amount of the payout. 

For Example

 If the advertiser had earlier received a click_id of “push_71872t38713891u12u0313” from Pushground and the payout of the offer was $5.00, then the postback URL becomes:

https://lupush.com/conversion?click_id=push_71872t38713891u12u0313&amount=5

Important: You will receive a “200 OK” HTTP response code if we attempt to process the postback, even if unsuccessful. This lets you know Pushground received the request, and to not resubmit it as you might for a 4xx or 5xx response code.

Did this answer your question?