Troubleshooting installation

Installed the snippet but no data yet? Work down this list — one of these covers almost every case.

Is the snippet really live?

  • The snippet is in the <head> of your published site, not just a local or staging copy.
  • If a CDN or cache plugin sits in front of your site, clear its cache so the updated <head> is served.
  • View your page’s source in the browser and confirm the wa-XXXXXXXX.js script tag is present.

Are you testing somewhere it’s skipped?

To avoid junk data, the tracker deliberately ignores some environments:

  • Localhost. It doesn’t track on localhost, 127.0.0.1, .local hosts, or file:// pages. Test on your real domain.
  • Automated browsers. Headless and automation browsers (anything reporting navigator.webdriver or headless Chrome) are ignored. Test in a normal browser window.
  • You opted out. If you ran the exclude-your-own-visits snippet, this browser won’t be counted. Clear it with localStorage.removeItem('wazlytics_ignore').

Other things to check

  • Content blocker. Pause any privacy or ad blocker in your own browser while testing your first visit.
  • Content Security Policy. If your site sends a CSP, allow scripts from the Wazlytics script domain so the tracker can load.
  • Installed twice. Using the WordPress plugin and a manual snippet can load the tracker twice. Wazlytics guards against double-counting, but pick one method to keep things clean.

Tip

Give it a few seconds and watch the Realtime view as you load a page. Still stuck? Reach out to support and we’ll help you get connected.