✦ Cookieless analytics, built around daily rotating IDs
☰
All featuresWeb AnalyticsCustom EventsCookieless AnalyticsIntegrationsPricingDocumentationComparisonsFree toolsBlogGlossary
PLANNED FEATURE

Plan transparent automated-traffic filtering

Automated traffic can distort reports. A validated bot classification and exclusion workflow is planned; the current product does not claim comprehensive bot detection.

Explore available event tracking ↗

Explain exclusions before hiding traffic

A useful bot report should distinguish raw collection from excluded activity and disclose which rules changed the count.

Check false positives

Shared networks, unusual browsers, and frequent requests are not proof of a bot. Classification should be reviewed against labelled examples and measured for mistakes.

Keep collection quality visible

Today, compare event names, paths, request context, and delivery behavior in the activity feed. Investigate unexpected traffic rather than assuming every spike is a person.

Current scope

Rate limits and input validation protect ingestion. They are not a bot detection score or a guarantee that automated traffic has been removed.

Frequently asked questions

Are all bots excluded today?

No. Comprehensive classification and exclusion are not implemented.

Is rate limiting bot detection?

No. It bounds request volume; it does not reliably classify visitors.

Where can I inspect unusual traffic?

Use activity and context filters to inspect the observed events.

Start with a clear measurement model.

Install the SDK, then explore traffic and product activity with the same definitions.