Playbook: Wire a broker S2S postback that doesn't double-count FTDs

Playbook: Wire a broker S2S postback that doesn't double-count FTDs

What it is: A step-by-step setup for server-to-server postbacks from a broker panel into your tracker so a First Time Deposit fires once, attributed correctly.

Best for: Media buyers running forex/CFD offers where the advertiser pays per FTD, not per signup.

The steps:
— Pull the broker's postback macro list first. You need at minimum {click_id}, {event}, {amount}, {currency}, {txn_id}. If {txn_id} is missing, ask before sending traffic — you can't dedup without it.
— Map click_id to your tracker's sub parameter (Voluum: cid, Keitaro: subid, Binom: clickid). Pass it on the click-out URL, never hardcode it.
— Set the postback to fire on event=ftd only. Many panels also fire on 'lead' and 'registration' through the same URL — filter by {event} or you'll inflate.
— Add a dedup rule keyed on {txn_id}, not click_id. A user can re-deposit; same txn_id should reject.
— Test with the broker's sandbox or a $10 live deposit before scaling. Log the raw postback, don't trust the dashboard count.

Pros:
— Real-time FTD data lets you cut losing zones same-day
— txn_id dedup survives re-deposits and panel retries

Cons:
— Some smaller brokers send no txn_id; you're stuck trusting their count
— Currency conversion on {amount} can drift if you don't normalize

Who should skip this: Anyone on a flat CPL deal — postback complexity buys you nothing without revenue events.

Verdict: Dedup on txn_id, always.