Ad platforms, Telegram, Discord and affiliate networks each have their own vocabulary, and a Telegram funnel uses all of them at once. This page defines the terms in the order they appear in a funnel, from the click to the report, and links each to the guide that explains it in full. The words match Tellmetric's dashboard.
A code the ad platform appends to the link on an ad click: Meta's fbclid, TikTok's ttclid, Google's gclid, Snapchat's sccid, Reddit's rdt_cid, Spotify's spdt, X's twclid. A tracking link stores it with the click so a join or deposit days later is credited to that exact ad and sent back with an id the platform recognises. See Meta ads to Telegram, TikTok, Google Ads and Snapchat.
Two Meta identifiers. fbc is the fbclid in the form Meta's Conversions API expects; fbp is the browser id Meta's pixel sets as a cookie, which only exists when the click passed through a page that runs the pixel. A tracking link captures fbc; a page with the tracker.js snippet adds fbp. See Pixel vs Conversions API for Telegram.
utm_source, utm_medium, utm_campaign, utm_content and utm_term: campaign labels on the ad URL, stored with the click. A link's ad URL carries utm_campaign from its name, and every later event inherits the labels, so results group by campaign and creative. See UTM tracking for Telegram ads.
Free-form slots affiliate trackers use for their own labels. A tracking link stores sub1 to sub9 from the ad URL, and an offer link fills them back into the broker's URL as {sub1} to {sub9}. See Telegram postback tracking.
A bot opens with t.me/<bot>?start=<code>, and Telegram hands the code to the bot when the person presses Start. A tracking link puts the click id in that code, so the bot knows which click each conversation came from. See Telegram bot analytics.
The same idea for a Mini App: t.me/<bot>?startapp=<click id>. The app reads the parameter from Telegram's signed initData and posts its events to the Mini App endpoint, where the signature is checked against the bot token: a proven pair of Telegram user and click. See the developer page.
An invite link the bot creates for one click, with a member limit of one. When Telegram reports a join made with it, the match between member and click is exact; no timing, no guessing. See Telegram group join tracking.
A permanent invite link with a name. It separates sources that carry no click id, such as a Telegram Ads creative or a partner's post; everyone who comes through it is credited to the name. See Track channel subscribers from ads.
A channel or group setting under which a new person asks to join and an admin, or the bot, approves. Telegram reports the request with the invite link used, so a request made through a single-use link is attributed the same way as a direct join. See channel subscribers from ads.
A link mode in which the visitor skips the bot's Start step and goes straight to the single-use invite link minted for their click. Fewer taps, fewer people lost on the way; the bot never talks to them. See Track Telegram joins from ads.
Your own bot, added as an admin or as a plain member. An admin bot creates invite links and sees which link each join used; a member-only bot sees only the join notice, so it records joins without the link behind them. Tracking never runs through a personal account. See group join tracking.
Telegram's own tag for ads that lead to a website. It records page events in aggregate and sees nothing inside a channel or bot. See The Telegram pixel explained.
The t.me destination used in a Telegram Ads creative. Telegram Ads add no click id, so attribution is per creative: each link gets its own t.me address (a permanent invite the bot makes, or a bot start code) and spend is entered by hand on the Telegram Ads page under Ad accounts. See Telegram Ads conversion tracking.
"Joined the group": a person joined your Telegram group, channel or Discord server. The record keeps how they joined (your link, an approved request, a public link, a folder link, added by someone, or the join notice), so real joins are told from the rest. See group growth tracking.
"Still a member": someone who joined through your ad is still there after the number of days set on Connections (seven by default). A stronger signal than the join: cheap members who leave within a day are not worth paying for. See Telegram group ROI.
"Left the group": a member left or was removed. Leaves are kept in reports as a negative signal and never sent to an ad platform as a conversion. See group growth tracking.
"Messaged you": the first message a person sends to your bot after arriving through a message link. It is the lead event in funnels that end in a conversation rather than a join. See How to track Telegram leads.
"Messaged you (source unknown)": a message arrived, but the person never came through a tracking link, so no ad can be credited. See Which ad drove this Telegram lead.
The page at /health that answers "is it actually working?": the bot listening and keeping admin rights, clicks turning into joins, Meta accepting events, match quality holding. A failed check sends an email notice. See Telegram funnel tracking.
A URL of yours that receives every join, message, deposit, lead and membership change as it happens, as a GET template or a signed JSON POST with an X-Tellmetric-Signature header. See Telegram to Zapier, Make and Google Sheets.
A Deposit is a payment your platform reported; an FTD (first-time deposit) is a person's first; a Purchase is a completed payment such as Telegram Stars or a paid channel subscription. All three go to ad platforms as purchase events with value and currency. See How to track Telegram deposits.
A server-to-server (S2S) request sent by the system that sees the money, with the click id, a status such as reg, ftd or dep, the payout, the currency and a transaction id. The grammar is the one affiliate trackers use. See Telegram postback tracking.
Ad spend divided by real joins, shown beside each row once spend is imported from Meta or Google or entered for Telegram Ads. It replaces cost per click as the number to compare creatives by. See Telegram group ROI.
Ad spend divided by members still present after the retention period. A creative with a low cost per join can have a high cost per retained member if its members leave. See group growth tracking.
Ad spend divided by first-time deposits, the figure a deposit-driven funnel is judged on. See tracking Telegram deposits.
Return on ad spend: deposit value divided by spend. 3× means every euro of ads brought three euros of deposits. See Telegram group ROI.
How long after a click an ad platform still credits a conversion to it; Meta's default is seven days after a click. Tellmetric's records never expire, but Meta refuses events older than seven days, so send deposits as they happen. See Why Meta's leads do not match Telegram sales.
Meta's server-side endpoint for conversions; Snapchat, Reddit and Spotify use the same name for theirs. Joins, messages and deposits go to Meta on every plan, with the click id and hashed identifiers. See Meta Conversions API for Telegram.
TikTok's equivalent of the Conversions API; events carry ttclid. On Pro and Agency. See TikTok ads to Telegram.
The Google Ads endpoint Tellmetric uses for uploads, keyed by gclid, instead of the older conversion upload. On Pro and Agency. See Google Ads to Telegram.
Every event carries an id (a click is c_…; a postback's includes the txid). The platform drops a second event with the same id, so a repeated postback counts once. See Sending Telegram events to Meta CAPI.
Meta's score (event match quality) for how well it can recognise the person behind an event. The match panel (Pro and Agency) shows which identifiers your events carry; tracking health warns when the share with a strong one falls. See Pixel vs Conversions API.
external_id is the Telegram account, sent as a SHA-256 hash; email and phone from a postback are hashed the same way before storage. See Telegram tracking without a pixel.
Meta's field for where a conversion happened (website, chat, app). An invalid value rejects the whole batch, so only values Meta accepts are sent. See Sending events to Meta CAPI.
Discord has no pixel and never says which invite a member used. An authorised join link sends the visitor through Discord's OAuth screen ("know your username, join servers for you"); the callback adds them to the server and records the join against the click. Retained and Leave come from a periodic rights check. See Discord invite tracking and Discord server growth tracking.
fbclid (as fbc), fbp when a page sets it, ttclid, gclid, sccid, rdt_cid, spdt, twclid, Whop's wuid, every utm_* label and sub1 to sub9.
A join is the moment someone enters; retained means they are still there after the days set on Connections. Cost per retained member is the fairer way to compare creatives.
An FTD is the first deposit a person makes; it is sent to ad platforms as a Purchase with its value and currency, like any later deposit.
Ad platforms optimise towards the events they receive; a negative outcome sent as a conversion would teach them to find more of it. Leaves, refunds and ended subscriptions stay in reports only.
No. A tracking link records the click and opens Telegram or Discord directly; a landing page with the snippet is optional.
The Free plan requires no card. Upgrade to Pro at any time.