Telegram bot
The bot sends conversion notifications and a daily digest, and answers commands with statistics. It speaks the same seven languages as the panel.
Connecting
- In Telegram, open
@BotFather, run/newbotand get a token like1111:AAABBBβ¦. - β β Integrations β Telegram Bot β paste the token and press Connect.
- On the same page, Connect chat β Get code and send
/start CODEto the bot (or open the "Open bot" link). The code is one-time and valid for 15 minutes. The bot does not accept chats without a code; a chat can be disconnected on the same page. - Enable the notifications you need.
After /start the bot pins a keyboard menu: Stats, Top, Campaigns, Conversions, Notifications, Digest, Language, Help β no need to type the commands.
How updates reach the bot
The panel picks the mode itself and shows it on the status card; you can also set it manually.
- Webhook β Telegram calls
https://<domain>/telegram_bot.php. Works only over HTTPS, on a domain name, with a certificate Telegram trusts. The request is verified by the Telegram secret token. - Polling β the
telegram_poll_cron.phpcron fetches updates once a minute. No inbound connection needed: the bot works on a bare IP, overhttp://and behind a proxy. The installer adds the cron:
* * * * * php /var/www/orbitra/telegram_poll_cron.php --quiet >> /var/www/orbitra/var/logs/telegram_poll.log 2>&1
When a webhook is active, the job exits immediately without doing anything.
If the bot is silent, the status card will show the mode, the error returned by Telegram itself (getWebhookInfo), and the poller's last run time. An empty time in "polling" mode means there is no crontab entry. Manual check:
sudo -u www-data php /var/www/orbitra/telegram_poll_cron.php --once
Commands
| Command | What it does | ||||||
|---|---|---|---|---|---|---|---|
/stats | Today's statistics; /stats yesterday, /stats 1d, /stats 7d, /stats 30d | ||||||
/campaigns | Active campaigns, with a button for each | ||||||
/campaign ID | Campaign details | ||||||
/top | Top 5 campaigns by revenue today | ||||||
/conversions | Last 10 conversions | ||||||
| `/notify on\ | off` | Conversion notifications; without an argument β current state and a button | |||||
| `/daily on\ | off` | Daily digest | |||||
| `/lang en\ | ru\ | uk\ | es\ | zh\ | fr\ | de` | Bot language; without an argument β choose with buttons |
/sources | Traffic sources and the status of their URL check | ||||||
/checksources | Check all sources' URLs | ||||||
/allow ID | Allow one more chat by its ID | ||||||
/help | Help and re-pinning the menu |
Commands without an argument change nothing: /notify shows the current state instead of turning notifications off.
Notifications
- On a conversion β campaign, status, amount and currency, country with a flag, time.
- Daily digest β clicks, conversions, revenue, cost, profit and the top 3 campaigns. Send time is
telegram_daily_timein the integration settings. The digest is sent by the poller (for webhook mode too), at most once a day.
Telegram channels as offers β separate funnel bots
The admin bot is never the destination of a Telegram channel offer. Ad visitors talk to separate funnel bots (Admin β Telegram funnel bots), polled by their own worker; the admin bot keeps answering only the chats you admitted. See External PWA & Telegram channels.
Conversion alerts to channels
Notifications β Telegram β Conversion alerts to channels (the bot connection stays in Integrations β Telegram) sends chosen conversions to a channel or group through the admin bot: pick the chat (the bot must be an admin of the channel or a member of the group, press Check), the statuses (deposit, registration, sale, tg_joinβ¦), the campaigns, and an HTML template with macros β {campaign}, {offer}, {status}, {payout}, {currency}, {country}, {flag}, {source}, {ad_campaign_name}, {adset_name}, {ad_name} (ad-platform names from the cost sync), {sub1}β{sub3}, {click_id}, {time}, {date}. Send test posts sample values; the log keeps the last 200 sends per alert. The per-chat /notify switch keeps working as before.
Quick start: your first campaign
The short path: install the tracker, create a campaign, and get your first clicks and conversions in under an hour.
Read guide βDocsInstallation and updates
Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.
Read guide βDocsMigrating from Keitaro
Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β what transfers and what to check.
Read guide βDocsMigrating from Binom
Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.
Read guide βDocsFeature overview
Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.
Read guide βDocsCampaigns and streams
The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.
Read guide βDocsCloaking
Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.
Read guide βDocsBrowser check
How the JS check catches bots, VMs and emulators through contradictions in the browser environment.
Read guide βDocsLanding pages
Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β the complete reference.
Read guide βDocsPWA and Web Push
Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.
Read guide βDocsPWA Funnel
A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.
Read guide βDocsConversion popups
Show real conversion events as on-page popups: setup, triggers and placement.
Read guide βDocsSession recordings and heatmaps
Replay real visits and see click and scroll maps. Storage limits and privacy notes.
Read guide βDocsContent gallery
Central storage for icons, screenshots and creatives used across PWAs and landings.
Read guide βDocsCreatives library
Store creatives with subid tracking and test them across campaigns.
Read guide βDocsExternal PWA and Telegram channels
Publish PWAs to external domains and run Telegram channels as a traffic source.
Read guide βDocsPostbacks and conversions
Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.
Read guide βDocsCosts
Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β and how the revenue aggregator works.
Read guide βDocsPush and pop networks
Working with push and pop traffic sources: feeds, zone optimization and the zone killer.
Read guide βDocsFacebook / Meta
Cost import from Meta Ads and the Conversions API: server-side events with deduplication.
Read guide βDocsDolphin / Fbtool
Receive Facebook costs through the Dolphin (Fbtool) API in real time.
Read guide βDocsFB comment cleaner
Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.
Read guide βDocsTraffic sources and affiliate networks
Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.
Read guide βDocsReports, logs and metrics
The report builder, saved reports, click logs and every metric explained.
Read guide βDocsDomains and SSL
Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.
Read guide βDocsCloudflare
How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.
Read guide βDocsAdministration
Users, roles and permissions, security settings, geo databases, updates and system health.
Read guide βDocsTelegram bot
Manage the tracker from Telegram: stats, conversions and alerts in chat.
Read guide βDocsMCP: an AI assistant in the tracker
Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.
Read guide β