A bare t.me link opens Telegram's own preview: a name, a photo, a join button, nothing you control. A landing page for a Telegram channel is a page on your own domain that shows the channel properly, a real preview, a real join button, and counts who visited and who joined instead of handing that count to Telegram alone. Scalegram is the Telegram CRM for IBs and forex affiliates, and its Websites feature builds exactly that page from the channel itself and reports every visit and join back to the ad that paid for it.
What a t.me link leaves out
Send someone a t.me/yourchannel link from an ad and three things happen outside your view. Telegram decides what preview to show, the click never touches your own domain, and if the person joins, nothing about that join reaches the ad platform unless you built a separate reporting step for it. The tracked-link approach covered in Telegram UTM tracking fixes the reporting gap without a page at all: a redirect link that reads utm_source and utm_campaign, tags the visitor, and reports the join under those tags. A hosted landing page does something the redirect cannot: it puts an actual page, with your own copy, your own pixel code and your own domain, between the ad and the join.
The card comes from the channel, not from a template
The page itself is not hand-built once and forgotten. Scalegram's own product page describes the mechanism plainly: the page is "hosted on the customer's own domain (a CNAME is all it takes)" and "the card is fetched from the channel." A bot reads the channel the same way any Telegram bot reads a chat it administers, through the Bot API's getChat method, which Telegram's own documentation says returns the chat's "title," its "photo" and its "description, for groups, supergroups and channel chats." Post a new pinned message or swap the channel photo, and the next visitor to the landing page sees the update, because the page is reading the channel live rather than displaying a screenshot someone pasted in six months ago.
Why the domain the page sits on decides whether the pixel fires
The reason a landing page beats a link for tracking is not the page itself, it is the domain. Apple's WebKit engineering blog, which documents Safari's Intelligent Tracking Prevention, states the rule without qualification: "ITP by default blocks all third-party cookies. There are no exceptions to this blocking." A pixel or a cookie set from a shared tracking domain, the kind every visitor to every customer's page shares, is exactly the third-party pattern ITP targets. A pixel fired from a page on the customer's own domain is a first-party request instead, and WebKit's own account of first-party storage draws the line clearly: first-party cookies "are not subject to the blanket blocking applied to third-party cookies," even though a separate seven-day cap limits how long script-writable storage persists in some cases. An ad blocker that keeps a filter list of known tracker domains runs into the same asymmetry. It can block a request to a shared domain it recognizes; it has no reason to block a request to a domain it has never seen before, because that domain belongs to the site itself.
Conversions API vs pixel covers the server-side half of the same problem, reporting a join or a deposit straight to Meta's servers instead of waiting on a browser event. A first-party domain and a server-side report solve different halves of the same leak: the domain keeps the pixel from being blocked before it fires, the server call keeps the conversion from being lost after it fires. Scalegram runs both: the Websites feature puts the page on the customer's own domain, and Meta ads Telegram conversion tracking covers how the join is then reported server side to Meta, TikTok and Snapchat.
Counting a join, not a click
A click on a landing page is not the number that matters, the join is. Scalegram's product page states the tracking outcome directly: "every visit and join is tracked and reported." That means the page distinguishes someone who loaded it and left from someone who actually pressed join and landed in the channel, and only the second event is what gets reported back to the ad platform as a conversion. Counting the click alone would optimize a campaign toward people who load pages, which is not a business. Best Telegram tracker 2026 lists what other tools in this category report and how; a hosted page that fetches the channel's own card and reports the join server side is the version Scalegram ships.
Setting one up
The setup step is a CNAME record, the same DNS change a landing page builder or an email platform asks for when a customer wants mail or pages on their own domain rather than a shared one. Point a subdomain, or the domain itself, at the address Scalegram gives, and the page starts serving from that domain within the time the DNS record takes to propagate, typically minutes to a few hours depending on the registrar. No separate website needs to exist first. The channel card renders because the bot already reads the channel it administers; the domain just decides whether the visit and the join that follow are first-party or not. The how it works section shows where this sits next to the bot that answers the lead once they join, and the pricing page lists one page on Lite and unlimited pages on the full plan.
Sources
- Telegram Bot API, getChat, Telegram, checked 27 September 2026
- Tracking Prevention, WebKit, checked 27 September 2026
A t.me link is Telegram's preview. A landing page on your own domain is yours, and it is the difference between a pixel that fires and one that never gets the chance.
— The Scalegram Team
Key takeaways
- A hosted landing page fetches the channel's own title, photo and description live through the Bot API, rather than a static screenshot.
- WebKit's Intelligent Tracking Prevention blocks all third-party cookies by default but treats first-party cookies on the site's own domain differently, which is why the domain the page sits on decides whether a pixel keeps working.
- Scalegram's Websites feature needs only a CNAME record on the customer's own domain, no separate website first.
- The page tracks the visit and separately reports the join, so the ad platform optimizes on people who actually joined the channel.
Frequently asked questions
What is a landing page for a Telegram channel?
A page hosted on your own domain that shows your channel's card, title, photo and description, pulled live from the channel, with a join button, instead of relying on Telegram's own link preview.
Do I need to build a website first to get one?
No. Scalegram's Websites feature hosts the page itself once you point a CNAME record at the address it gives you; no separate site needs to exist.
Why does the domain matter for tracking, beyond the page design?
Browsers such as Safari block third-party cookies by default under Intelligent Tracking Prevention but treat first-party cookies on the page's own domain differently, and ad blockers filter known shared tracking domains rather than a domain unique to the page.
Does the landing page track clicks or joins?
Both are recorded, but the join is the event reported back to the ad platform as the conversion, since a visit that never joins is not the outcome a campaign is paying for.
Put one bot on your own Telegram
Scalegram answers every lead in the language it arrived in, checks the deposit against the broker's own records, opens the paid group and files the client. Lite starts at $99 a month.