Verify & Troubleshoot Your Humblytics Tracking Script

Purpose: Use this guide if your site in unable to get verified in the Humblytics dashboard after you’ve installed the tracking snippet.

1. Fast 4‑Point Checklist (90 seconds)

  1. Domain Match – Does the domain you entered in Humblytics exactly match the URL you’re loading? https://www.example.com ≠ https://example.com.

  2. Head Placement – The entire snippet must sit inside the global <head> tag on every page you want tracked.

  3. CSP / Ad‑Blockers – Confirm that app.humblytics.com isn’t blocked by a Content‑Security‑Policy header, browser extension, or firewall.

  4. Correct Script ID – The id= value in the snippet should match the Site ID shown in Settings → Install Tracking Code.

If all four items look good, click Verify Website again—most issues are resolved right here.

2. Full Troubleshooting Flow

2.1 Confirm the Script Loads (client‑side check)

<!-- Humblytics Global Tag -->
<script async src="https://app.humblytics.com/hmbl.min.js?id=YOUR_SITE_ID"></script>
<!-- End Humblytics Tag -->

  1. Open DevTools → Network → JS and refresh the page.

  2. Look for hmbl.min.js with a 200 status.

  3. If it’s missing or blocked:

    • Ad‑Blocker: Whitelist your domain or pause the extension and test again.

    • CSP Error: Add https://app.humblytics.com to script‑src & connect‑src.

    • Firewall: Allow outbound requests to *.humblytics.com.

2.2 Verify the Correct Domain

Scenario

Fix

Staging site (e.g. beta.example.com) connected, tracking prod (example.com)

Add each domain as a separate site in Humblytics.

Using ‘www.’ in browser but not in Humblytics (or vice‑versa)

Edit the site settings to match the exact domain.

2.3 Check for Head Placement Mistakes

  • Late Injection: Some page builders inject custom code after <body>—make sure your platform supports true <head> injection.

  • Per‑Page vs Global: Single‑page placement means only that template is tracked; use the global head / layout file.

2.4 Single‑Page Apps (SPA)

For React, Next.js, Vue, etc. place the tag in the global layout (e.g. _app.js, root.tsx). Humblytics automatically listens for history changes—no extra config needed.

2.5 Multiple Tracking Scripts Installed

Running legacy snippets from previous workspaces can cause ID mismatches. Remove duplicates and keep only the latest tag.

3. Frequently Asked Questions

"How long after verifying will I see data?"

Within 60 seconds of the first page view, real‑time visitors should appear in the dashboard.

"Can I keep Google Analytics on the site?"

Yes. Humblytics is async and <36 KB, so it runs alongside other trackers without conflicts.

"Do I need a cookie banner for verification?"

No. Humblytics is cookie‑free - verification succeeds regardless of consent prompts.

"What if my CMS doesn’t let me edit <head>?"

Most platforms (Webflow, Framer, Squarespace, WordPress) do. If yours doesn’t, embed the tag via a global header injection plugin or theme setting.

"My site uses a strict CSP—what directives are required?"

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

5. Still Stuck? We’re Here → [email protected]

  1. Send your live URL.

  2. Include a screenshot of DevTools → Network with hmbl.min.js filtered.

  3. We’ll reply within one business day—usually much faster.

Next Steps

  • Once verified, explore Heatmaps, Funnels, and Experiments in your dashboard.

PreviousFrequently Asked QuestionsNextHow to Get Started

Last updated

Was this helpful?