You opened the live dashboard during a launch, saw the counter stall at 199, and felt a cold drop in your stomach. Did the site break? Did Product Hunt ghost you? Maybe. Or maybe you hit a realtime visitor cap: a deliberate limit on how many concurrent sessions get drawn on the map, pushed over the websocket, or labeled “active right now.”
Related reading: live launch guides. Read the main guide on launch-day live views for the playbook; this article explains why caps exist and how to interpret them without analytics superstition.
Two different numbers: “shown” vs “counted”
Founders mix these constantly:
| Concept | What it is | Typical use |
|---|---|---|
| Counted visitors | Events ingested and aggregated for hourly/daily totals | Pins, RPV, week-over-week |
| Displayed live sessions | Subset rendered for UX and cost | Globe dots, “active now” list |
A cap usually applies to display or live fan-out, not necessarily to whether your site recorded the pageview. After launch, your pinned range for yesterday should still show the full visitor total even if the live map never showed more than N dots.
Always check: does the product document cap on visualization or cap on ingestion? Ingestion caps are rare on paid tiers and serious on free tiers. Visualization caps are common everywhere because launches are spiky.
Why vendors cap realtime at all
Websocket and fan-out cost
Live dashboards push events to browsers. A launch that sends 50 pageviews per second multiplies by every open dashboard tab in your company, your investor’s phone, and that one Discord lurker with a shared link. Uncapped fan-out turns your analytics into a broadcast CDN you did not budget for.
Browser performance
A map with 10,000 animated points melts laptops. Thinning keeps frames usable. You still want the aggregate number in a big font; the map is illustration.
Privacy and fingerprinting vibes
Listing every live session with full path, referrer, and city block can feel like surveillance, bad for brand and bad for GDPR narratives. Caps plus aggregation (“12 active in Germany”) reduce creep factor while preserving coordination value.
Abuse resistance
Public or guessable live URLs get scraped. Rate limits stop someone from mirroring your traffic into their stream. Rotate shared links after launch if your tool allows it.
Common cap patterns you will see
Rolling window “active” definition. “Active” might mean “had an event in the last 5 minutes.” Late launch evening, active count drops while daily uniques keep climbing. That is not a bug; your definition cooled off.
Map point reservoir sampling. Show at most N random recent sessions on the globe. Count total in a header separately if the product is well designed.
Per-project connection limits. Fifth teammate opens live view → oldest connection drops. Looks like “traffic died” to one person only.
Geo bucketing. One dot per country per minute, not per user. Fine for “did US newsletter fire?” useless for “which city?”
Rate-limited counter animation. The big number updates every 10 seconds to save CPU. Humans perceive a stall; the backend still batches.
When evaluating tools, ask for a sentence in the docs on each pattern. Silence usually means “we throttle something; good luck.”
How to behave on launch day when you hit a cap
- Read the header total, not only the map. If the product separates them, trust the total for panic/recovery decisions.
- Open one live tab, not six. You reduce fan-out and your own anxiety (when live stats distract).
- Use referrers and top paths: they aggregate and rarely share the same thin cap as dots.
- Pin tomorrow. Daily charts rarely use the live visualization pipeline. Compare launch day to baseline in marketing pulse guides.
- Correlate money. A webhook row for new checkout does not care about map dots (webhook ROI stack).
When a cap might mean real data loss
Caps matter financially when they apply to ingestion or retention:
- Free tier drops events after N per month.
- Live-only sampling with no durable log (rare on marketing analytics; more common on toy counters).
- Aggressive bot filtering that deletes events instead of labeling them.
Run a post-launch audit: Stripe or Paddle gross for the day vs attributed revenue in analytics vs server access logs (sampled). Large gaps deserve a support ticket, not a tweet thread.
Caps vs sampling in A/B tests
Do not run rigorous experiments on capped live views. Use daily segmented reports. Live view is for operational response (“404 on pricing”) not statistical proof (“variant B won”).
Engineering-friendly mental model
Think of three layers:
Pageview → ingest queue → durable store → daily aggregates
↘ live projector (capped) → browserYour job as founder is to know which layer feeds payroll decisions. Almost always: durable store + pins, not live projector.
Talking to your team about caps
Script for Slack:
> “The map shows a sample of live sessions so the app stays fast. The daily total in the pin is the number we use for retro. If pricing traffic flatlines on paths while home spikes, we fix links, we don’t need 2,000 dots to see that.”
Investors and advisors may want the globe because it photographs well. Send a screenshot of the pinned spike the next day; it ages better than a frozen map frame.
Relation to bot traffic
Bots can consume live display budget faster than humans, same as they inflate visitor counts. Filtering strategy belongs in launch day bot swarm. Do not crank bot exclusion live unless you tested it; you may hide real mobile clients.
Choosing a tool with honest limits
Green flags:
- Docs explain active definition and map thinning.
- Daily totals match a simple export spot-check.
- Shared live links expire or are revocable.
Red flags:
- “Unlimited realtime” with no technical blog post.
- Counter resets at midnight UTC with no timezone note.
- No pinned ranges, only live.
Checklist before you blame the cap
- Confirmed whether stall is map-only or global counter
- Only one dashboard connection per watcher
- Compared top paths and referrers (uncapped aggregates)
- Scheduled pin for launch window tomorrow
- Revenue webhook firing in same product
FAQ founders ask in Discord
“If the live counter stalls, should I reboot the landing page?” No, check server health and checkout separately. Rebooting marketing mid-launch creates a second problem. Watcher compares path panel to baseline; if / loads, the stall is almost certainly display-side.
“Can I pay for unlimited dots?” Sometimes higher tiers raise fan-out limits. Ask whether the upgrade changes ingestion or only live projector capacity. Paying for prettier maps while daily exports stay capped is a bad trade.
“Our investor wants a live link, is that safe?” Use expiring read-only links if available. Remind them caps apply and that pinned charts are the number for follow-up emails. Send the pin screenshot the next morning so the narrative matches durable data.
“Does ad blockers affect the cap?” Ad blockers affect client-side trackers, not websocket caps. If live traffic looks low but server logs disagree, you may have a tagging problem unrelated to realtime limits, fix the snippet before launch rehearsal, not during hour one.
Next reads
- Live visitor dashboard guide, launch playbook
- Globe vs arcade UI, attention economics
- Live launch dashboard hub