Skip to content
Traffic Quality

Separate people from machines

Your default numbers are people, not requests.

Real People is the view every other module reads from. Known bots, verified crawlers and security traffic are excluded wherever classification is confident enough. Requests the classifier cannot place are reported as unresolved rather than folded into the human count, so the number is conservative by construction.

Real People

  • Human-only default in every metric
  • Per-class confidence thresholds
  • Unresolved traffic reported separately
  • Any class re-included on demand

How it helps

What Real People gives you

1

Confidence decides the split

Every classification carries a confidence level, and the exclusion applies only above the threshold you set. Traffic sitting below it is counted as unresolved and shown separately, so the human figure is never propped up by a guess.

2

One denominator, everywhere

Conversion rate from server events, revenue per visit from your finance system, channel comparisons and page reports all divide by the same human count. A denominator that quietly included crawlers would understate every rate on the site, and would understate them unevenly from page to page.

3

Comparisons survive rule changes

Classification rules change as new agents appear. Each change is dated, and a comparison can be run on one consistent ruleset, so a drop between two weeks is a change in behaviour rather than a change in definition.

Connect a site today. Read tomorrow's brief instead of building it.

Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.

Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo