Docs

Browser check

Catches bots, moderators' virtual machines, emulators and anti-detect browsers by contradictions the browser reports about itself. Examples: a software GPU instead of a real graphics card, "iPhone" in the User-Agent while the platform is Linux, a "phone" without a touch screen. Real phones, including the Facebook, Instagram and TikTok in-app browsers, show no such contradictions, so the check can act on them without cutting real visitors.

It is configured in one place for the whole tracker: βš™ β†’ Settings β†’ Bots β†’ Browser check.

What it is not

It is not a visitor ID and it does not count unique visitors. Fingerprints of real phones collide: every iPhone of the same model and iOS version looks practically identical, and in-app browsers even more so. Using a fingerprint for uniqueness would merge different people into one and undercount uniques. Orbitra never does that: uniques are counted exactly as before, by IP / IP+User-Agent. A short fingerprint is stored only as a diagnostic in the click card.

Modes

ModeWhat it doesRisk of losing real visitors
OffNothing is collected; everything works as beforeβ€”
Observe onlyBlocks nothing. The click card shows what looked suspicious and which browser it wasNone
Soft (recommended)Acts only on hard evidence (table below)Minimal: real devices don't show these signs
StrictAlso acts on indirect signsYes: a real person on a VPN, roaming or with unusual settings can be marked as a bot

Default: a fresh install starts in Soft. An existing install that updates to this version starts Off and the panel shows a one-time banner: Turn on soft mode / Learn more / Not now. An update never changes your routing by itself.

What "acts" means

So if you want the check to send suspicious browsers to the safe page, turn on the JS check in the cloak stream. Soft mode then protects that stream at no extra cost: the JS step already exists, and the check just runs inside it.

A single cloak stream can opt out: cloak settings β†’ Browser check β†’ Off for this stream.

The signs

Hard evidence (Soft and Strict act on it):

SignWhy a real device never shows it
Browser automationnavigator.webdriver is true, or the browser is HeadlessChrome
Virtual machine without a GPUThe WebGL renderer is software: SwiftShader, llvmpipe, Microsoft Basic Render Driver, VirtualBox, VMware. Phones always have a hardware GPU
Phone User-Agent on a desktop"iPhone" in the UA but the platform isn't iPhone; "Android" in the UA on a Windows/Mac platform. iOS always reports iPhone
Phone without a touch screenA phone UA with maxTouchPoints = 0 and no touch events
Client Hints: "not mobile"An Android phone UA while userAgentData.mobile is false

Indirect signs (only Strict acts on them):

SignWhen a real person shows it too
Timezone of another countryVPN users, travellers, roaming. Neighbouring zones with the same offset don't count
Browser language β‰  headerRare setups, some privacy extensions
Android on x86Emulators (BlueStacks, AVD) and a few Chromebooks
Platform spoof on desktopA UA-switcher extension
Zero-size windowOld headless builds. Desktop only: Android in-app browsers legitimately report 0

A missing signal never counts against the visitor. If WebGL is off (iPhone Lockdown mode, privacy settings), the GPU sign simply doesn't apply.

Where to see the results

How to start safely

  1. Turn on Observe only for a day or two and look at the stats and a few click cards. You see how much of your traffic would be affected, without any risk.
  2. Switch to Soft. Turn on the JS check in the cloak streams where you want such visitors on the safe page.
  3. Use Strict only on traffic where VPN users and travellers don't matter to you.

Technical notes

← Previous
Cloaking
Next β†’
Landing pages
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 β†’