Telegram pixel: how to track Telegram joins from your ads

A Telegram pixel is the setup that tells your ad platform when someone who clicked your ad joined your Telegram channel. The join happens inside the Telegram app, where no script of yours is running, so the job is done in three parts: a pixel on the landing page that records the ad click, a bot that watches the channel for joins, and a server event that reports each join back to Meta, TikTok or Snapchat. Scalegram is the Telegram CRM for IBs and forex affiliates, and the Scalegram Pixel plus its join-watching bot is that setup, carried on to the deposit.

To pick a tool, see the Telegram tracker comparison. Below is what any Telegram pixel has to do.

Why a normal pixel stops at the Telegram button

Meta's Pixel documentation defines the Meta Pixel as "a snippet of JavaScript code that allows you to track visitor activity on your website." It works by "loading a small library of functions which you can use whenever a site visitor takes an action."

The important word is website. The pixel runs while your page is open in the visitor's browser. When they tap a t.me link, the Telegram app takes over, and the join happens there. Your page is gone and your script with it. The last thing the pixel saw was a click on a button.

If the only signal Meta receives is "clicked the Telegram button", the campaign goes looking for more button clickers, and plenty of them never join.

What a Telegram pixel has to do

Four things have to happen in order:

1. Capture the click id when the visitor lands from the ad.
2. Carry that visitor's identity through the jump into Telegram.
3. See the join inside the channel.
4. Send the join back to the ad platform as a server event, with the click id attached.

Step 1: the click id

Every major ad network puts a click id on the landing page URL. Meta's ClickID and fbc page says the ClickID "is a Meta-generated parameter that is passed with the URL of an advertiser's website when a user clicks an ad on Facebook and/or Instagram." It arrives in the fbclid query parameter. TikTok's Click ID article describes TTCLID as "a tracking parameter appended to a landing page URL when you click on an ad on TikTok," shown in its example as &ttclid= added to the address.

Reading and keeping that value is the part a browser pixel does well.

Step 2: getting through the jump

Once the visitor leaves for Telegram, the browser cookie stays behind. Something has to link the person who arrives in your channel to the click that sent them. Telegram's own tools allow this. The Bot API lets a bot create invite links with createChatInviteLink, with an optional name of "0-32 characters", and when a member joins, the ChatMemberUpdated object carries "the invite link used by the user to join the chat; for joining by invite link only."

Step 3: seeing the join

A page cannot see a channel. A bot inside the channel can. The Bot API is specific about the conditions: for chat_member updates, "the bot must be an administrator in the chat and must explicitly specify "chat_member" in the list of allowed_updates to receive these updates." For channels that approve members, a bot receives chat_join_request updates only if it has "the can_invite_users administrator right in the chat."

Any Telegram pixel worth paying for will ask you to add its bot as an admin. That is not overreach. Per the Bot API, join updates go to an admin bot that asked for them, and a page script never receives them.

Step 4: reporting the join

The join is then sent to the ad platform from a server, not from a browser. Meta's Conversions API overview says server events "are processed like events sent using the Meta Pixel," and the fbc page says: "We recommend that you always send _fbc and _fbp browser cookie values in the fbc and fbp event parameters, respectively, when available." TikTok describes its Events API as a connection "across web, app, and offline (eg. Store, CRM) channels." Snap says its Conversions API "lets you pass web, app, and offline conversion events directly to Snap via a server-to-server integration."

Without the click id, a join report is a number with no ad to credit.

How the Scalegram Pixel does it

The Scalegram Pixel is one line of code on a landing page. It ties each visitor to the ad click from Meta, TikTok or Snapchat and rewrites the Telegram links on that page automatically. One Scalegram Pixel can run on any number of sites.

A dedicated Scalegram bot watches who joins the channel. Every subscriber is reported server side to the ad platforms, so ad blockers and iOS do not stop it.

You do not need a website at all. Every Scalegram tracked link has its own address you can paste into an ad, a bio or a post, tagged with the standard UTM parameters. The tags are kept against the visitor and every subscriber that link brings is reported under them, broken down in the panel by source, medium, campaign and creative. A tagged link also reads fbclid, gclid, ttclid and sccid, so the conversion still reaches the ad platform with a click id to match on. The UTM tracking guide goes through the tagging in detail.

If you want a page anyway, Scalegram Websites are landing pages for a channel hosted on your own domain with a CNAME, carrying your own Meta, TikTok and Snap pixels so the tracking is first party. The landing page article shows how they are set up.

Where a join stops being the right event

For an IB or a forex affiliate, a join is a halfway mark, and a campaign that optimizes on joins still pays for people who never deposit.

This is where Scalegram goes past a tracker. Its AI bot answers the lead in Telegram in the language they wrote in, sends the broker link, asks for the email or account number, and checks it against the broker's IB portal or the prop firm CRM over a read-only API. When the broker's records confirm the deposit, Scalegram ties that deposit back to the ad that bought it and reports it server side to Meta, TikTok and Snapchat. The campaign then learns from depositors rather than from joins.

Scalegram stores no messages. The client card holds the stage, tags, notes, UID, email, broker and deposit, which is what the ad report needs. The article on paying for clicks that never deposit covers the campaign side, and Conversions API vs pixel explains how the browser and server channels split the work without counting twice.

Questions to ask any Telegram pixel

Ask these of any tool:

• Does it read the click id from the ad, and does it send that click id with the server event?
• Does it put its own admin bot in the channel, or is it guessing from link clicks?
• Which platforms does it report to: Meta only, or TikTok and Snapchat as well?
• Does it stop at the join, or can it report a later event like a verified deposit?
• Can one pixel run on more than one site?

If you run ads to a Telegram channel and sell a broker or prop firm offer, Scalegram answers yes to all five. Start with how it works, then pick a plan on the pricing page: Lite is $99 a month for one of each, and the full Scalegram plan is $999 a month with no limits on counts.

Sources

• Meta Pixel, Meta for Developers, checked 4 October 2026
• Conversions API, Meta for Developers, checked 4 October 2026
• ClickID and the fbp and fbc parameters, Meta for Developers, checked 4 October 2026
• About TikTok Click ID, TikTok Ads Manager, checked 4 October 2026
• About Events API, TikTok Ads Manager, checked 4 October 2026
• Conversions API introduction, Snap for Developers, checked 4 October 2026
• Telegram Bot API (createChatInviteLink, ChatMemberUpdated, chat_member and chat_join_request updates), Telegram, checked 4 October 2026

Your ad account never sees a Telegram join by itself. A Telegram pixel is whatever closes that gap, and for an IB the gap runs all the way to the deposit.

— The Scalegram Team

Frequently asked questions