Start here

Almost everything that goes wrong is one of five things. Work down this list before reading anything else — it usually takes two minutes.

1. Open your site and watch Live

   Open Live in one tab and your website in another, then reload a page. If a visitor appears, tracking works and the problem is somewhere else. Remember the live view only covers the last 30 minutes.

2. Check the network request, not the console

   The script never logs anything, so an empty console proves nothing. In the browser’s Network tab, look for a request to /api/collect. A 202 means it was accepted. No request at all means the script did not load or did not run.

3. Check data-domain

   The domain in the tag must match the site you are looking at in Statsy. Beacons from any other host are dropped silently, and the request still answers 202, so this is the most common invisible cause. No data arriving has the details.

4. Rule out a blocker

   Try a browser with no extensions, or a private window. If data appears there but not in your normal browser, it is an ad blocker. See Ad blockers.

5. Check whether you are counted as a bot

   Headless browsers, Lighthouse, Playwright, uptime monitors and link previews are all classified as bots and reported separately, not as visitors. So is a request with an empty user agent.

By symptom

Things that look like bugs but are not

• Live shows nobody. The window is 30 minutes. If nobody has visited in half an hour, it is correctly empty.
• A long date range shows less detail. Raw events are kept 90 days, so queries that need them are clamped. Totals go back further. See Data retention.
• Your own visits are missing. Check whether your IP or the path is in the exclusion lists in site settings.
• Your trial ended and you cannot change anything. Data still arrives; the dashboard is read-only until you pick a plan.

Still stuck? Email support@statsy.co with your domain and roughly when you expected the data.