Open AnalyticsOpen Analytics
Home/Documentation

Troubleshooting

Common issues and how to fix them. Most tracking problems come down to a missing script, wrong site key, or an ad-blocker.

No data is appearing in my dashboard

  • Check that the script tag is actually present in the HTML source of your page (use View Source, not DevTools Elements — DevTools may show injected nodes).
  • Confirm the data-site-key attribute matches the site key in your dashboard exactly.
  • Open the Network tab in DevTools and look for a POST request to /api/events. If it is blocked, an ad-blocker may be active.
  • Verify data-endpoint points to the correct URL — copy the snippet from Settings → Tracking code to be sure.
  • Data can take up to 10 seconds to appear. Hard-refresh your dashboard.

My bounce rate looks wrong / too high

  • Bounce rate is calculated per visit. A visit that has only one pageview counts as a bounce.
  • If your SPA navigation is not being tracked, every "page" looks like a single pageview. Confirm the script is loaded before the router initialises. See SPA routing.

Custom events are not showing up

  • Make sure you call OpenAnalytics.track only after the script has loaded. Use optional chaining (OpenAnalytics?.track) or a load event listener.
  • Custom events appear in the Custom Events card on the Overview and Stats pages.

I see my own visits in the stats

  • Go to Settings → Tracking exclusions and add your IP address using the Add my IP button.
  • Alternatively, install an ad-blocker on your development browser.
  • Events from localhost and 127.0.0.1 are filtered automatically in the dashboard.

The script is blocked by Content Security Policy (CSP)

Add your analytics domain to your CSP directives:

Content-Security-Policy: script-src 'self' https://analytics.gitopen.dev; connect-src 'self' https://analytics.gitopen.dev;

Realtime globe has no markers

  • Geo data requires the tracker's IP lookup to succeed. Some browsers or networks block third-party geo requests.
  • Visitors still appear in the live count and page list even without geo — only the globe markers are affected.

Search Console shows no data

  • You must connect Search Console separately from dashboard sign-in. See Search Console setup.
  • The Google account you connect must have access to the property in Google Search Console.
  • Search Console data has a 2–3 day delay from Google.

Bot Analytics shows no visits

  • Confirm your Cloudflare Worker is deployed and active. See Bot Analytics.
  • Check that bot tracking is not paused in Settings → Bot Analytics.
  • Bot visits are detected server-side — the main tracker.js script does not track bots.

Still stuck?

Review the Installation guides for your framework, or check Script options for configuration details.