Quantity

Your subscription includes one visit pool for the billing period. Every site on your account draws from the same pool. When the published limit is reached, counting pauses until the next period.

What the visit pool covers

StatelessID sells one monthly subscription. That subscription includes a fixed number of countable visits for each billing period. A visit is recorded when the server receives a beacon from your tracking script, verifies it as real visitor traffic, and stores it on your dashboard board. Bot traffic filtered before counting does not consume the pool. Country-blocked traffic rejected before counting does not consume the pool either.

The visit pool is shared across every site registered under your account. If you run three sites and they collectively receive traffic during the month, all of that traffic counts against the same pool. There is no per-site sub-quota and no way to reserve capacity for one hostname while another draws more. The account settings page shows how much of the pool you have used and how much remains for the current period.

The published visit limit is the number shown on /pricing and in your account settings. That figure is the capacity you are buying for the period. See /pricing for the subscription price and the exact visit allowance included with it. Help articles describe how counting works; dollar amounts live on /pricing only.

How visits are measured against the pool

Each countable visit subtracts one from the remaining pool for the current billing period. The counter runs continuously from the moment your subscription is active until the period ends or the published limit is reached. The dashboard quota indicator reflects usage in near real time so you can see whether you are on pace to finish the period with headroom or whether you are approaching the ceiling.

The pool resets at the start of each new billing period. There is no rollover. Visits you did not use in one period do not carry forward to the next. Each period begins with the full published allowance again. Planning around seasonal traffic means accepting that quiet months do not bank capacity for busy months within the same subscription model.

If you are comparing this count to another analytics tool, use raw page loads rather than sessions or unique visitors. StatelessID counts page loads that pass its filters. A session-based or identity-based tool will show different numbers because it is answering a different question. The visit pool is sized for countable loads on your board, not for deduplicated people.

What happens when the pool is used up

When your usage reaches the published visit limit for the period, counting pauses. New beacons may still arrive at the server, but they are not recorded on your dashboard. Your board remains open and shows everything counted before the pause. The gap in the record during the paused window is permanent — those visits are not recovered when the next period starts.

Counting resumes automatically when the new billing period begins. There is no manual reset button and no mid-period purchase that raises the ceiling. The subscription includes one allowance per period. If you regularly hit the limit before the period ends, see the Exhausted help article for what the dashboard shows and how to read the situation honestly.

Watching usage halfway through the period is the practical habit. Compare your daily visit trend on the board to the days remaining in the period. A sudden spike from a referrer you did not expect can drain the pool faster than your publishing schedule alone would suggest. Catching that early gives you time to understand the traffic even though the pool itself cannot be expanded mid-cycle.

One plan, one pool, no quantity changes

There is no visit slider, no yearly billing option, and no ladder of quantity tiers. You subscribe once at /pricing and receive the visit allowance defined there. The subscription quantity is fixed at one unit — you cannot add a second unit of capacity to the same account or schedule a different allowance for the next renewal.

That simplicity is deliberate. Your access key opens one account with one shared pool and up to ten domain slots. All limits are defined in the single plan. If the published allowance fits your traffic pattern, you have a stable monthly rhythm. If it does not, the honest choices are to reduce countable traffic through filters where appropriate, accept a paused record during peak weeks, or evaluate whether the service matches your volume — not to hunt for a larger tier that does not exist.

Unused visits at period end simply expire. They are not refunded and they are not banked. Paying for the period means the infrastructure stayed ready whether or not your sites sent traffic every day. The Non-Use help article explains renewal during quiet months. The Cancel help article explains leaving when the service no longer fits.

Troubleshooting

If the quota indicator is climbing faster than you expect, open the board for each registered site and check referrers and daily totals. External links, aggregator pickups, and social shares can deliver bursts that have nothing to do with your posting calendar. Also review whether bot traffic is unusually high — filtered bots do not count, but misclassified traffic can still move the number.

If you believe counting stopped early, confirm the period end date in account settings and compare it to the published visit limit shown there. A browser cache on the settings page can display stale usage. Hard-reload the page. If the exhausted state persists and the numbers still look wrong, contact support with your access key and the approximate date the pause began.