Verify & Troubleshoot Tracking

Use this guide if Humblytics can't verify your site, or your visits aren't showing up, after you've installed the tracking code.

How to verify

1. Publish or deploy your site with the tracking code in the <head>.

2. In Humblytics, open Site settings → Install and click Verify install. During first-time setup, the button is I've added it - check now.

3. Open your live site in a private window, with ad blockers off, and click around.

4. Go to Observe → Analytics → Overview. Your visit shows in Live Activity within about a minute.

Quick checklist

Most problems are one of these four:

Check	What to look for
Published	Drafts, editor previews, and localhost don't verify. Publish or deploy, then test the live URL.
Domain matches	The domain in Humblytics matches the one you're visiting. www.example.com and example.com count as different. If one redirects to the other, add the final one.
In the <head>	The snippet sits in the global <head> of every page, not in the footer or a single page.
Correct ID	The id= value in your site's snippet matches the one in Site settings → Install. Remove old snippets from previous sites or workspaces.

Check that the script loads

1. On your live site, open DevTools (F12) → Network.

2. Refresh the page and filter for hmbl.min.js.

3. A 200 status means the script is loading.

If it's missing or blocked:

• Ad blocker or browser extension: pause it and test again.

• Caching or optimization plugin: clear the cache, and exclude Humblytics from JavaScript combine, defer, and delay settings. See WordPress for common plugins.

• Content Security Policy: allow Humblytics (below).

• Firewall: allow outbound requests to app.humblytics.com.

Some builders, such as GoHighLevel, add tracking code after the page loads, so it won't appear in View Page Source. The Network check above still works.

Content Security Policy (CSP)

If your site sends a CSP header, allow Humblytics in script-src and connect-src:

Content-Security-Policy:
  script-src 'self' https://app.humblytics.com;
  connect-src 'self' https://app.humblytics.com;

The snippet also includes a small inline script. Under a strict CSP, allow it with a nonce or hash, or with 'unsafe-inline' if your policy already uses it.

Single-page apps

For React, Next.js, Vue, and similar apps, add the script once in the global layout or index.html. Humblytics tracks route changes on its own, with no extra code.

Messages you might see

"Verify says not installed, but I see traffic." The check can miss a working install because of ad blockers, cached pages, or single-page-app timing. If your dashboard already shows visits, tracking works. Re-check from Site settings → Install after clearing your site's cache.

"Waiting for visitors." The script is installed, but no page views have arrived yet. Visit your site in a private window. If nothing shows up within a minute, run the checks above.

"Couldn't launch test." This can happen right after a Humblytics update, when your browser's saved copy of the app is out of date. Hard refresh (Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows) and try again. If it keeps happening, recreate the draft test or contact support.

Common questions

Can I keep Google Analytics? Yes. Humblytics loads asynchronously and runs alongside other trackers.

Do I need a cookie banner? The Humblytics analytics layer does not itself require a cookie-consent banner, but your site may still need consent for other tools or uses. Verification works with or without consent prompts.

My platform doesn't let me edit the <head>. Use Google Tag Manager, or a header-scripts plugin or theme setting.

Still stuck?

Email [e-mail] with your live URL and a screenshot of DevTools → Network filtered for hmbl.min.js.