Docs

Troubleshooting

Most 'not tracking' reports come down to one of a few causes. Work through these in order.

The script isn't sending events

  • Ad blockers / privacy extensions. Many block analytics requests. Test in a clean browser profile.
  • Do Not Track. If the visitor's browser sends DNT, the script exits silently by design.
  • Domain mismatch. The request host must match the website's registered domain (subdomains are allowed). Check the domain in the site settings.
  • Wrong tracking ID. Copy the snippet again from settings — a mistyped ID returns 404 and the script disables itself for the rest of the page.
  • Localhost / file://. These are skipped on purpose; tracking only runs on real domains.
  • lumen_ignore flag. If localStorage.lumen_ignore is "true", the script stays off for that browser.

Debug logging

Add data-debug to the script tag, or append ?lumen_debug to the page URL, to log init/event/error details to the console.

Exclude yourself from stats

Open your site's console and run this once — it persists for that browser:

localStorage.setItem("lumen_ignore", "true");

To start counting yourself again, remove the key: localStorage.removeItem("lumen_ignore").

Numbers differ from Google Analytics

Lumenlytic is privacy-first and cookie-free, so it under-counts by design: no cross-day visitor stitching, DNT respected, and ad-blocked requests are simply not seen. Lower numbers here are expected and are the point.

Single-page apps

Client-side navigations are tracked automatically. If you only see the first pageview, confirm the script is loaded once in the root layout and not re-injected per route.