How to track conversions from Telegram ads

Telegram's self-serve ads document no pixel or click ID and can't link to websites. How to track sign-ups and sales anyway: one start code per ad, the bot, and your tracker.

By Andrej Ruckij · · 9 min read

How do you track conversions from Telegram ads?

By Andrej Ruckij · November 15, 2026 · Telegram, Meta and Google docs checked the same day

TL;DR: Telegram’s self-serve ad platform documents no pixel and no postback, and its ads link only to a channel or bot on Telegram, so you can’t put a tracker redirect in front of the ad the way you would elsewhere. What carries the ad’s identity is a ?start= code on the bot link, one code per ad, plus the Telegram user ID the bot sees when someone presses Start. Store those two together, and every later event (a sign-up, a sale, a block) can be traced back to the ad. Your tracker’s own click ID starts one step later, on the link the bot sends to your landing page. Telegram’s dashboard shows views and joins or bot starts. Whether it shows clicks isn’t documented, so I wouldn’t plan around it.

We set up this tracking for clients as part of running their Telegram ads: Telegram ads at Primores.

What Telegram’s dashboard tells you

Less than you’d hope. Telegram’s getting-started page says the Statistics tab shows “overall views” and a graph of “views of your sponsored message and the number of times a user joined your channel or started the bot after viewing the sponsored message” (Telegram).

That’s it. Neither that page nor the ads homepage mentions conversion tracking, a pixel, a postback or an attribution window (Telegram Ads).

Clicks are the odd one. Telegram’s API docs tell its apps to report a click when someone taps the ad (Telegram API), so Telegram has the data. The getting-started page doesn’t list clicks in the dashboard, and third-party guides disagree about whether they show up. I’d check your own account rather than trust either side.

So a join or a bot start is the last thing Telegram counts for you. Everything after that, you build.

Why the usual tracking setup doesn’t fit

On Meta or Google, the normal setup is: the ad links to a tracker (software that counts clicks and sales per ad), the tracker creates a click ID and redirects to the landing page, and when a sale happens your server sends that click ID back to the tracker. That server-to-server message is called a postback. Two things break that on Telegram’s own ads.

No tracker in front of the ad. “All links included in the Text and URL field must link to a channel or bot on Telegram”, and “Links to external sites are not allowed” (Telegram). The ad goes straight to your bot or channel.

No click ID. I found no documented macro for putting a per-click value into the ad link. A vendor blog says dynamic macros aren’t accepted, but I couldn’t confirm that on a Telegram page. Either way, the practical answer is the same: one fixed code per ad.

Some ad networks that sell placements inside Telegram mini apps do have a click macro. RichAds’ docs, for example, show https://t.me/yourBotName?start=yourStartParams__clickId=[CLICK_ID] (RichAds). That works on their network. It isn’t how Telegram’s own ad platform works.

The setup that works: start code, user ID, then your tracker

1. One start code per ad. Telegram’s guidelines allow it: “If the destination is a Telegram bot, links may include start parameters for the bot” (guidelines). A link like t.me/yourbot?start=ad12 delivers /start ad12 to the bot (Telegram).

The rules for that code: “A-Z, a-z, 0-9, _ and - are allowed” and “The parameter can be up to 64 characters long” (same page). No &, no =, no dots. RichAds’ docs make the same point: “& is not allowed in Telegram deep links! Use __ (double underscore) or another separator instead”.

2. Store the code with the Telegram user ID. When /start ad12 arrives, the bot knows who sent it. Write both to your database the moment it happens. G.MEDIA’s measurement guide calls the start payload plus logging “the most reliable measurement path on Telegram” (telegramadsanalytics.com). From here on, every event in the bot carries the ad it came from.

3. Mint the tracker click on the bot’s link out. When the bot sends someone to your landing page, it builds the URL: the stored ad code, UTMs and your tracker’s sub-ID (a slot in the tracker’s link where you put your own value, here the ad code). This is where a tracker such as Voluum takes over. Its docs describe the usual flow: “a unique click ID value is generated for the click”, then passed back by a “server-to-server (S2S)” postback when the conversion happens (Voluum).

4. Tag every link the bot sends. Google’s guidance: “you should always use utm_source, utm_medium, and utm_campaign” (Google). Miss them and the visit lands in analytics as “(direct)”, which is a warning G.MEDIA’s guide also gives.

5. Count blocks too. When a user blocks or unblocks the bot, Telegram sends it an update: “For private chats, this update is received only when the bot is blocked or unblocked by the user” (Bot API). Log it against the stored ad code, and you’ll see which ad brings people who leave fast.

If the ad promotes a channel instead of a bot, the same idea works with invite links: the Bot API reports which invite link a user joined through (same page), so one named invite link per ad does the job of the start code.

If you send people into a Mini App instead, the link t.me/botusername/appname?startapp=... passes its value to the app as start_param (Telegram). I found no published length limit for it, so keep it short and stick to the same safe characters.

Why we send ad traffic to a bot in the first place is its own article: Telegram bot marketing.

Sending conversions to Meta or Google

This is where people get confused. Sending a conversion to Meta or Google only helps ads you bought on Meta or Google. If the user came from a Telegram ad, sending that sale to Meta doesn’t attribute it to Telegram; it just teaches Meta about a customer it didn’t bring.

It matters when the funnel is a Meta or Google ad that sends people into your Telegram bot. Then:

  • Meta. The Conversions API connects data from “an advertiser’s server, website platform, mobile app, or CRM to Meta systems” (Meta). Two details bite with bots. First, business_messaging is for “ads that click to Messenger, Instagram or WhatsApp”, not Telegram. One developer argues for other and passing Meta’s click ID through the start code (DEV); Meta’s list also has chat, so this one is unsettled. Second, events can be at most 7 days old, and one stale event fails the whole request (Meta).
  • Google. Offline import needs a conversion action with “a type of UPLOAD_CLICKS”, and a Google click ID is “Recommended when available” (Google Ads API). With no Google ad in the path, there’s no click ID to send.

The pixel side of Meta, and when to use which, is covered in Meta Conversions API vs pixel.

One more limit: a Meta click ID plus your own ad code may not fit in 64 characters. I haven’t measured that, but it’s easy to avoid: store the long ID on your server and put a short key in the start code.

Where tracking usually breaks

Most of these follow from the rules above. They aren’t measured, they’re the things we check first:

  • A disallowed character in the start code (&, =, .), so the link doesn’t carry the code.
  • The bot reads /start ad12 but never saves it, so later events have no source.
  • A user who already started the bot taps another ad. Whether you get a fresh code depends on how they come back; I haven’t verified that it always arrives, so don’t assume it does.
  • A redirect between the bot and the landing page that drops the query string.
  • Bot links without UTMs, landing as “(direct)”.
  • Meta events sent more than 7 days late, which rejects the batch.
  • Nobody listening for the block update, so the block rate stays invisible.

How to do it

What I’d set up before the first Telegram ad goes live:

  1. Name the ads. One short code per ad: ad12, es_b2. Letters, digits, _ and - only, under 64 characters.
  2. Put the code in the ad link. t.me/yourbot?start=ad12, the same code in the button and in any link in the ad text.
  3. Save on /start. Telegram user ID, ad code, timestamp. Test it: tap your own link and check the row exists.
  4. Tag the link out. The bot’s link to your landing page carries the ad code, UTMs and your tracker’s sub-ID.
  5. Postback the sale. Your landing page or CRM tells the tracker when someone signs up or pays, server to server.
  6. Log blocks. Store the block update against the ad code.
  7. Read per ad weekly. Starts, landing visits, sign-ups, sales and blocks, each by ad code. Telegram’s dashboard gives you views and starts; the rest comes from your own data.

Before you buy traffic, pick channels that fit: how to find Telegram channels to advertise in. For the whole picture of buying on Telegram, the guide to advertising on Telegram.

Sources

https://t.me/aidaily_business