Also known as server-side, server call, server 2 server, s2s and, mistakenly, server pixel tracking, relies on the advertiser’s servers to track sessions generated on clicks to attribute conversions.  The servers record and then pass the transaction ID back to Mobidea Push. 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 Mobidea Push server. The server records the click, then generates and records the ID for that session (in most cases the click_id).
4. Mobidea Push immediately directs the user to the offer’s landing page, including ID for that session in the offer URL (click_id)
5. User sees offer’s page on advertiser’s site. 

When the user converts on that offer:

1. The advertiser’s server sends a signal to Mobidea Push (a.k.a. fires a postback) that includes the click_id that Mobidea Push initially supplied. The user is not directed back to Mobidea Push in any way.
2. Mobidea Push records the conversion for that session.

Implementation

Your tracking offer URL would then look something like this:

http://advertiser.com/?aff_sub={click_id}

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

http://advertiser.com/?aff_sub=push_71872t38713891u12u0313

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

• Postback URL: 
• The click_id for that session

The postback URL is:

https://s2s.mobideapush.com/conversion?click_id={click_id}

In the above URL, the advertiser replaces click_id with the click_id that they stored for that session. For example, if the advertiser had earlier received a click_id of “push_71872t38713891u12u0313” from Mobidea Push, then the postback URL becomes:

https://s2s.mobideapush.com/conversion?click_id=push_71872t38713891u12u0313

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