How Tapper uses browser fingerprints to detect invalid traffic

Tapper reads signals from each visitor's browser to tell people from bots. With the visitor's behavior on your page, they feed one decision: is this click valid?

What the signals tell Tapper

• Whether the browser's details agree with each other. A browser that claims to be one device but reports the screen, language or settings of another is often spoofed or automated.
• Whether the browser is automated. Headless browsers, automation tools and virtual machines leave signs that normal browsers do not.
• Whether the browser stays the same across visits. A person's browser is stable; bots often change it between sessions.
• Whether language and time zone fit the IP address. A browser set to one region on an IP address in a distant one points to a proxy or a spoofed location.
• How the visitor behaves. Scrolling, clicking, tab focus and the timing between actions. Bots often behave in ways that are too uniform or too perfect.

What you need to do

Nothing to configure: install Tapper's monitoring script on your landing pages. For repeat offenders who change IP address, see Device blocking. The verdict: How Tapper decides a click is invalid.