Postbacks for CPA Merchants
This guide describes how to send S2S postbacks for conversion tracking, ensuring reliability and accuracy.
User Redirect Link Example
https://yourdomain.com?order_id={custom2}&kukuruku_login={custom3}&auth_url={custom4}&cid={click_id}&auto_login={custom3}
click_idis passed ascidand must be stored for the user. It is the main user identifier for us.- Other parameters are for user authorization on your side.
Expected Postbacks
FTD
https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}¤cy={currency}&token={token}&goal_alias=ftd
By default, FTD comes with status pending. After qualification, send:
https://trk.track-app-18.today/track/conv-change?click_id={click_id}&amount={sale_amount}¤cy={currency}&token={token}&goal_alias=ftd&conv_status=approved
conv-changeis for conversion status change, use the sameclick_idas in the first postback.conv_statuscan beapprovedorrejected.currencymust match the user's deposit currency.
RD
https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}¤cy={currency}&token={token}&goal_alias=rdep
Revshare*
https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}¤cy={currency}&token={token}&goal_alias=revshare
*amount is the revshare sum. By default, we expect 100% and multiply on our side, but this can be adjusted. Valid for hybrid deals only.
Postback Parameters
click_id: main player identifieramount: deposit amounttoken: verification token (request from our team)goal_alias: static goal aliases:reg(registration),ftd(first deposit),revshare,rdep(repeat deposit)