DocsTroubleshootingAll pages

Troubleshooting

Most problems are the tag missing from a page, a wrong key, or something blocking the request. The browser's console and network tab tell you which.

Nothing is arriving

  • View the page source of the live site and look for pagehum.js. If it’s missing, the tag isn’t in the layout that page uses, or the deploy didn’t go out.
  • Check data-site matches the key on the board exactly.
  • In the network tab, find requests to /api/ingest. A blocked request usually means a Content Security Policy without connect-src https://pagehum.com.
  • Privacy extensions and ad blockers can block analytics scripts. Counts from those visitors won’t arrive; nothing to fix on your side.
  • Press Send a test beacon on the board to confirm the board itself updates.

Console messages

Message starts withMeans
PageHum: data-site needs your site keyThe tag still has the placeholder or no key. Copy the snippet from your board.
PageHum: the demo key only counts on pagehum.comThe tag uses the demo key. Get your own free key.

Uptime checks the wrong address

The checked host is the first public host that sent a beacon. If that was a preview or staging domain, change it on the board next to the site’s name. The next check uses the new host.

Readings that look odd

  • Reachability says Waiting: no homepage check yet. It runs within five minutes of the first beacon from a public host.
  • Quiet: the homepage answers but nobody has visited recently. That is not an outage.
  • Visitors “partly estimated”: some days in the range predate unique counting, so a returning browser on those days counts once per day. It clears as those days age out.
  • Pageviews doubled: the tag is loaded twice, often once in a layout and once in a page or tag manager.
  • Client errors you can’t place: open the error on the board for its history, a note on common patterns, and an AI prompt to investigate it.

Still stuck

Copy the AI setup prompt from your board into your coding assistant and ask it to check the setup; it lists what to verify. Or start again from Installing the snippet.