Postback for media placement

1. Introduction

• client - server
• server - server

Client — server is used when user's action results in lead while user is interacting with the page, e.g. when lead is meant to be filling in the registration form.
Server — server is used when user is not interacting with the page while performing a lead, e.g. when lead is meant to be a confirmed order. It means that before lead will be counted, call center operator must call user and at this very moment user does not interact with the page in any way. Therefore advertiser's server interacts with MediaSniper server by transferring display ID.
The postback call's key point is — notification of a lead. All the traffic sent by MediaSniper contains a unique display ID in get parameter. It is called «s_trk». In order to inform about lead you need to return to MediaSniper s_trk get parameter of user that has performed lead.
Client — server allows to save a key in the cookie and read it at the time of performing a lead.
Server — server requires to store user's ID that helps to identify users and it must comply with s_trk.

2. Example of postback link

http://pback.mediasniperleads.com/ap_back_url.php?type=accept&pid={partner_ID}&plus={revenue}&s_trk={s_trk}&apid={trans_id}

❗️

PLEASE NOTE:

IT IS CRITICALLY IMPORTANT TO TRANSFER S_TRK PARAMETER VALUE WHEN CALLING THIS LINK

{partner_ID}	Partner ID in MediaSniper system. site_{site_name} where {site_name} for test.ru — testru can be used by default Finally - site_testru
{revenue}	Lead cost. If it is a test campaign, or if lead cost was not discussed separately, "1" can be transferred.
{s_trk}	Value of s_trk get parameter assigned to user. Example of s_trk: ChRhZHA0WncRerU-EeSLfgElkJWCShCpsuuqDBjNw4OnBSDkw4OnBQ
{trans_id}	Unique transaction number. If transactions are not separately tracked, then Unix Time Stamp can be transferred to this field.