Postbacks for CPA Merchants

Mandatory for merchants on Kukuruku (club)

If you are integrated with Kukuruku and your project is listed on the club, sending these postbacks is mandatory, not optional. FTD and RD postbacks are required for every merchant; Revshare applies to hybrid deals only.

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_id is passed as cid and 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

Goal	goal_alias	When to send	Postbacks	Status flow	Applies to
FTD	ftd	First successful deposit	2 (event + confirmation)	pending → approved / rejected	All merchants
RD	rdep	Every deposit after the FTD	1 per deposit	counted immediately	All merchants
Revshare	revshare	Per revenue event	1	counted immediately	Hybrid deals only

FTD — First Time Deposit

The player's first successful deposit at the merchant. Send this postback once per player, on the very first deposit that is confirmed as successful on your side.

FTD uses a two-phase flow: first you register the event (it lands as pending / on hold), then you confirm or reject it after qualification. Both postbacks are linked by the same click_id.

https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}&currency={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}&currency={currency}&token={token}&goal_alias=ftd&conv_status=approved

• conv-change is for conversion status change, use the same click_id as in the first postback.
• conv_status can be approved or rejected.
• currency must match the user's deposit currency.

RD — Repeat Deposit

Every deposit after the FTD for the same player at the merchant. Send one RD postback per repeat deposit. The payment method and which side initiated the deposit do not matter — any successful deposit beyond the first qualifies.

https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}&currency={currency}&token={token}&goal_alias=rdep

Revshare* — Revenue Share

Optional. Applies only to merchants on a hybrid deal. If you don't run a hybrid model, you don't send this postback.

https://trk.track-app-18.today/track/conv?click_id={click_id}&amount={sale_amount}&currency={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 identifier
• amount: deposit amount
• token: verification token (request from our team)
• goal_alias: static goal aliases: reg (registration), ftd (first deposit), revshare, rdep (repeat deposit)