Visitor Monitor
No schedule, no polling - a lightweight snippet on your site tells this uptime monitor when real traffic stops arriving.
A visitor monitor flips uptime monitoring around again: instead of Kawze calling your site, or your server calling Kawze, real visitors do the work. Drop a small snippet on your page and every real page load is a signal that your site is reachable and rendering. If that signal stops - no visitors, for longer than your grace period - the monitor goes down and alerts fire, even if a synthetic HTTP check from outside would have looked fine. On top of that, it can track resource load failures, failed fetch/XHR calls, and uncaught JavaScript errors happening in real visitors' browsers.
How this uptime monitor works
- Add the site URL for your own reference and get the embed snippet for this monitor.
- Add the snippet to your site - every real page load reports in, with no check schedule to configure.
- Set a grace period: how long after the last visitor hit before the monitor is flagged down, from 5 minutes up to a week.
- Optionally turn on tracking for resource load failures, fetch/XHR failures, and JavaScript errors seen in real visitor sessions.
- Optionally set a rate-alert threshold per error category - a count within a time window - so a single stray failure doesn't page anyone, but a genuine cluster does.
Visitor Monitor features
Every feature this monitor supports, and which plan it's included on.
Real-visitor-driven monitoring
FreeEvent-driven, not scheduled - the monitor is only as "up" as your actual traffic proves it to be.
Configurable grace period
FreeHow long after the last hit before the monitor is flagged down, from 5 minutes to a week.
Resource load failure tracking
FreeFlags failed image, script, and stylesheet loads seen by real visitors.
Fetch/XHR failure tracking
FreeFlags non-2xx or failed fetch()/XHR calls made by the page in the browser.
JavaScript error tracking
FreeFlags uncaught exceptions and unhandled promise rejections.
Per-category rate alerting
FreeAlert only when a category of error clusters past a count within a time window you choose, on top of the missing-traffic alert.
Tags and groups
FreeOrganize visitor monitors alongside your other monitors.
Email and SMS alerts
FreePer team member, open and recovery alerts on every channel.
Webhooks and Slack alerts
FreeRoute visitor-monitor alerts into Slack or any webhook endpoint.
Grace periods under 30 minutes
Entry+Free is limited to a 30-minute-minimum grace period; Entry and up can set it as low as 5 minutes.
What's free and what's paywalled
- Embedding the snippet, error tracking, and rate alerting are all available on every plan, including Free.
- The one gate is the grace period floor: Free requires at least 30 minutes of silence before alerting, while Entry, Mid, and Max can go as low as 5 minutes.
- Visitor monitors count against the same account-wide monitor limit as every other type (5 to 300, by plan).
Frequently asked questions
What is a visitor monitor and how is it different from a normal uptime monitor?
Instead of Kawze polling a URL on a schedule, a small snippet on your page reports every real page load. If real traffic stops arriving for longer than your grace period, the monitor is flagged down - catching situations a synthetic check from a single external location might miss.
Can it catch JavaScript errors, not just downtime?
Yes. Optionally track resource load failures, failed fetch/XHR calls, and uncaught JavaScript errors, with per-category rate alerting so isolated blips don't page anyone.
Is the visitor monitor free?
Yes - included on every plan, with a 30-minute-minimum grace period on Free and a 5-minute minimum on Entry and up.