Docs

Campaigns and streams

A campaign is the URL traffic arrives on plus a set of streams that decide where each visitor goes. The Campaigns section is in the top menu.

The campaign editor

The editor opens full-screen. On a wide screen (1280px and up) it is split into two panels: campaign settings on the left, streams on the right; on a narrower screen it becomes a single column.

Settings tabs

TabWhat is there
GeneralName, alias (6 characters, generated automatically), campaign URL, domain, group, traffic source, state, test link; lower on the tab β€” the social link preview card and the Zone Killer rule
FinanceCost model, uniqueness, stream rotation type
ParametersWhich link parameters the tracker saves into the click (keyword, cost, external_id, creative_id, ad_campaign_id, source, sub_id_1 … sub_id_30) and which source parameters to take them from
IntegrationsPixels (Facebook / TikTok etc., see Facebook / Meta) and connecting cost synchronization (Costs)
TrackingIntegration code generator: the tracking script, kclient.js, kclient.php, the pixel, banners (script / iframe), the WordPress plugin, widgets (a countdown timer, the "back button", exit-intent). Available after the first save β€” the code contains the campaign token
PopupThe campaign's own conversion popup: on/off (a dot on the tab while on), a live preview, four steps and an Advanced section
S2S PostbacksOutgoing postbacks to the traffic source, a postback tester, re-sending missed conversions β€” see Postbacks and conversions
NotesFree-form text

Cost models

CPC, CPV, CPuC (per unique click), CPM, CPA, CPS, RevShare. Manual cost is overwritten by cost import if it is connected (Costs).

Uniqueness

Campaign state

A stopped campaign (paused / disabled) responds with 503, an archived one with 404. This applies to the alias URL, click.php, and the Click API.

A card on the editor's General tab. When enabled, a social or messenger preview bot hitting the campaign URL β€” facebookexternalhit, telegrambot, whatsapp, twitterbot and the other link-preview fetchers β€” gets a minimal og:* card with your title, description and image instead of the click flow. Every human is routed exactly as always: no delay, no different page.

Search crawlers (googlebot & co) deliberately keep seeing the real campaign answer β€” this is only the messengers' preview fetchers; full bot handling is cloaking's job. The one-time disclaimer records that platform rules on custom previews are the operator's responsibility.

Streams

A stream is a routing rule: filters (who it matches) + a schema (what to show).

Types and order

  1. Intercepting β€” checked first. Suited for bots, white pages, exceptions.
  2. Regular β€” the main traffic. Selected by position or by weight (the rotation type on the "Finance" tab).
  3. Default β€” when nothing above matched.

Saving a campaign does not recreate its streams: each stream keeps a stable ID, so click history does not scatter across old numbers. New streams are named "Stream 1", "Stream 2" … The chevron on a card collapses the stream; the state is remembered per campaign.

Each stream card shows visits, uniques, bots, and the share of campaign traffic for today / yesterday / 7 / 30 days. This makes it easy to see how much traffic went to the white stream and how much to the money stream.

Filters

FilterHow it works
CountryA list of countries or a geo profile (EU, CIS…). If the country cannot be determined and "include" mode is on, the filter does not let the visitor through β€” but only when a geo database is installed; without one the filter abstains
DeviceDesktop / mobile / tablets
Operating system, BrowserValues are chosen from the list the tracker actually recognizes, including in-app browsers (TikTok, Facebook, Instagram, Telegram, WebView). You can type your own value and press Enter
Browser languageen β€” any English, en-IN β€” English (India) only. The entire Accept-Language is considered, not just the first language
BotThe bot detector at maximum sensitivity (the same one used in cloaking)
IP addressAddresses and CIDR, IPv4 and IPv6
Provider (ISP)Compared against the visitor's ISP and ASN (requires the ASN database)
Connection typeFrom geo-database data
Referer, KeywordCompared against the click's value
URL parameterAny link parameter by name. Case-insensitive exact match, * β€” any characters, "Empty" β€” the parameter is missing or empty
Day of week, TimeBy the visitor's local time (time zone from the geo database; without it, server time)

A stream's filters are combined with AND (all must match) or OR (one is enough). A filter that cannot reach a decision (no geo database, no ISP data) does not vote: under "AND" it does not block the stream, under "OR" it does not open it.

A trick against TikTok moderation via "URL parameter": add xxx=__PLACEMENT__ to the campaign URL; on an intercepting stream with a white page, set a "URL parameter" filter on xxx with the values __PLACEMENT__ and "Empty". In a real click the network substitutes the macro's value, while a moderator opening the bare link arrives with __PLACEMENT__ or without the parameter.

Schemas

SchemaWhat happens
Direct redirect to offerA redirect to an offer from the catalog (several offers rotated by weight) or to a direct URL. Every such transition is a click
Landing + OfferShows a landing from which the visitor goes on to the offer. The offer is optional
ActionDo nothing, 404, show text, show HTML, send to another campaign (the click is written to both)
CloakingSplits traffic between a safe page and a money page β€” see Cloaking

Offer selection in the "Landing + Offer" schema:

How to build the offer link on the landing itself ({offer}, /?_lp=1, passing sub_id_N to the offer) is covered in Landing pages.

Offer redirect types

Set on the offer. Macros and the SSRF check are the same for all types.

TypeBehavior
HTTP redirect302, the default
JS redirectAn HTML page that navigates via JavaScript
Meta RefreshA <meta http-equiv="refresh"> tag
IframeThe offer in a full-page iframe on your domain
Form SubmitAn auto-submitted POST form: tracking data in the request body
curl proxyThe offer page served through your server with a <base> tag

Rotation with auto-optimization

The Auto switch next to a stream's offer or landing list enables automatic weight recalculation by a metric: confirmed sales, CR, EPV, EPC, or ROI (ROI requires costs). Configurable: the window in days, the minimum number of sales before taking part in the split, the lower and upper bounds of the share, and the recalculation interval. Recalculation is done by the rotation_optimiser_cron.php cron; the decision log is visible in the stream card. While "Auto" is on, manual weight entry is locked.

Other stream settings

Bot Challenge is a campaign setting, not a stream one: a human check (reCAPTCHA v2/v3 or your own code) before a stream is chosen.

The Test link row on the "General" tab produces a campaign URL signed with ?_t=<id>:<hmac>. Real routing works along it β€” streams, filters, rotation, landings, offers β€” but the click is not recorded, so statistics stay clean.

The signature is derived from the installation's postback key, so it survives a campaign token change; changing the postback key revokes all test links. An invalid or foreign signature turns the request into an ordinary click.

Traffic simulation

βš™ β†’ Traffic simulation: set an IP, User-Agent, country, device, language, and URL parameters β€” the panel will show which stream fired and why, without recording anything.

Click API and campaign tokens

Every campaign has a token (32 hex characters). Integration scripts (click.php, kclient.php, tracking.js, Click API v3 /click_api/v3) address the campaign by token, not by ID. Tokens are transferred on import from Keitaro, so already-installed scripts keep working. The token can be reissued in the editor. For details on the PHP client, see Tracking Client (PHP).

Duplicate protection

Bulk operations

Campaign copying, bulk deletion, import, moving a group of campaigns to another domain (bulk_set_campaign_domain, also in MCP), renaming groups right in the list.

← Previous
Feature overview
Next β†’
Cloaking
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 β†’