Reduce usage
Keep analytics useful by excluding low-value traffic and avoiding unnecessary events.
If event volume is high, cut noise with traffic exclusions so unwanted hits never count toward quotas.
Start with low-value traffic
Common candidates:
- Internal dashboards such as
/app/*. - Admin tools such as
/admin/*. - Preview, staging, or QA hostnames.
- Your own browser with
localStorage.kobbe_ignore = "true". - Countries you do not serve, when the traffic is clearly not useful.
For example, a SaaS might care most about marketing pages, signup, checkout, and onboarding. Logged-in app traffic can be noisy if product analytics already live somewhere else.
Do not exclude conversion paths
Be careful with pages that explain whether your marketing works:
- Signup, checkout, payment success, and onboarding pages.
- Landing pages used in campaigns.
- Funnel steps you measure in Kobbe.
- Pages where custom events fire, such as
Signup completedorCheckout started.
If you exclude a conversion page or event, Kobbe cannot include it in dashboards or funnels.
Watch optional tracking features
Optional features can increase event volume:
- Hash page paths can add pageviews on
hashchange. - Scroll tracking adds one custom event per marked section per page visit.
- Performance and Web Vitals adds one performance payload per page visit when enabled.
- Cross-domain tracking can make more of a multi-domain journey visible in one site.
These are useful when configured intentionally. Keep event names and marked sections focused on decisions you actually make.
Use exclusions
Use Exclude visits to configure:
- Path rules.
- Hostname rules.
- Country rules.
- IP rules.
- Browser-level ignore for your own device.
Exclusions apply before events are stored or counted toward quotas.