Home

Orbitra is a self-hosted traffic and conversion tracker: campaigns and streams, cloaking, landing pages and PWA, postbacks, cost import, reports. It runs on a single inexpensive VPS (PHP + SQLite + Nginx) and is Keitaro-compatible via Click API, campaign tokens, and templates.

This documentation is current for v1.6.19. For what changed in each version, see the CHANGELOG.

wget -O orbitra-install.sh https://raw.githubusercontent.com/fenjo26/Orbitra.link/main/install.sh && bash orbitra-install.sh

Getting started

• Quick start: your first campaign
• Installation and updates
• Migrating from Keitaro
• Feature overview

Traffic

• Campaigns and streams — filters, schemas, rotation, test links
• Cloaking · How the cloaker works (EN)
• Landing pages (EN) — landing types, {offer}, macros, the JS adapter, LeadForge
• Tracking Client (PHP) (EN) — kclient.php
• PWA landing pages and Web Push · PWA Funnel (EN)
• Content gallery

Conversions and money

• Postbacks and conversions — incoming postbacks, statuses, S2S to the source
• Costs — Facebook, TikTok, Google Ads, the revenue aggregator
• Facebook / Meta (EN) — cost import and Conversions API
• Dolphin / Fbtool — receiving costs via the Keitaro Admin API
• Traffic sources and affiliate networks
• Affiliate network offer parameters (EN)

Analytics

• Reports, logs, and metrics

Infrastructure

• Domains and SSL
• Cloudflare · Cloudflare Full Strict SSL (EN)

Management and integrations

• Administration — users, permissions, settings, geo databases, updates
• Telegram bot
• MCP: an AI assistant in the tracker
• REST API — authorization and the catalog of all actions

For developers

• Architecture — internals, crons, the database, development, releasing a version
• Technical specs and write-ups: load and SQLite, SSL chains and privacy, Web Push, logs, geo, streams, Media Core v1, LeadForge subid validation (EN)
• Archive of outdated documents

Support

Questions and bugs — GitHub Issues. In the panel: ⚙ → Support and feedback.