Keitaro Unity Ads postbackDeposits next to Unity spend.
Set up one S2S postback in Keitaro and every registration and deposit of your Unity traffic lands in Ramet, on the campaign, geo and source that brought it.
Set it upin five steps.
Carry the Unity macros in the link
In the offer or landing link that Unity sends traffic to, put the Unity macros into Keitaro sub parameters, for example sub_id_1 for the campaign ID, sub_id_2 for the country and sub_id_3 for the source app ID.
Tell Ramet which sub is which
In the postback settings of Ramet choose Keitaro and enter the mapping: which sub carries the campaign ID, the country and the source app ID. Ramet reads deposits by this mapping and does not guess.
Paste the URL into Keitaro
Copy the postback URL Ramet builds for you and add it as an S2S postback on the Keitaro campaign. It already carries the Keitaro macros for the click ID, the status and the payout.
Send a test event
Press Check in Ramet, trigger a test conversion and see how every field was read. A macro that was not filled in is shown as it came, so you can fix it before real deposits arrive.
Open the analytics
Deposits join the analytics rows of the same campaign, geo and source, next to Unity spend.
The link Unity sends traffic to
Unity fills its macros in at click time. Keitaro keeps them in sub_id parameters.
https://your-domain/click?sub_id_1={campaign_id}&sub_id_2={country_code}&sub_id_3={source_app_id}The postback URLas Ramet builds it.
This is its shape. Ramet fills in your host and your token, and you only copy it.
https://<host>/pb/<token>?m=other&v=3&tid={tid}&event={status}&payout={revenue}&ts={conversion_time}&cid={sub_id_1}&geo={sub_id_2}&src={sub_id_3}Which macrofeeds which field.
Each parameter of the URL takes a Keitaro macro. The sub values follow the mapping you set.
| Parameter | Macro | What Ramet reads |
|---|---|---|
| tid | {tid} | The click or event ID, so a repeated postback is counted once. |
| event | {status} | The raw status: registration, deposit and the like. |
| payout | {revenue} | The payout of the event. |
| ts | {conversion_time} | When the event happened. |
| cid | {sub_id_1} | The Unity campaign ID. |
| geo | {sub_id_2} | The country. |
| src | {sub_id_3} | The source app ID, so a deposit is placed on its source. |
The exact URL and macros of your Keitaro version come from Ramet. The shape here is an example.
What you getin Ramet.
Deposits by campaign, geo and source next to Unity spend, the cost per deposit of each row, and rules that can act on it.

Questionsabout this page.
Where do I add the postback in Keitaro?
On the S2S Postbacks tab of the campaign. Paste the URL from Ramet there and choose the statuses that should be sent.
Why does the payout have to be sent explicitly?
A Keitaro campaign with automatic payout can report a revenue of 0 in the macro. The URL from Ramet carries the payout macro explicitly so the value arrives.
Do I need a Keitaro API key?
No. Deposits come in by postback, so Keitaro only needs the URL.
Also in RametFour more places to look.

Tracker integrations
Deposits from Keitaro, Binom, DarkCore CRM and DarkCore PWA by postback.

Analytics
Spend, installs and cost per deposit by campaign, geo, app and source.

Auto-rules
Rules that pause a campaign, block a source app or lower a bid for you.

Cabinets
Every Unity org in one workspace, each with its status and who can use it.
Launch your next 36 campaigns today.
Connect a cabinet, pick a bundle, press launch. We are on Telegram if you get stuck.