How to track Telegram conversions from Meta ads
Meta reporting ends at the click because the pixel cannot run inside Telegram. This guide describes the server-side process that reports Telegram conversions to Meta.
Meta reporting ends at the click because the pixel cannot run inside Telegram. This guide describes the server-side process that reports Telegram conversions to Meta.
Ads Manager attributes only what its pixel or its own surfaces can observe. A Telegram join, a message to your bot and a deposit made after a conversation all take place outside a browser. Meta has no record of them, so it continues to optimise for people who click, regardless of whether they convert.
Event name and time, action source, the fbc reconstructed from the click id, fbp when a landing page captured it, hashed email or phone if your funnel collected them, a hashed Telegram user id as external id, client IP address and user agent, and value and currency for deposits. Meta uses these fields to calculate match quality.
No. The path from ad to tracking link to Telegram works without one. A landing page with tracker.js is optional and improves match rates.
Clicks, bot starts, group and channel joins, DMs to your admin bot, offer link clicks, Mini App events, Stars payments, and deposits or first-time deposits via postback.
Clicks appear immediately. Conversions are delivered to Meta on the next worker cycle, normally within a minute.
No. The same events can be delivered to TikTok, Snapchat, Reddit, Spotify and Google Ads from one setup on the Pro plan.
The Free plan requires no card. Upgrade to Pro at any time.