Counter · Rate Limits

Counter Dev Rate Limits

Counter does not publish formal rate limits, quotas, or throttling tiers for its tracking, stats, or account endpoints. The tracking snippet is designed to be lightweight - it fires at most once per tab per session (guarded by a sessionStorage flag) plus one Beacon pageview per load - which naturally bounds collect traffic. Server-side protections (e.g. bot filtering, ignoring localhost origins) exist in the source but no numeric per-client limits are documented. Self-hosted deployments are bounded only by the operator's own infrastructure.

Counter Dev Rate Limits is the machine-readable rate-limit profile for Counter on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Web Analytics, Privacy, Open Source, Self-Hosted, and Rate Limiting.

3 Limits Throttle: not documented
Web AnalyticsPrivacyOpen SourceSelf-HostedRate LimitingQuotas

Limits

Tracking (collect) requests client
requests
see provider documentation
No published numeric limit. Snippet self-limits to one /track per tab per session plus one /trackpage Beacon per page load.
Stats / dashboard data requests account
requests
see provider documentation
No published numeric limit on /query or the /dump SSE stream.
Account endpoints account
requests
see provider documentation
No published numeric limit.

Policies

Bot Filtering
The /track endpoint drops requests from detected bots and from localhost/127.0.0.1 origins.
Client-Side Throttling
The tracking snippet fires once per tab per session via a sessionStorage flag, bounding collect volume.
Self-Hosted Scaling
Self-hosted operators scale Redis and the Go server to their own traffic; no upstream-imposed quota.

Sources