Binom Unity Ads postbackDeposits next to Unity spend.
Set up one postback in Binom 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 link that Unity sends traffic to, put the Unity macros into Binom tokens, for example t1 for the campaign ID, t2 for the country and t3 for the source app ID.
Tell Ramet which token is which
In the postback settings of Ramet choose Binom and enter the mapping: which token 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 Binom
Copy the postback URL Ramet builds for you and add it as a postback on the Binom traffic source or on the campaign. It carries the Binom tokens for 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 token 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. Binom keeps them in the tokens t1 to t10.
https://your-domain/click?t1={campaign_id}&t2={country_code}&t3={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={clickid}&event={cnv_status}&payout={payout}&cid={t1}&geo={t2}&src={t3}Which macrofeeds which field.
Each parameter of the URL takes a Binom macro. The sub values follow the mapping you set.
| Parameter | Macro | What Ramet reads |
|---|---|---|
| tid | {clickid} | The click or event ID, so a repeated postback is counted once. |
| event | {cnv_status} | The raw status: registration, deposit and the like. |
| payout | {payout} | The payout of the event. |
| cid | {t1} | The Unity campaign ID. |
| geo | {t2} | The country. |
| src | {t3} | The source app ID, so a deposit is placed on its source. |
The exact URL and macros of your Binom 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 Binom?
On the traffic source or on the campaign, wherever you keep postbacks. Paste the URL from Ramet and choose the statuses to send.
Which Binom tokens carry the sub values?
Binom keeps sub values in the tokens t1 to t10. You choose which token holds the campaign ID, the country and the source app ID, and tell Ramet in the mapping.
Do I need a Binom API key?
No. Deposits come in by postback, so Binom 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.