Visitor behavior doesn't match normal browsing
Navigation repeats or looks unusual across visits.
See the browser evidence and visitor journeys behind each classification.
No card · No ad account connection · No blocking
Illustrative example: request_bot, classified from 4 linked signals (no JS, curl lib, no cookies, tor exit), action block.
Connect the paid click to the visitor, the path they took, and the outcome that followed.
Compare paid clicks with what visitors actually do after they arrive. High questionable traffic only matters when it changes business outcomes.
| Channel | Paid clicks | Questionable | Reached checkout | What this means |
|---|---|---|---|---|
| Google Search Ads | 2,246 | 44.5% | 3.4% | High volume + worth reviewing |
| Google Display Network | 1,053 | 44.4% | 1.1% | Weak post-click behavior |
| Meta Ads | 282 | 37.2% | 2.7% | Better than display |
| Google Demand Gen | 164 | 51.2% | 0.9% | Small volume, poor quality |
Follow paid traffic beyond the click.
Illustrative example data, not customer results. Select a page to follow its visitors.
Button weighs several independent signals and tells you what they add up to. No one has to understand TLS fingerprints or network reputation to use it.
Navigation repeats or looks unusual across visits.
The browser claims one thing, and its device signals say another.
Proxy, datacenter or previously suspicious networks.
Button holds off instead of guessing.
Traffic Detective examines whether questionable visits behave differently after they land. Understand the evidence, the uncertainty and the practical implications before recommending a campaign or protection change.
Inspect the journey behind a visit and see which checkout, signup and other goal pages it reached.
Even once your ad platform tag (like Google Ads) runs through Button, the platform sees the same signals it always has. Nothing changes until you choose to act.
See how much questionable traffic reaches your checkout, signup and other goal pages, not just how many clicks it costs.
Inspect classification reasons, browser signals and the journeys behind the visits. →
Invalid ad interactions and bot visits overlap, but aren't interchangeable. →
Not necessarily. Short visits also happen for ordinary reasons. →
Review automation signals and request patterns, not just the user-agent string. →
Inspect what those visitors actually do before excluding a whole group. →
More answers in the Knowledge Base →
The answer should always tell you what was observed, what remains uncertain, and whether there is enough evidence to act. See a real investigation and a decision not to block →