How many HeronSignal signals should a website expect?
A practical guide for estimating tracked signals by use case, so SaaS teams can understand usage, pricing, and what HeronSignal collects by default.
What HeronSignal counts as a signal
A signal is a useful piece of product or technical evidence collected from a real session. It can be a page view, click, performance metric, frontend error, failed network request, custom business event, or log message.
HeronSignal is not trying to store everything forever. Raw diagnostic data is short-lived, while important aggregated analytics and saved analysis history are kept so teams can still understand long-term trends.
- Traffic signals: page views, sessions, visitors, referrers, and campaign context
- Experience signals: page load, LCP, FCP, INP, CLS, and server response timing
- Reliability signals: frontend errors, failed resources, failed requests, and health checks
- Business signals: custom events such as demo_requested, signup_started, or checkout_completed
Typical signal ranges by use case
The exact number depends on how interactive the product is, how much logging is enabled, and whether the app sends custom business events. A static marketing page usually creates fewer signals than a SaaS dashboard with many clicks, API requests, and flows.
For planning, it is better to think in ranges instead of one fixed number per visitor.
- Landing page or brochure site: around 8–20 signals per visitor
- SaaS marketing site with forms and CTAs: around 15–40 signals per visitor
- Logged-in SaaS dashboard: around 30–80 signals per visitor
- Diagnostic-heavy setup: higher volume if console, network, and custom events are all enabled
Example: a SaaS with 1,000 visitors per month
A SaaS website with 1,000 monthly visitors might generate about 20,000 to 80,000 signals, depending on the number of pages viewed, clicks, logs, failed requests, and custom events.
That is why HeronSignal plans are based on tracked signals rather than only visitors. Two companies can have the same visitor count but very different diagnostic depth.
- Simple website: Free or Starter can be enough
- Active SaaS product: Starter is usually safer than Free
- Growing SaaS with funnels, logs, and network diagnostics: Growth is usually a better fit
- High-traffic or multi-team product: Scale should be sized with the team
How to keep signal volume useful
More signals are not automatically better. The goal is to collect enough evidence to explain what users experienced without creating noise.
A good setup tracks real journeys, important clicks, frontend errors, failed network requests, performance metrics, and business events. It avoids sensitive data, form values, and unnecessary custom logs.
- Use custom events for meaningful milestones, not every tiny UI state
- Track failed or slow network requests instead of every successful request
- Keep console capture optional when production logs are noisy
- Use funnels to connect technical signals to business outcomes
Ready to monitor real website experience?
Use HeronSignal to connect real visitor signals, frontend diagnostics, funnels, and AI guidance.