Binary Options Postback: Track FTDs from Telegram

If your operation promotes a binary options broker through a Telegram signals channel or group, you have the same problem as iGaming: the channel entry isn’t the conversion that matters — the first deposit (FTD) at the broker is. That’s what a binary options postback solves. One person can enter the channel, follow the signals and never open an account or deposit; another deposits the same day. Without visibility of the deposit, Meta Ads (or any ad platform) has no way to tell the two apart.

This guide assumes you already track channel entries (see the complete guide to tracking Telegram conversions) and focuses on closing the loop all the way to the deposit at the broker, via postback — the same mechanism described in the iGaming S2S postback guide (and part of a full iGaming paid traffic structure), adapted here to binary options.

Why the channel entry isn’t enough for binary options

Binary options signals channels commonly see a relatively high volume of entries — curious people, testers, people comparing channels — and a much lower share of people who actually open a broker account and deposit. Optimizing a campaign only for the entry event, with no visibility of the deposit, tends to scale toward the “curious person who joins”, not toward the one who actually becomes a paying broker client.

Picture two traffic sources with the same 1,000 entries in a month (illustrative numbers): one produces 15 FTDs, the other 60. Measured by entries alone, they look identical — and you’d keep splitting budget evenly between them.

Tracking origin works for ads, partnerships and organic alike

Binary options signals channels usually grow through a mix of paid ads, referrals, partnerships with other channels and free content that pulls people into the paid (VIP) channel. The broker’s postback works the same way wherever the lead comes from — the “campaign” of origin may be an ad, a partnership or a mention in another channel. Unless every ad, partnership or piece of content sends people to your funnel’s bridge page (or its entry link) with its own UTMs — or through a separate funnel when the path is different — it’s impossible to know which one actually brought in subscribers, versus which one only brought in curious volume; a channel link shared directly (t.me/...) stays outside tracking. With UTMs, each channel entry shows up with its origin, lead by lead, in Track4you’s metrics report. On the deposit side, the logic is the same for every source: what closes the loop is the lead going through the integration’s promo link on the way to the broker.

What a postback is (quick recap)

A postback is a server-to-server (S2S) notification: when an event happens on the broker’s side (sign-up, first deposit, subsequent deposits), an HTTP call is fired automatically to a URL you configured beforehand, carrying the identifier of the original click (click_id) along with the event type and, for deposits, the amount.

The full flow, from click to deposit

1. From click to channel entry

The ad, partnership or post carries its UTMs and points to your capture page, which has Track4you’s script; the button uses the funnel’s entry link, which takes the person to the signals channel. When they join, the tracking bot detects the entry and enter_channel reaches your pixel, attributed to the click within the attribution window (see the Facebook Pixel and CAPI guide for Telegram for this specific piece).

2. The integration’s promo link goes in the channel

Inside the channel — pinned message, description, posts — the link to the broker isn’t the raw affiliate link: it’s the promo link of a Track4you integration (https://t4y.io/v2/...), whose redirect destination is the broker’s sign-up page with your affiliate link.

3. The click creates the click_id and leads to sign-up

On every click, Track4you creates a unique click_id and redirects the person to the broker’s sign-up page with that value in the URL, in the parameter you pick as the integration’s URL identifier — click_id (default), afp, a UTM or a custom name such as subid or aff_sub — matching the parameter in which the broker reads the affiliate sub ID. The broker stores the value with the new account; nobody has to carry anything forward by hand.

4. The broker fires the postback

When the sign-up, the first deposit (FTD) or a subsequent deposit happens, the broker calls the matching integration’s postback URL (a server-to-server GET), sending back the same value. The key is always click_id=, followed by the broker’s own macro; for FTD and deposits it also sends the amount, with a dot as the decimal separator. Each event type has its own integration and its own postback URL.

5. Track4you sends the conversion to the pixel

Track4you recognizes the click_id and sends the conversion to the Meta pixel chosen in the integration, server-side through Meta’s Conversions API (CAPI): sign-up as CompleteRegistration, FTD as the custom event FTD (confirmed once in Events Manager) and deposits as Purchase, with the amount — closing the loop: click → channel entry → deposit. There’s no time limit on Track4you’s side: a deposit that arrives through the postback weeks after the click still goes to the pixel and becomes signal for the algorithm; whether it’s credited to a campaign in Ads Manager depends on Meta’s attribution window (default: 7 days after the click or 1 day after the view).

Setting up the binary options postback at the broker

Just like in iGaming, most brokers with an affiliate program expose a postback URL field per event in the affiliate dashboard. In Track4you (Pro and Enterprise plans), you create one integration per event, send the integration’s test event with the test code from Events Manager, copy the promo link and the postback URL, and paste that URL into the matching event at the broker, replacing {{click_id}} and {{value}} with the broker’s macros. Map the available events carefully:

• Sign-up: account opened, no deposit yet — arrives as CompleteRegistration.
• FTD (first time deposit): usually the most important event for optimization — it’s also the event many CPA deals pay on — and it arrives as FTD.
• Subsequent deposits: more relevant for recurrence/LTV metrics (and RevShare reporting) than for acquisition optimization — with the Deposit event type, they arrive as Purchase.

Also check the currency the deposit amount is reported in — brokers serving multiple markets may report in different currencies, and amounts in different currencies added up in the same event distort your ROAS reading.

How to check that the postback is working

Make a test sign-up and deposit (with the minimum amount) through the promo link and check: whether the integration’s status changed from waiting for data to receiving data, whether the conversion shows up in the integration’s event history (you can search for the click_id copied from the sign-up URL), and whether the event reached Meta’s Events Manager with the right name — the first deposit as FTD, not as Purchase — and the correct amount. To test only the connection to Meta, use the integration’s test event: firing the postback URL by hand with a real identifier counts as a real conversion.

Common mistakes in this setup

• Posting the raw affiliate link in the channel: without going through the promo link, the sign-up reaches the broker with no click_id, and the postback has no click to be tied to. The same happens if the integration’s URL identifier isn’t the parameter the broker reads.
• Not separating sign-up from FTD: pasting the same postback URL on both events counts them as the same event, inflates the number of “conversions” and distorts the real CPA.
• Edited postback URL or renamed key: changing the domain, the code after /event/ or the event= value, or renaming click_id=, means the call isn’t recognized — silently, with the integration stuck waiting for data or flagged as invalid.
• Reading only Ads Manager: a deposit that happens days after the click reaches the pixel, but it’s only credited to the campaign if it falls inside the Meta attribution window set on it — the total that came in through Integrations is on the FTDs and Deposits cards of Track4you’s Dashboard.

Build it yourself or use a ready-made tool?

Building this in-house means linking each channel entry to its click on your own, creating an identifier per click and passing it to the broker in the right parameter, keeping an endpoint that receives postbacks, matching each postback to the right click and firing the CAPI call with the right name and value — ongoing engineering work that grows with the number of campaigns. A dedicated tool solves this out of the box: you paste the postback URL at the broker, with matching and event delivery already handled.

How Track4you handles it out of the box

With Track4you Integrations (Pro and Enterprise plans), the promo link creates the click_id and delivers the lead to the broker’s sign-up page with it in the URL; the broker sends that value back on the postback URL; and Track4you sends the conversion to your Meta pixel — CompleteRegistration, FTD or Purchase, depending on the event type — with no matching logic to build by hand. Each integration’s status and its event history show whether postbacks are arriving.

Frequently asked questions

Terms like click_id, CAPI and postback have a quick definition in the glossary.

Conclusion

For binary options, just like for iGaming, tracking the channel entry solves only half the problem — the other half is closing the loop all the way to the deposit at the broker. The mechanism is the same (S2S postback + CAPI) whatever the vertical; the only thing that changes is who fires the notification on the other side. And it holds wherever the lead comes from — ads, partnerships or organic: with UTMs on the way to the channel and the promo link on the way to the broker, every channel entry shows its origin and every deposit makes it back to the pixel tied to the promo-link click.