S2S — Server-to-Server

With browser tracking, a pixel or cookie on the advertiser's page records the conversion. Ad blockers, browser restrictions and cookie refusals break that kind of counting.

With S2S, the click ID is stored on the advertiser's server alongside the order or sign-up, and the network learns about the conversion by postback. ThanklyClub works exactly this way: the link to the partner carries the click ID, and the conversion arrives by postback.

Example

For example, out of 100 conversions a browser pixel would see maybe 80, because some shoppers have blockers. With S2S all 100 land in the report, as long as the partner sent a postback for each.

How to calculate it / how it works

The scheme: a click → the network issues an ID → the partner's server saves it with the order → when the person acts, the server itself reports it to the network. The shopper's browser plays no part in the transfer.

For example, in a month there were 100 conversions. Step 1: 20 shoppers have blockers or cookies turned off. Step 2: a browser pixel sees 80 conversions. Step 3: with S2S the partner's server passes all 100, if it sent a postback for each. The 20-conversion difference is money you would not have had with a pixel.

Where it shows up in ThanklyClub and common mistakes

For a partner, S2S comes down to one obligation: save sub together with the sign-up or order and send it back in the postback. Without the ID, the network cannot match the conversion to a click, and there is nothing to pay.

• Sending the postback before the order is saved in the database, and losing the link to the click.
• Not retrying after a server failure, so the conversion is lost. A repeat postback with the same sub is safe: it updates the record.
• Keeping a pixel "just in case" and getting mismatches in the reports.
• Not logging the postbacks that were sent, and being unable to sort out disputed cases.

FAQ