Back to Blog

Common Humblytics Installation Issues (And How to Fix Them)

Having trouble setting up Humblytics? This troubleshooting guide covers the most common installation issues — from script placement and CMS configurations to verification failures — with step-by-step fixes.

Common Humblytics Installation Issues (And How to Fix Them)

Common Humblytics Installation Issues (And How to Fix Them)

Introduction

Humblytics is built to get you up and running fast. Most users have their analytics tracking live in under five minutes — a single lightweight script (just 36KB), no cookies, no complex configuration. It works across every major website platform, from Webflow and Framer to WordPress, Shopify, and custom-built sites.

But sometimes things don't go exactly as planned. Maybe your dashboard isn't showing any visitors. Maybe verification is spinning longer than expected. Maybe your A/B test isn't firing.

The good news? Nearly every Humblytics installation issue has a quick, straightforward fix. This guide walks you through the eight most common setup problems, explains exactly why they happen, and shows you how to resolve each one in minutes. Bookmark this page — it's the only troubleshooting reference you'll need.

Issue #1: No Data Showing After Installation

This is the single most common issue new users encounter. You've added the script, published your site, and opened your Humblytics dashboard — but the visitor count sits at zero.

Why It Happens

In most cases, the tracking script is installed but something small is preventing it from connecting to your dashboard. It's rarely a bug — it's almost always a configuration detail.

The Fix: Run Through This Checklist

Work through each item in order. Most users find their answer in the first three steps.

  1. Confirm the script is in the <head> section. Humblytics requires the tracking script to load in your page's <head> tag, not the <body> or footer. This ensures the script initializes before the page renders. See Issue #2 below for platform-specific placement instructions.

  2. Make sure your site is published. If you're working in a site builder like Webflow or Framer, saving your changes in the editor isn't enough. You need to hit Publish so the changes go live on your actual domain.

  3. Verify the domain matches exactly. The domain registered in your Humblytics dashboard must match the domain where the script is installed. We cover this in detail in Issue #3.

  4. Double-check your script ID. Each Humblytics account has a unique script snippet. Make sure you copied the correct one from your dashboard — especially if you manage multiple sites.

  5. Wait at least 60 seconds. After publishing, give the system a moment to register the first pageview. Refresh your dashboard after a minute.

Still Stuck?

  • Open your published site in an incognito or private browsing window to rule out browser extensions or cached versions.
  • Right-click your page, select Inspect, and open the Console tab. Look for any errors related to script loading. If you see a network error or 404 for the Humblytics script URL, the snippet may have been pasted incorrectly.
  • Clear your browser cache and reload. Cached versions of your site may not include the newly added script.

Issue #2: Script Placed in the Wrong Location

Where you place the Humblytics tracking script matters. The script must be inside the <head> tag of your HTML document — not in the <body>, not in the footer, and not inside a specific page component.

Why Placement Matters

The <head> section loads before the visible page content renders. Placing the script here ensures Humblytics captures the full pageview from the moment a visitor arrives. When the script is placed in the <body> or footer, it loads later in the page lifecycle, which can cause missed pageviews, inaccurate session data, or the script not running at all on fast-loading pages.

Platform-Specific Placement Guide

Every website builder handles custom code injection slightly differently. Here's exactly where to place your Humblytics script on each major platform.

Webflow

The recommended approach is to install Humblytics via the Webflow App Store integration — it's a one-click setup that handles placement automatically.

If you prefer manual installation, go to Site Settings → Custom Code → Head Code. Paste your script there. Do not use the Footer Code field. After adding the script, make sure you Publish your site for changes to take effect.

Framer

Navigate to Site Settings → General → Custom Code. Paste the Humblytics snippet into the Head field (sometimes labeled "End of <head> tag"). Do not use the "End of <body>" field. Publish your site after saving.

WordPress

If your theme supports it, add the script directly to your header.php file, just before the closing </head> tag. Alternatively, use a plugin like Insert Headers and Footers or WPCode that lets you inject code into the <head> section without editing theme files. This is the safer option if you're not comfortable editing PHP templates.

Shopify

Open your Shopify admin, go to Online Store → Themes → Edit Code. Find the theme.liquid file and paste the Humblytics script before the closing </head> tag. Save and you're set — Shopify publishes changes immediately.

Next.js

For the Pages Router, add the script to pages/_document.tsx inside the <Head> component. For the App Router, add it to app/layout.tsx using Next.js's built-in <Script> component with strategy="beforeInteractive" or by placing it directly in the <head> section.

React (Single-Page App)

Open public/index.html and paste the Humblytics script inside the <head> tag. This file serves as the shell HTML document for your entire app, so the script will load on every route.

Issue #3: Domain Mismatch

The domain registered in your Humblytics dashboard must match the domain where your site is actually live. If there's a mismatch, the tracking script will load but your dashboard won't associate the incoming data with your account.

Common Mistakes

  • Including or excluding www. If your site lives at www.example.com but your dashboard is set to example.com (or vice versa), data won't appear. These are treated as different domains.
  • Using a staging or preview subdomain. If you're testing on staging.example.com or a builder preview URL like project-name.webflow.io, but your dashboard is registered to example.com, nothing will track.
  • Protocol doesn't matter — but the domain does. Whether your site uses http:// or https:// is irrelevant for matching purposes. Only the domain name itself needs to match.

How to Fix It

  1. Log into your Humblytics dashboard.
  2. Go to Settings and check the domain listed for your site.
  3. Compare it to the URL in your browser when you visit your live site.
  4. If they don't match, update the domain in your dashboard to the exact domain your visitors see in their address bar.

Issue #4: Verification Taking Too Long

After adding the Humblytics script, the setup wizard asks you to verify the installation. Normally this takes about 30 seconds — you'll see a green confirmation almost immediately. But sometimes the verification spinner keeps going.

Why It Happens

Verification works by detecting a live pageview from your domain. If the system can't detect one, verification stalls. This is almost never a server-side problem — it's nearly always one of the issues below.

How to Fix It

  • Refresh your live site in a new browser tab. The verification system needs at least one real pageview. Open your published site (not the editor preview) in a fresh tab to trigger it.
  • Try an incognito window. Browser extensions — especially ad blockers or privacy tools — can sometimes prevent the tracking script from loading. Incognito mode disables most extensions by default.
  • Confirm the site is published, not just saved. In Webflow, Framer, and similar builders, saving in the editor doesn't push changes live. You need to explicitly publish.
  • Framer users: Make sure you're visiting your custom domain, not the .framer.website preview URL. The preview domain won't match the domain in your Humblytics dashboard.
  • Webflow users: After publishing, make sure you published to your primary custom domain, not just the .webflow.io staging URL.

If verification is still stuck after trying all of the above, it's likely one of the other issues in this guide (wrong placement, domain mismatch, etc.). Resolve those first, then return to verification.

Issue #5: Partial or Intermittent Tracking

Your dashboard shows some data, but the numbers seem low or inconsistent. Pages that you know receive traffic aren't appearing, or sessions drop off unexpectedly.

Common Causes

The script isn't on every page template. This is especially common on WordPress sites that use multiple page templates or theme layouts. If the Humblytics script is only in your main header.php but your site uses a separate template for landing pages, blog posts, or product pages, those pages won't be tracked. Make sure the script is placed in a global layout or template that loads on every page.

JavaScript errors on the page are blocking execution. If another script on your page throws an unhandled error before Humblytics loads, it can prevent subsequent scripts from executing. Open your browser's developer console (right-click → Inspect → Console) and look for red error messages. Fixing those upstream errors will restore Humblytics tracking.

Browser-based ad blockers or privacy extensions. Humblytics is designed with ad-blocker resistance — our cookie-free, privacy-first approach means most blockers don't flag the script. However, aggressive browser-level privacy extensions on your own device might still interfere. To confirm, check your analytics from a different device or browser without extensions installed. Your visitors are unlikely to be affected at the same rate.

The Fix

  1. Ensure the Humblytics script is in a site-wide template (e.g., a global header, layout file, or site-level custom code injection).
  2. Check your browser console for JavaScript errors on affected pages.
  3. Test from a clean browser session to rule out local extension interference.

Issue #6: A/B Test Not Running

You've created a split test in Humblytics, but traffic isn't being split between your variants and results remain empty.

The Checklist

  1. Is the experiment status set to "Active"? New tests start in draft mode. Make sure you've activated the test from your dashboard.
  2. Are both variant URLs live and publicly accessible? If either variant page returns a 404 or is behind a password, the test can't run.
  3. Is the Humblytics script installed on both variant pages? This is the most commonly overlooked step. The tracking script must be present on every page involved in the test — including the variant. If you duplicated your page in Webflow or Framer, confirm the variant page also has the Humblytics script in its <head>.
  4. Check for geo or audience restrictions. If you've configured the test to target a specific geography or audience segment, make sure your own location and device match those criteria, or test with restrictions temporarily removed.

For a deeper walkthrough on setting up tests, check out our guides on A/B split testing in Webflow and A/B split testing in Framer.

Issue #7: Form Submissions Not Tracking

Humblytics automatically tracks standard HTML form submissions — no extra configuration needed. If you're using native <form> elements, submissions should appear in your dashboard as events.

Third-Party Form Providers

If you're using an embedded third-party form tool — like Typeform, HubSpot, Cal.com, or Tally — automatic detection won't work because these tools use iframes or JavaScript-rendered forms that bypass standard form submission events.

For these integrations, you'll need to use the Humblytics.trackFormSubmission() JavaScript hook to manually fire a tracking event when the form is submitted.

Example: Tracking a Typeform Submission

// Listen for Typeform submission event
window.addEventListener('message', function(event) {
  if (event.data && event.data.type === 'form-submit') {
    Humblytics.trackFormSubmission({
      formId: 'typeform-contact',
      formName: 'Contact Form'
    });
  }
});

This sends a form submission event to your Humblytics dashboard with a custom form ID and name so you can identify it in your reports.

For complete integration guides covering Typeform, HubSpot, Cal.com, Tally, and other providers, visit our documentation.

Issue #8: Heatmaps Not Generating

You've enabled heatmaps in Humblytics but the heatmap view for your page is empty or shows a "not enough data" message.

Why It Happens

Heatmaps require a minimum number of visitor interactions before they generate a meaningful visualization. If your page hasn't received enough traffic since you enabled the heatmap, the system holds off on rendering to avoid misleading data from a tiny sample size.

How to Fix It

  1. Confirm the heatmap is created and set to "Recording." In your Humblytics dashboard, navigate to the Heatmaps section and verify the heatmap for your target page is active and recording.
  2. Check that the page URL matches exactly. The URL you entered when creating the heatmap must match the live page URL character for character — including trailing slashes, query parameters, or path segments. A mismatch means clicks are being recorded but not associated with your heatmap.
  3. Give it time. Once enough visitors interact with the page, the heatmap will generate automatically. For pages with lower traffic, this may take a day or two. Higher-traffic pages typically generate usable heatmaps within hours.

Quick Reference Troubleshooting Checklist

Use this summary checklist when something isn't working. It covers the most common fixes at a glance.

  • Script location: Confirm the Humblytics script is in the <head> section, not <body> or footer.
  • Site published: Make sure your site is published to your live domain (not just saved in the editor).
  • Domain match: The domain in your Humblytics dashboard matches your live site URL exactly (including or excluding www).
  • Script ID: Verify you're using the correct script snippet for this specific site.
  • Wait time: Allow at least 60 seconds after publishing before checking for data.
  • Incognito test: Open your site in an incognito window to rule out browser extension interference.
  • Console check: Inspect the browser console for JavaScript errors or script loading failures.
  • All templates covered: Ensure the script is in a global template so it loads on every page of your site.
  • A/B test active: Split tests must be set to "Active" status, with the script on all variant pages.
  • Form tracking: Third-party forms require the Humblytics.trackFormSubmission() hook.
  • Heatmap recording: Heatmaps must be set to "Recording" with the correct page URL and sufficient traffic.
  • Cache cleared: After making changes, clear your browser cache and test again.

Still Need Help?

If you've worked through this guide and your issue persists, our team is here to help.

  • Email support is available on all plans — reach out and we'll respond quickly.
  • Documentation: Browse the full knowledge base at docs.humblytics.com for detailed guides on every feature.
  • Video tutorials: Watch step-by-step walkthroughs at humblytics.com/resources/video-tutorials.
  • Free conversion audit: Not sure if your tracking is set up optimally? We offer a complimentary conversion audit to help you get the most out of Humblytics.
  • Slack support: Enterprise customers have access to a dedicated Slack channel for real-time assistance from our team.

Most installation issues come down to small configuration details — a misplaced script, a domain typo, or a page that hasn't been published yet. Once you've identified the culprit, the fix is usually a single change that takes less than a minute. You'll be tracking in no time.

Related Resources

Most Humblytics installation issues come down to a handful of common causes: script placement, domain mismatches, caching, or platform-specific quirks. The fixes are almost always straightforward once you know where to look.

If you haven't started yet, setup genuinely takes about five minutes — and you'll have privacy-first analytics, heatmaps, A/B testing, and conversion tracking all in one lightweight tool.

Start your free Humblytics trial — no credit card required.

Ready to optimize your conversions?

Start running A/B tests, analyzing funnels, and tracking revenue attribution—all without writing code.

Start Free TrialView Pricing