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
| Mode | What it does | Risk of losing real visitors |
|---|---|---|
| Off | Nothing is collected; everything works as before | β |
| Observe only | Blocks nothing. The click card shows what looked suspicious and which browser it was | None |
| Soft (recommended) | Acts only on hard evidence (table below) | Minimal: real devices don't show these signs |
| Strict | Also acts on indirect signs | Yes: 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
- In a cloak stream with the JS check on (stream β cloak settings β JavaScript check), the signals are collected during that same JS step and judged before the money page is served. A browser the mode acts on gets the safe page right away. The cloak reason shows which sign it was, for example
bc_software_gpu. - Everywhere else (landings without the JS check, external pages with
tracking.js/kclient.js/kclient.php), the signals are sent from the landing after it loads. The click is marked as a bot (is_bot), which cleans up reports and feeds the "bot" stream filter. The visit itself isn't stopped: there is no intermediate step to stop it in, and adding one would slow down every real visitor.
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):
| Sign | Why a real device never shows it |
|---|---|
| Browser automation | navigator.webdriver is true, or the browser is HeadlessChrome |
| Virtual machine without a GPU | The 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 screen | A 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):
| Sign | When a real person shows it too |
|---|---|
| Timezone of another country | VPN users, travellers, roaming. Neighbouring zones with the same offset don't count |
| Browser language β header | Rare setups, some privacy extensions |
| Android on x86 | Emulators (BlueStacks, AVD) and a few Chromebooks |
| Platform spoof on desktop | A UA-switcher extension |
| Zero-size window | Old 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
- Click card β Browser check: the verdict (Clean / Suspicious / Bot), each sign with its detail (for example the exact GPU string), the platform, the browser timezone and where it was checked (cloak JS step or landing).
- Cloak reasons:
bc_software_gpu,bc_ua_platform,bc_mobile_no_touchand so on, with plain-language descriptions in the cloak diagnostics. - Settings β Bots β Browser check: visits checked over the last 7 days, how many were bots and suspicious, and the most frequent signs.
How to start safely
- 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.
- Switch to Soft. Turn on the JS check in the cloak streams where you want such visitors on the safe page.
- Use Strict only on traffic where VPN users and travellers don't matter to you.
Technical notes
- Collector:
/bc.js(β2 KB). In the cloak JS step it is inlined and its signals ride the next URL as_ocb. On landings it is loaded withdeferand posts once toPOST /pixel.gif?action=bc, signed with an HMAC of the click. - Verdicts: table
click_browser_checks(one row per checked click, cleaned with the click statistics retention). Migration 77. A second report for the same click is ignored. - Mode: setting
browser_check_mode(off/observe/soft/strict). Stream opt-out:"browser_check": "off"in the cloak stream's settings. - Code:
core/BrowserCheck.php,bc.js. Test:tests/browser_check_test.php.
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 βDocsInstallation and updates
Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.
Read guide βDocsMigrating from Keitaro
Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β what transfers and what to check.
Read guide βDocsMigrating from Binom
Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.
Read guide βDocsFeature overview
Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.
Read guide βDocsCampaigns and streams
The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.
Read guide βDocsCloaking
Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.
Read guide βDocsBrowser check
How the JS check catches bots, VMs and emulators through contradictions in the browser environment.
Read guide βDocsLanding pages
Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β the complete reference.
Read guide βDocsPWA and Web Push
Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.
Read guide βDocsPWA Funnel
A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.
Read guide βDocsConversion popups
Show real conversion events as on-page popups: setup, triggers and placement.
Read guide βDocsSession recordings and heatmaps
Replay real visits and see click and scroll maps. Storage limits and privacy notes.
Read guide βDocsContent gallery
Central storage for icons, screenshots and creatives used across PWAs and landings.
Read guide βDocsCreatives library
Store creatives with subid tracking and test them across campaigns.
Read guide βDocsExternal PWA and Telegram channels
Publish PWAs to external domains and run Telegram channels as a traffic source.
Read guide βDocsPostbacks and conversions
Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.
Read guide βDocsCosts
Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β and how the revenue aggregator works.
Read guide βDocsPush and pop networks
Working with push and pop traffic sources: feeds, zone optimization and the zone killer.
Read guide βDocsFacebook / Meta
Cost import from Meta Ads and the Conversions API: server-side events with deduplication.
Read guide βDocsDolphin / Fbtool
Receive Facebook costs through the Dolphin (Fbtool) API in real time.
Read guide βDocsFB comment cleaner
Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.
Read guide βDocsTraffic sources and affiliate networks
Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.
Read guide βDocsReports, logs and metrics
The report builder, saved reports, click logs and every metric explained.
Read guide βDocsDomains and SSL
Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.
Read guide βDocsCloudflare
How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.
Read guide βDocsAdministration
Users, roles and permissions, security settings, geo databases, updates and system health.
Read guide βDocsTelegram bot
Manage the tracker from Telegram: stats, conversions and alerts in chat.
Read guide βDocsMCP: an AI assistant in the tracker
Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.
Read guide β