Count clicks from a specific Telegram channel post

Telegram's channel analytics show you views, forwards, and reactions per post — but never how many people tapped a link inside it. If you're posting an offer to your channel and want to know whether it actually drove traffic, the link itself has to do the counting.

Wrapping the link

From a channel post's detail view, mint a track link for it: paste the real destination URL, and you get back https://<your-domain>/t/<code> — a short redirect on your own domain that stands in for the real link in the post.

• The domain used is your account's first registered domain; if you have none yet, connect one first (see Domains).
• One track link per post. Minting again for the same post with a different destination updates the target in place and keeps the same code — so a link you already pasted into a published post keeps working even after you repoint it.

Paste the returned /t/<code> URL into the post instead of the raw destination.

How the count works

Every visit to /t/<code> is a real 302 redirect to the stored destination, and it lands one click row in the same log every other redirect on your domains writes to — tagged with the post's message id as its source. The post's click number shown in the panel counts only these rows; it's never an estimate derived from views or reactions.

Because it goes through the standard click pipeline, a click from a channel post shows up alongside every other click in the clicks report too — filterable, exportable, and covered by the same fraud signal as any other traffic.

An unknown or disabled code

If the code in a /t/<code> URL doesn't match anything on record — mistyped, or the link was never minted through this flow — the redirect is a clean 404. Nothing about the destination or why it failed is revealed.

What's next

Want to see how this post's clicks compare across your other traffic? See Check a campaign's clicks for fraud.