Headless browser
A headless browser is a browser that runs with no graphical interface, controlled entirely by code. Real users never run headless browsers — it's a tool for developers, scanners, and, more relevant to buyers, automated ad-network moderation. In PWA arbitrage, headless detection is one of the first filters standing between a visitor and the offer.
Why headless browsers get used against arbitrage traffic
Ad networks and antifraud platforms run headless Chrome or Chromium — via tools like Puppeteer or Playwright — to auto-check landing pages for policy violations, essentially a robot reviewer. That visit looks like a normal click at the user-agent level but carries none of the behavior a real person leaves behind: mouse movement, scrolling, natural pauses between actions. Fail to tell headless apart from a live visitor, and the offer gets flagged by an automated check before it ever turns a profit.
How APEX detects headless traffic and what it shows instead
APEX's antibot checks for headless environment fingerprints — flags like navigator.webdriver, window and rendering properties that don't match a real browser, and a lack of interaction events. When those trip, the visitor gets routed to the white page instead of the offer, and the cloaking engine handles it without manual setup on the buyer's side. It's the same layered logic used against datacenter IPs and emulators — all the signals work together.
FAQ
- Is a headless browser always a bot?
- In the context of a PWA landing page, practically yes — real users don't run headless mode; it's a tool for automated tests, scanners, and moderation, not ordinary traffic.
- Can headless be caught from the user agent alone?
- No, modern headless browsers can mask their UA to look like regular Chrome, so detection relies on extra JS-level environment signals rather than a single header.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free