If you have ever set up integration tracker and PP, then you are aware that the tracker There is such a thing as postback: when a lead drops in the PP (or when the status of the lead changes), the PP engine (Cake, Affise, HasOffers, etc.) sends tracker a request that includes all data on the changes that have occurred. Tracker this query processes, updates the data and draws you a nice (or not so nice) statistic.
Tracker in this case, the receiving party. But (surprise, masefaka!), if you look closely at the settings of any campaign Keitaro or to the traffic source settings there, we will see there such a thing as S2S-postback. S2S stands for "server to server".
What is this beast? Turns out, tracker after receiving a postback from PP can send (roughly speaking duplicate) the postback to the address specified in the field above! "And what the hell do I need it?" you ask.
In general, you usually need this shit to send data to a traffic source. Yes, yes, some traffic sources know how to optimize campaigns based on the data received from your traffic source. tracker data, kind of like how fb optimizes traffic based on data from the pixel.
But we're going to use this feature in a way that's not quite intended: we'll create a bot in the cart that will email us every time something happens to our leads.
What follows is practically a copy-paste of the manual. Keitarobut who reads the manuals? Let's go!
- Go to the cart, search for the bot @BotFather and create a new bot using the command /newbot
- Set the names and save the resulting token
- Open a dialog with your bot, write any message to it.
- If you are in the Russian Federation, launch Tor Browser. If you are not, any other one will do.
- We need to get the id of the chat with our bot. To do this, make a request to the bot by writing the following in the browser address bar:
api.telegram.org/botREPLACE/getUpdates
where, instead of REPLACE you need to insert the bot's API token in the format 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11 - Look for the chat identifier in the received string
message":{"message_id":X, "from":{"id":ID
where, instead of ID will be your real id. - Send a message to the bot via API by typing the command in the address bar of the browser api.telegram.org/botREPLACE/sendMessage?chat_id=ID&text=text
where, instead of REPLACE you need to insert the API token of the bot, and instead of ID - received chat id - If everything is ok and the message arrived, you can use the received address as S2S postback in the campaign settings tracker or, if you want to make a postback for all campaigns, in the Traffic Source. An example S2S postback template can look like this:
https://api.telegram.org/botREPLACE/sendMessage?chat_id=ID&text={campaign_name}:{status}:{conversion_revenue}
where
{campaign_name} is the name of the campaign in the tracker,
{status} - conversion status,
{conversion_revenue} - conversion payout.
The full set of macros that can be passed in such a postback can be look here.
That's it! Now you can worry less about status and spend more time on approaches and funnel.
And with you was the Yellow Web, pour in the plus and send donatiks! ?? Hugs, everybody.