Documentation

Installation checks and domain ownership guide

Verify installation polls for a received pageview for this Site ID. It does not fetch your website, inspect DNS, or prove ownership. A browser can submit a claimed URL; treat event receipt as a connectivity signal. Domain ownership must be verified separately through Domains. This workstream never sets verified_at when an event arrives.

No pageview yet

1. Check that the published page contains exactly one script with your real data-website-id and tracking origin. Save and publish site-builder changes and clear caches.
2. Visit the public hostname in a normal browser after required consent. Localhost, headless/webdriver and ml_ignore=true are ignored by default. Use ml_ignore=false to undo local opt-out.
3. In browser Network tools check /js/script.js and /api/event. A downloaded script alone is not successful ingestion. Wrong Site IDs and rejected domains can be silently dropped to keep customer pages working.
4. Check CSP script-src and connect-src, consent configuration and browser extensions. If an ad blocker blocks the analytics origin, use your platform's first-party proxy recipe. Keep both script and ingestion routes proxied to the same AnalyticFast host.
5. Confirm the workspace has a trial or active plan. Billing/ingestion entitlement controls may prevent recording until the lead integrates continued recording and quota locks.

Health lists registered domains and a sample of hostnames from the latest 1,000 sessions started in the past 30 days (up to 50 groups). Unknown hostnames trigger warnings; they are never automatically approved. Domains with no events remain unverified until the ownership process succeeds. Historical event receipt can remain detected even if a tracker was later removed; last-event time and stale warnings help you spot that.