Fingerprint
A fingerprint is a set of browser and device parameters that identify it. In cloaking, a fingerprint helps filter bots and automated checks.
What a fingerprint consists of
User-agent, screen resolution, language, fonts, GPU, plugin set and other signals. Their combination is unique enough to tell a real device from an emulator or crawler.
Fingerprint in cloaking
The cloak matches the fingerprint against bot and auto-check traits: suspicious combinations go to white, live devices to the offer. It complements IP and user-agent filters.
FAQ
- Why does cloaking need a fingerprint?
- To more accurately tell live devices from bots and emulators and keep automated checks off the offer.
- Is a fingerprint just the user-agent?
- No, it is a combination of many signals (screen, language, fonts, GPU, etc.), which makes it harder to fake.
- Can a fingerprint cut real users?
- With crude tuning, yes. So filters are set carefully to avoid losing real mobile users.
Build your PWA in APEX in minutes
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free