tellmetric
Affiliate

Telegram postback tracking: S2S deposits back to the ad that brought the subscriber

Affiliate funnels run on postbacks: the broker, casino or network fires a server-to-server request when a lead registers or deposits. In a Telegram funnel the click id has to survive a group, a chat and days of conversation before that postback arrives. This guide shows how it does, and how the deposit then reaches Meta or TikTok.

What a postback is, in a Telegram funnel

A postback is a server-to-server request sent by the system that sees the money. A broker or casino calls your tracker's URL with the click id it was given at registration and a status such as reg, ftd or dep, plus the payout. Trackers such as Keitaro, RedTrack and Voluum are built around it: clickid, status, payout, currency, txid.

On a website funnel the click id travels in the offer URL, so the broker has it from the first page view. In a Telegram funnel the person leaves the browser at the first tap. The click id has to be kept somewhere the broker can still get it, days later, when the person finally registers through a link posted in the channel or sent by a manager.

Carrying the click id into Telegram and out again

  1. The ad points at a tracking link. Tellmetric records the click, issues a click id and stores the fbclid or ttclid, the campaign parameters and sub1 to sub9 with it. The visitor goes into Telegram through their own single-use invite link or bot start code, so the join or the bot start is tied to that click id.
  2. The click id stays attached to the Telegram user. From then on the person is known by their Telegram account. Nothing expires: a deposit a month later is still looked up by the same click or the same Telegram user.
  3. The offer link carries it out. An offer link, a tracked link you post in the channel, pin in the bot or let a manager send, is filled per click with {clickid}, {utm_*} and {sub1}…{sub9} macros, so the broker's registration page receives the click id in its own parameter, exactly as it would from a website.
  4. The broker fires the postback to Tellmetric's postback URL with that click id, the status and the payout. The deposit lands on the click's campaign, ad set and creative.
  5. The deposit goes to the ad platform as a Purchase with value and currency through Meta's Conversions API, TikTok's Events API and the others, with the original click id, so the platform can optimise for depositors.

The postback URL

One GET request per event. The grammar is the one affiliate trackers use, so a Keitaro or RedTrack template drops in without changes:

Postback URL
GET https://www.tellmetric.com/postback?clickid={clickid}&status=ftd&payout=100&currency=EUR&txid={transaction_id}&api_key=YOUR_KEY
  • status: lead, contact, reg, dep, ftd or sale. ftd and dep become a Purchase with value; reg a registration; lead a lead.
  • txid is part of the event id, so a repeated postback for the same deposit is ignored while a second deposit from the same person is counted.
  • The key goes in the URL for trackers that cannot set headers, or in an Authorization: Bearer header from your own backend.
  • Email or phone, if the broker has them, can be added and are hashed before storage; they raise the match rate on Meta.

The exact URL with your key, the Keitaro and RedTrack/Voluum templates and the event API are on the developer page.

Sending postbacks onwards

Many teams keep their main tracker. Tellmetric can forward every join, message and deposit to it as an outbound postback, with a template of your choosing, for example https://your-tracker/postback?cid={clickid}&status={status}&sum={payout}, so the Telegram part of the funnel shows up in Keitaro or Binom next to the rest. Deliveries are logged and retried.

Where it breaks, and how to tell

  • The offer link was shared without a tracked link. A plain broker link in the channel carries no click id, so the postback arrives with an empty one and cannot be attributed. Post offer links created on the Links page.
  • The broker sends its own id, not yours. Map the macro: the value in clickid must be the one Tellmetric put into the offer link. The response to a test postback states whether the click was matched.
  • Postbacks arrive in a batch days later. Meta refuses events older than seven days; send them as they happen.
  • Two trackers count the same deposit. If the broker also postbacks to Keitaro, keep Tellmetric as the one that reports to the ad platforms, or deduplicate by txid.

Frequently asked

Which postback format does Tellmetric accept?

The clickid / status / payout / currency / txid grammar used by Keitaro, RedTrack, Voluum and most networks, as a GET request with the key in the URL or a bearer header.

Can the postback be matched by Telegram user instead of click id?

Yes, through the event API: send the depositor's Telegram user id and the deposit is attributed to the click that user arrived with.

Does Tellmetric replace my tracker?

It replaces the part a web tracker cannot do: following the click into Telegram and back out. Keep your tracker for routing and offers and let Tellmetric forward events to it, or run Tellmetric alone.

Which platforms receive the deposit?

Meta on every plan; TikTok, Snapchat, Reddit, Spotify, X and Google Ads on Pro and Agency, each as its purchase event with value.

Related guides

Track Telegram and Discord conversions from your ads

The Free plan requires no card. Upgrade to Pro at any time.