Skip to main content

Verify installation

PureStats verification is split into separate checks so you can see exactly where the setup fails.

Verification states​

StateMeaning
Script foundThe configured page contains a PureStats script tag.
Script loadsThe browser can load pf.js from PureStats.
First hit receivedPureStats accepted a pageview for the site or one of its aliases.

All three states must pass before the site should be considered fully installed.

How to run a manual check​

  1. Open your site in a normal browser.
  2. Disable browser extensions that block analytics scripts.
  3. Confirm the script exists in page source.
  4. Open the browser Network panel and look for pf.js.
  5. Reload the page and check whether /api/event returns a successful response.
  6. Return to PureStats and refresh Site Health.

Common failure reasons​

  • data-domain does not match the canonical site or alias.
  • The website has a Content Security Policy that blocks https://purestats.io.
  • The current path is excluded in Site Settings.
  • Consent mode is enabled and no consent was granted.
  • A bot/spam filter suppresses the visit.
  • The site exceeded a hard quota.

Verification and aliases​

If tracking is installed on www.example.com but the PureStats site is example.com, add www.example.com as an alias. Without an alias, PureStats rejects the event because the hostname is not allowed for that site.

info

Verification checks are intentionally stricter than dashboard filters. A hit must first be accepted by the tracking API before dashboard filters can include or exclude it.