Troubleshooting

No pageviews arrive

Check, in order:

1. The hostname. UsherStats accepts reports only from pages on the site's hostnames. If your site answers on both example.com and www.example.com, add both in the site's settings.
2. The key. The snippet's data-site must be the site's public key exactly: pk_ and 26 letters and digits. A malformed key makes the script do nothing at all.
3. Your browser. Browsers that send Global Privacy Control (Brave and DuckDuckGo by default, and some extensions) are not recorded. Test with another.
4. Leave the page. A page reports when it is hidden or closed, not when it loads. Switch tabs or close it, then look.
5. Content Security Policy. If your site sends one, allow https://collect.usherstats.com in script-src and connect-src, or use a first-party path.
6. Blockers. Some blocking extensions drop third-party analytics. A first-party path avoids that.

My visits show under Crawlers or Internal, not People

That is usually right:

• Internal: your browser is marked as internal, or you are on a network listed in the site's internal networks.
• Crawlers: you are browsing from a hosting network (many VPNs run on cloud servers), your computer reports its time zone as UTC, or the session went past twenty pages. See Concepts.

People is empty behind my own proxy

A first-party path on your own server must send your server secret and the visitor's IP address, country and network (AS number and name). Without them UsherStats sees your server, a hosting network, and counts every reader as automated. See A first-party path, or use the snippet directly.

A single-page app shows one pageview per visit

The snippet reports one pageview per full page load. Navigations inside a single-page app are not reported as separate pageviews yet.

The Crawlers view is empty

Crawlers do not run scripts, so the snippet cannot see them. Install the Worker SDK or use proxy mode. If you have and it is still empty, check that the Worker's USHERSTATS_SECRET is the site's current server secret. On Free, server-request logging pauses past 150% of the month's allowance; see Billing and plans.

Real people are being challenged

Switch the site to log mode, read the Bot protection view to see which rule or signal is responsible, and adjust your rules. See Bot protection.

Search data is missing

• The service account (yours or ours) must be a user of the Search Console property, with at least Restricted access.
• The property must match your site: a domain property covers every hostname; a URL-prefix property only its prefix.
• Search engines publish data a few days late, so the most recent days fill in later.

See Search Console and Bing setup.

Still stuck

Write to support@usherstats.com with your site's name and what you expected to see.