Telegram gate bot

The gate bot («Прокладка») is your own Telegram bot standing between paid traffic and your manager DM. Instead of sending ads straight to a personal account, you send them to the bot: it greets every /start with a localized message and one button to the DM — and does two things a bare link can't:

1. Attribution. Any button or redirect pointing at t.me/<your-bot> automatically gets a personal ?start= payload carrying the click id. Every /start is tied back to the originating click (country, domain, source), so the click → subscriber → money funnel resolves with no manual tagging. First-writer-wins: a repeat /start never rewrites the original acquisition click.
2. Traffic split. Junk (freshly created accounts — trolls, throwaways) can be routed to a public channel so they never see the DM link. Quality traffic passes through.

Connecting

Dashboard → Telegram → Прокладка:

1. Create a bot with @BotFather (/newbot), copy the token.
2. Paste it into the token field → Подключить бота. The webhook is registered automatically; the token is stored encrypted and only a mask is ever displayed.
3. Set the DM destination — usually https://t.me/<your-manager>.

The status card shows webhook health («последний апдейт N минут назад») and a re-register button in case Telegram drops the subscription.

Bot reply

The default greeting ships localized in 16 languages, picked from the deep-link payload or the user's Telegram profile. Everything is overridable: a global greeting/button override, per-language overrides, and a 0–4000 ms "typing…" simulation before the reply.

Traffic split

Telegram ids grow roughly chronologically — a very high id means a freshly created account.

Advanced routing: destinations & rules

The DM/channel split above is actually the simplest case of a more general routing engine: up to 20 named destinations and up to 30 ordered rules, evaluated top to bottom with the first match winning. Conditions can combine Telegram Premium, account freshness, client language, the originating click's country, whether a username is set, and whether the visitor arrived with a tag at all (organic vs. tagged) — so you can, for example, send one country to a local manager, non-Premium fresh accounts to a channel, and everyone else to the DM, all from one ordered list.

The moment any rule is saved, it takes over routing entirely — the plain split fields above stop being read. See Route different audiences with rules for the full reference.

Profile sync

The bot's public Telegram identity — name, bio, short bio, avatar — isn't edited as plain text fields on this tab; it's pulled from and pushed to Telegram itself. Sync reads the bot's current profile from Telegram (partial-tolerant — whatever succeeds gets saved even if one call fails), and profile edits are pushed live to Telegram (setMyName/setMyDescription/ setMyShortDescription) then re-synced, so the panel always reflects what Telegram actually accepted rather than what was typed. The avatar itself can only be changed in @BotFather — Telegram's Bot API has no method to set it — then pulled in with Sync. See Sync or edit the bot's Telegram profile.

Stats

The tab shows /start totals (all-time / 24h / 7d), the DM vs channel split, top audience languages and the Premium share — scoped to your account.

Multi-tenancy

Every platform account connects its own bot with its own token. All bots share one webhook URL; the tenant is resolved from the secret Telegram sends in the X-Telegram-Bot-Api-Secret-Token header, so another tenant's /start can never be recorded under your account.