Docs

Cloaking

The Cloaking stream schema splits traffic into two branches: suspicious visitors (bots, moderators, data centers, VPNs) see the safe page, real people the money page. One module (core/CloakDetector.php) makes the decision for all entry points: the campaign URL (index.php), click.php, and Click API v3.

A detailed technical write-up in English: How the Orbitra Cloaker Works.

Stream setup

Safe page

Built-in HTML, an external URL, a local landing, or a local offer. Landings and offers in the list are grouped by group, with a search.

Money page

Works like the "Landing + Offer" schema, including "before the click / after the click" offer selection.

Clean visitors to the next stream

The "Send clean visitors to the next stream" checkbox turns the cloak into an entry filter. Suspicious visitors get the safe page, while clean ones continue down the stream list β€” geo, devices, and languages are split up by regular streams. This stream's money page is not used in this mode. Put such a stream first or make it intercepting so that every visitor passes the check.

Detection layers

LayerSourceDoes not work without
Data centers / hostingAn ASN blocklist (core/data/asn_blocklist.json), published cloud and crawler ranges, hosting keywords in the ISP nameThe ASN database (GeoLite2-ASN)
VPN / proxyIP2Proxy PX12 (VPN, TOR, residential, threat, fraud score β‰₯ 80), a VPN-ASN listIP2Proxy PX12 / the ASN database
Bot blacklistsIPs and User-Agent signatures from Settings β†’ Botsβ€”
User-Agent heuristicsCrawlers and tools (facebookexternalhit, meta-externalagent, curl, python, headless…), an empty User-Agent, a missing Accept-Languageβ€”

If a required database is missing, the campaign editor shows a warning right in the cloak card.

Sensitivity

Signals are either hard (an explicit hit in a blocklist or reputation database) or soft (individually noisy heuristics).

LevelSafe page when
Lowonly a hard signal
Medium (default)a hard signal, or two soft ones
Highany single signal

Targeting filters

Applied after the passive layers; a mismatch means the safe page (TARGETING_SAFE):

JavaScript verification

Off by default. The visitor first receives the safe page and moves to the money page via a one-time signed link (TTL 5 minutes) only after executing JS. navigator.webdriver = true stays on the safe page. So does anything that does not execute JS. The price is one extra hop for every live visitor.

With the browser check on (Settings β†’ Bots), the same step also collects browser signals: in Soft or Strict mode a virtual machine, emulator or spoofed phone gets the safe page here, with a bc_ reason. The stream's Browser check* field can turn it off for this stream only.

Preloader. While the JS step runs (a fraction of a second) the visitor sees a loading page, configured per stream under JS Challenge Preloader: the built-in page, or your own HTML with a live preview. Historically this step reused the safe page's HTML β€” that markup is still shown when no preloader is configured, so existing campaigns keep their look; pick Custom HTML to override it. The verification probe is injected into your HTML automatically β€” do not add your own redirect scripts, they race the signed link.

Recording and reports

SettingDefaultWhat it does
Record Safe Page clicksonSafe-page hits are written with is_safe_page = 1. Turn it off and they will not reach the database
Exclude Safe Page clicks from reportsonHits stay in the click log but drop out of every report metric β€” clicks, visits, uniques, bots, empty referers, cost, CPV. A safe hit is still a visit to the campaign link, so with the box off it counts in "Clicks" too (since 1.8.5 clicks count every visit)

Even when hits are not written, the suppressed-hit counter (cloak_suppressed_stats) counts them per campaign, stream, day, and verdict β€” "zero clicks" will not hide the real traffic.

Global settings: Settings β†’ Bots

Diagnostics

Verdicts and reasons

Verdicts: money, passive_safe, targeting_safe, js_safe. Reasons are written to clicks.cloak_reasons; the main ones:

CodeMeaning
geo_country / geo_unknowncountry not in the list / country could not be determined
device_typedevice type not allowed
bot_isp, isp_blocklistISP in the bot and data-center list
datacenter_asn, asn_datacenterdata-center or hosting ASN
vpn_proxy_asnVPN or proxy provider ASN
iprange_datacenterIP in a published cloud or crawler range
hosting_isphosting keyword in the ISP name
ip2proxy_*an IP2Proxy signal: vpn_proxy, datacenter, residential, tor, bot, threat, high_fraud
bot_blocklistIP in the bot list
crawler_or_tool_ua, suspicious_ua, no_user_agent, missing_accept_languageUser-Agent and header heuristics
webdriver, js_missing, js_fingerprintJavaScript verification

Common problems

SymptomWhat to check
The ad dashboard shows clicks, the tracker shows zeroWhether Safe Page click recording is off; the suppressed-hit counter
100% of traffic on the safe pageWhether the geo database is installed (βš™ β†’ Geo databases); geo_unknown reasons in the click log
Live mobile users on the safe pageReason ip2proxy_vpn_proxy β€” remove the VPN/proxy layer (it is a hard signal; low sensitivity will not cancel it)
Meta or Telegram reviewers reach the offerTheir networks are not flagged as data centers by ASN; a single range hit at medium sensitivity is only a soft signal. Raise the sensitivity or add a "Bot" filter to an intercepting stream
← Previous
Campaigns and streams
Next β†’
Browser check
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 β†’