Bot detection
Automated traffic can inflate page views, sessions, and conversion rates. leadmaps identifies traffic that is clearly automated and keeps it separate so your human analytics remain useful.
Hosted leadmaps manages detection automatically. You do not need to maintain bot lists or write filtering rules.
What leadmaps does
Section titled “What leadmaps does”Browser events are checked for automation when they reach the collector. Events classified as automated are kept out of human-focused analytics. The detection is used for analytics filtering only. It does not block crawlers from your website or replace your site’s crawler access controls.
Detection methods can change as automated traffic evolves. The detailed rules remain internal so they cannot be used as an evasion guide.
What you see
Section titled “What you see”The dashboard’s Bot traffic card shows the number and percentage of events classified as automated for the selected period. The query API also provides a per-site breakdown.
These results are aggregate. Customer-facing reports do not expose visitor identities, network addresses, or the internal details behind a classification.
Hosted leadmaps
Section titled “Hosted leadmaps”No setup is required. Detection is managed as part of the hosted service.
Self-hosted collector
Section titled “Self-hosted collector”Choose how events classified as automated are stored:
BOT_MODE=tag| Value | Behavior |
|---|---|
tag | Store automated events with is_bot=true, exclude them from default human analytics, and keep them available for reporting. This is the recommended default. |
drop | Do not store automated events. This can save storage, but discarded events cannot be reviewed or reported later. |
Use tag while evaluating the results. Change to drop only when losing the
historical breakdown is acceptable.
Privacy
Section titled “Privacy”Bot detection does not turn anonymous analytics into identity tracking. Anonymous analytics remain anonymous, and customer-facing results contain only aggregate classification information.
Limitations
Section titled “Limitations”No detector catches every sophisticated automated browser. leadmaps favors keeping uncertain traffic over wrongly excluding a real person’s activity.
To exclude visits from your own team, see Internal traffic exclusion.