Server-side
Telegram tracking without a pixel, and why it is more reliable
A pixel only measures what happens in the browser. Telegram funnels need a measurement layer that does not depend on it.
What a pixel cannot do
A pixel is JavaScript on a web page. It runs when the page loads and reports what happens on that page. Telegram is a native app with no page and no script, so once a visitor taps "Open Telegram", the pixel has nothing further to report. Tracking prevention, ad blockers and iOS restrictions also mean that the web part of the funnel is under-counted.
What server-side tracking changes
- The click is recorded by a server-side redirect rather than by a script that may be blocked.
- The conversion is observed inside Telegram by a bot, with no browser involved.
- The two are linked by an identifier your server controls, and the result is sent to the ad platform through its server API.
- Measurement does not depend on cookies persisting, a page loading or a device permitting scripts.
Setting it up
- Point ads to a Tellmetric tracking link instead of a t.me address. The redirect captures fbclid or ttclid, UTM values and browser hints in a single step.
- Connect your Telegram bot. Joins, bot starts and messages are matched to the click.
- Send deposits to the postback URL with the click id.
- Optionally, add tracker.js to a landing page to capture the fbp cookie and visit data. This improves match rates but is not required.
Example
Illustrative example: an advertiser sending traffic directly to Telegram sees 40 conversions a week in Meta, all of them landing-page views. After switching to server-side join and deposit events, Meta receives 210 joins and 19 purchases with values. The campaign can now optimise for deposits, because the platform receives the signal it needs.
Common mistakes
- Sending pixel and server events for the same action without a shared event id. Meta then counts both.
- Sending events without identifiers. A server event still needs fbc, an IP address and user agent, or a hashed email address to be matched.
- Reporting only the join. Without purchase events that carry a value, the platform optimises for volume.
- Assuming a landing page is required. It is optional when the redirect performs the capture.
How Tellmetric handles it
Tellmetric is server-side throughout: redirects record clicks, the bot verifies conversions, and a delivery worker sends events to Meta's Conversions API, TikTok's Events API, the Snapchat, Reddit and Spotify Conversions APIs, and Google Ads through the Data Manager API, with event ids for deduplication. Hashed email addresses and phone numbers can be attached through the postback, which improves match quality beyond what a pixel alone provides. A match-quality panel shows which identifiers your events include.
Frequently asked questions
Do I need a pixel at all?
No. If you do run one on a landing page, Tellmetric deduplicates against it by event id.
Does Meta accept server-side events for Telegram actions?
Yes. They are standard Conversions API events with the website action source and the original click id.
Is it accurate on mobile?
It is more accurate than a pixel, because nothing needs to run on the device after the click.
How quickly are events delivered?
The delivery worker sends events within approximately thirty seconds of the conversion.
Track Telegram conversions from your Meta ads
The Free plan requires no card. Upgrade to Pro at any time.