Tracking Deposits From Telegram Leads Back to the Ad

Why deposits are difficult to attribute

In a web store, the purchase is recorded on a confirmation page by the pixel. A Telegram funnel has no equivalent page. The deposit may be recorded in a broker's back office, a payment provider, a Stars invoice inside the bot, or a spreadsheet maintained by a sales team, and it usually occurs well after the ad click. Unless the click id has been retained throughout, the deposit cannot be assigned to the campaign that produced it.

What must be recorded

The click id issued at redirect time, together with its campaign, ad set and creative.
The Telegram identity that later joined or sent a message, linked to that click id.
The deposit itself: amount, currency, transaction id and time.
Any identifier known to the payment system, such as an email address or phone number, hashed for matching.

Setup

Place a tracking link behind every ad so each click receives its own id before the visitor reaches Telegram.
Send the visitor into Telegram with a link that carries the id, and have the bot record the join or first message against it.
Give your deposit source (a tracker, CRM or payment gateway) a postback URL that includes the click id.
On postback, look up the click, inherit its identifiers and send a Purchase event with value and currency to the ad platform.
Include the transaction id in the event id so a repeated postback for the same deposit is ignored, while a second deposit from the same person is counted.

Illustrative example

The following sequence is illustrative. A Meta ad sends a visitor through a tracking link on 3 March. The link issues click id c_8Xk…, records the fbclid and UTM campaign, and opens the bot. The visitor joins the VIP group the same day, which Tellmetric reports as a registration. On 14 March the broker's system calls /postback?clickid=c_8Xk…&status=dep&payout=200¤cy=EUR&txid=90412. Tellmetric matches the click, attaches the hashed Telegram id and the customer's hashed email, and sends a Purchase event worth €200 to Meta under the original campaign. The deposit is attributed correctly eleven days after the click.

Common points of failure

Recording deposits only in the CRM. Your team sees the revenue, but the ad platform continues to optimise for clicks.
Using the same Telegram invite for every campaign, so a deposit can be tied to a person but not to a traffic source.
Reporting a purchase without a value. Meta counts it but cannot bid towards revenue.
Relying on a weekly export. Meta rejects events older than seven days, and delayed events weaken optimisation.
Matching only on a name entered by a sales representative. Ad platforms match on hashed email or phone number.

How Tellmetric attributes deposits

Tellmetric keeps the click attached to the Telegram user for the full length of your sales cycle. A deposit can be reported in four ways: the standard postback format used by affiliate trackers such as Keitaro, RedTrack and Voluum, the /track/event API from your own backend, a hosted confirmation form, or a Telegram Stars payment received by your bot. Each is mapped to Purchase, enriched with hashed email, phone or external id when supplied, deduplicated by transaction, and delivered to Meta, TikTok, Snapchat, Reddit, Spotify and Google Ads. Refunds and chargebacks are recorded but never reported as conversions.

Frequently asked questions

My deposits come from a broker who only knows a sub-id. Is that supported?

Yes. Pass the Tellmetric click id as the sub-id when you send the visitor onward, and have the broker return it in the postback's clickid field.

Can I report the first deposit separately from later ones?

Yes. Use status=ftd for the first deposit and status=dep for subsequent ones. Both are sent to Meta as Purchase; the dashboard reports them separately.

What about payments inside the bot?

Telegram Stars payments are recorded automatically when the invoice payload carries the click id, so no postback is required.

Tracking deposits from Telegram leads