Keitaro, Voluum and Binom postback from your Telegram CRM
If your campaigns run through a tracker, ScaleGram CRM sends it what happens on Telegram and at the broker: channel join, lead, registration, confirmed deposit. The tracker keeps the full view of your conversions, whatever the traffic source.
In short
ScaleGram calls your tracker’s postback URL, by GET or POST, on each event of the lead. Macros in braces ({sub1}, {event}, {value}, {currency}…) are replaced with the values of the click and the event. There is no dedicated module for Keitaro, Voluum or Binom: they all use this generic postback.
The principle: your click ID makes the round trip
- Your tracker sends the visitor to the campaign’s ScaleGram tracking link, adding its own click ID in a sub1 to sub5 parameter.
- ScaleGram stores that parameter with the click and gives the visitor their single-use Telegram invite link.
- On each event of the lead (join, lead, registration, deposit), ScaleGram calls your tracker’s postback URL, where {sub1} is replaced with the ID received at the start.
The name of the token that holds the click ID depends on your tracker: take it from its documentation and put it in the sub1 parameter of the ScaleGram link.
Available macros
| Macro | Value |
|---|---|
| {sub1} … {sub5} | The sub1 to sub5 parameters received on the click, for example your tracker’s click ID |
| {event} | The event name (by default join, lead, registered, deposit…) |
| {value}, {currency} | The amount and currency, for the deposit |
| {time} | The time of the event (Unix timestamp) |
| {click_id} | The click ID at ScaleGram |
| {campaign} | The ScaleGram campaign |
| {lead_id}, {telegram_user_id} | The lead’s ID in the CRM and their Telegram ID |
| {fbclid}, {ttclid}, {gclid}, {gbraid}, {wbraid}, {sccid}, {twclid}, {msclkid} | The ad networks’ click IDs, if they were in the URL |
| {utm_source}, {utm_campaign} | The click’s UTMs |
The events sent
Each CRM event can be sent to the tracker. By default, the channel join, the lead and the confirmed deposit are on; the join request, bot start, first private message and registration are available. The name passed in {event} can be changed rule by rule, to match your tracker’s statuses.
The deposit is sent only once confirmed, with its value. The registration is sent when the lead enters the pipeline stage you choose, or when the CellXpert sync reports it.
Keitaro
In Keitaro, the campaign sends traffic to the ScaleGram tracking link, with Keitaro’s click token in sub1. In ScaleGram, the postback destination gets the postback URL of your Keitaro installation, with the click ID replaced by {sub1} and the status by {event}.
Voluum
In Voluum, the offer points to the ScaleGram tracking link, with Voluum’s click ID token in sub1. In ScaleGram, Voluum’s postback URL gets {sub1} in place of the click ID, and {value} for the deposit amount.
Binom
In Binom, the offer points to the ScaleGram tracking link, with Binom’s click token in sub1. In ScaleGram, Binom’s postback URL gets {sub1} as the conversion ID, {event} for the status and {value} for the amount.
Setting up and testing the postback
- In the Tracking screen, add a postback destination: the URL with its macros, and the GET or POST method. With POST, all values are also sent in the request body.
- Click “Test”: ScaleGram calls the URL with a test event.
- Choose the events to send and their names.
- Only public http or https addresses are accepted; local and private addresses are refused.
- A failed send is retried after 1, 5, 30, 120 and then 720 minutes, then given up and logged.
- X (twclid) and Microsoft (msclkid) click IDs are recorded but have no direct send: the postback is the way to pass them on.
Frequently asked questions
Does ScaleGram have a native Keitaro, Voluum or Binom integration?
No. ScaleGram calls your tracker’s postback URL with macros. It is the method these trackers offer to receive conversions from an external source.
How does the tracker recognize the right click?
Your tracker passes its click ID in a sub1 to sub5 parameter of the ScaleGram link. ScaleGram sends it back in the postback with the matching macro, for example {sub1}.
Is the deposit amount passed on?
Yes, with the {value} macro, and the currency with {currency}.
Can I send events to several trackers?
Yes. Each destination has its own URL, and a campaign can send to several destinations at once, on top of Meta, TikTok or Snapchat.
GET or POST?
Both work. With GET, the macros are filled in the URL. With POST, the values are also sent in the request body.
What if my tracker does not answer?
The send is retried after 1, 5, 30, 120 and then 720 minutes, then given up. Sends and their responses are logged in the CRM.
See also
Telegram ad tracking
One Telegram invite link per click, sent back to Meta, TikTok and Snapchat up to the deposit.
Meta Ads
Server-side Conversions API and spend import per ad and per day.
TikTok Ads
Server-side Events API and TikTok spend import.
Snapchat Ads
Server-side Conversions API v3, from join to deposit.
Integrations
Telegram, ad networks, CellXpert, trackers and Google Sheets.
Create your workspace in a few minutes
Free during the launch, no credit card. Connect a Telegram account and your first leads land in the pipeline.