Telegram strips query parameters from t.me links. Telebam holds them on the landing page and stores them per join — so utm_source, utm_medium, utm_campaign all survive the click.
If you've ever tried to put ?utm_source=newsletter on a t.me/+abc123 link, you'll have noticed: it doesn't work. Telegram drops query strings on the deep-link, so by the time the user is in the app, every campaign tag is gone.
Result: marketers running multi-channel Telegram funnels (newsletter + Twitter + paid + influencer) have no way to know which channel drove which join. You're left guessing — or running each channel in isolation, which kills budget efficiency.
A Telebam invite link is a real web URL, so query parameters are first-class. We capture every UTM the user arrived with and store it on the resulting group join. Filter your dashboard by utm_source to see exactly which channel produces real conversations.
utm_source, utm_medium, utm_campaign, utm_content, utm_term — captured automatically, no setup needed.
Pass anything: ?ref=joe, ?creator=alex, ?ab=variant_b. Stored as metadata on each join.
Dashboard slices joins by source, campaign, or any custom param. See ROI per channel at a glance.
Push attributed joins to your CRM, attribution tool, or warehouse via webhook. Close the loop end-to-end.
Telegram's deep-link handler strips query strings. The OS opens telegram.org with the path only — your tracking parameters never reach Telegram, never reach you.
No. Just append them to any Telebam invite URL — we capture them automatically.
Yes. Each join row shows source/medium/campaign. Filter and group by any combination.
Webhooks fire on each join with the full UTM payload. Plug into Segment, RudderStack, or your data warehouse directly.
Free Telebam tier includes UTM capture and per-link analytics. Set it up in 60 seconds.
Start free