Docs

External PWA and Telegram channels

Two ways to widen the funnel beyond Orbitra's own PWA builder: third-party PWA services as stream targets, and Telegram channels as offer destinations with attributed subscribers.

External PWA builders

A third-party service (PWA.Group, TSL.app, or any other) can be a stream target exactly like a landing:

  1. Create the builder β€” βš™ β†’ Integrations β†’ External PWA. Pick a service from the catalog (data/external_pwa_services.json: redirect URL template, postback template, status map) or fill your own; your values win over the catalog's. The shipped catalog entries are templates β€” verify every parameter against the service's current docs before going live.
  2. Point the service back: in its settings, set the post-install redirect to

https://<tracker-domain>/eflow/<campaign-alias>?subid={subid}&eid={eid} (the page shows the exact shape for copy-paste).

  1. Add it to a stream β€” in the campaign editor's landings block, Add external PWA. External builders ride the same weighted pool as landings, so the split gives you "own PWA vs theirs" A/B in one funnel.

What happens on traffic: the click leaves for the service with subid = click id (clicks.external_pwa_id remembers which service). When the visitor returns to /eflow/<alias>, the tracker stamps the install (external_install_at), stores the service's eid (kept 7 days), and continues to the offer through the campaign's own selection β€” exactly like "own" PWA after install.

Conversions on those clicks are posted back to the service through the same reliable s2s queue as partner postbacks, with subid + eid + the service's status word (mapped per service) + payout. Campaign reports gain external installs.

Telegram channels as offers

A Telegram channel offer sends ad visitors into a Telegram channel through a funnel bot and credits the join as a conversion. Funnel bots are separate from the admin bot (Integrations β†’ Telegram): the admin bot only answers the chats you connected and reads your statistics, so strangers from an ad must never reach it. The panel refuses the admin bot's token as a funnel bot.

Setup:

  1. Create a new bot in @BotFather and add its token in βš™ β†’ Integrations β†’ Telegram funnel bots.
  2. Add that bot to your channel as an admin with the Invite users via link right. The channel appears on the bot's card by itself (or add it there by @name, t.me/… or -100…).
  3. Create an offer of the Telegram type, pick the bot and the channel, set the join window (1–7 days) and, optionally, a welcome text.
  4. Put the offer into a campaign stream and run traffic through the campaign link. Never hand out a direct channel link β€” those joins cannot be attributed.

The funnel:

  1. Click β†’ https://t.me/<funnel bot>?start=<subid> β€” /start binds the Telegram user to the click (tg_start).
  2. The bot answers with the welcome text and a join-request invite (creates_join_request=true, expiring with the offer's window).
  3. chat_join_request β†’ the bot approves only users it invited within the window and writes a tg_join conversion (with campaign and offer) on the bound click. Requests from anyone else are left to the channel's moderators.
  4. A network that knows only the subscriber posts to the regular postback URL with tg_user_id and channel_id instead of subid:

https://<domain>/<postback key>/postback?tg_user_id={tg_user_id}&channel_id=-100…&status=deposit&payout=50 β€” resolved to the click of that user's last join of the channel within 30 days. The offer editor's Integration tab shows the exact URL.

Funnel bots are polled by cli/tg_funnel_poll_cron.php (every minute, all bots in parallel, no webhook β€” works without a domain). install.sh schedules it; the bots page shows the crontab line when the poller is not running.

← Previous
Creatives library
Next β†’
Postbacks and conversions
View source on GitHub: github.com/fenjo26/Orbitra.link/wiki
All guides
Docs

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 β†’
Docs

Installation and updates

Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.

Read guide β†’
Docs

Migrating from Keitaro

Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β€” what transfers and what to check.

Read guide β†’
Docs

Migrating from Binom

Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.

Read guide β†’
Docs

Feature overview

Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.

Read guide β†’
Docs

Campaigns and streams

The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.

Read guide β†’
Docs

Cloaking

Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.

Read guide β†’
Docs

Browser check

How the JS check catches bots, VMs and emulators through contradictions in the browser environment.

Read guide β†’
Docs

Landing pages

Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β€” the complete reference.

Read guide β†’
Docs

PWA and Web Push

Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.

Read guide β†’
Docs

PWA Funnel

A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.

Read guide β†’
Docs

Conversion popups

Show real conversion events as on-page popups: setup, triggers and placement.

Read guide β†’
Docs

Session recordings and heatmaps

Replay real visits and see click and scroll maps. Storage limits and privacy notes.

Read guide β†’
Docs

Content gallery

Central storage for icons, screenshots and creatives used across PWAs and landings.

Read guide β†’
Docs

Creatives library

Store creatives with subid tracking and test them across campaigns.

Read guide β†’
Docs

External PWA and Telegram channels

Publish PWAs to external domains and run Telegram channels as a traffic source.

Read guide β†’
Docs

Postbacks and conversions

Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.

Read guide β†’
Docs

Costs

Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β€” and how the revenue aggregator works.

Read guide β†’
Docs

Push and pop networks

Working with push and pop traffic sources: feeds, zone optimization and the zone killer.

Read guide β†’
Docs

Facebook / Meta

Cost import from Meta Ads and the Conversions API: server-side events with deduplication.

Read guide β†’
Docs

Dolphin / Fbtool

Receive Facebook costs through the Dolphin (Fbtool) API in real time.

Read guide β†’
Docs

FB comment cleaner

Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.

Read guide β†’
Docs

Traffic sources and affiliate networks

Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.

Read guide β†’
Docs

Reports, logs and metrics

The report builder, saved reports, click logs and every metric explained.

Read guide β†’
Docs

Domains and SSL

Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.

Read guide β†’
Docs

Cloudflare

How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.

Read guide β†’
Docs

Administration

Users, roles and permissions, security settings, geo databases, updates and system health.

Read guide β†’
Docs

Telegram bot

Manage the tracker from Telegram: stats, conversions and alerts in chat.

Read guide β†’
Docs

MCP: an AI assistant in the tracker

Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.

Read guide β†’