Source

Installation, integrations & performance — found from sitemap — Fathom Analytics

Checked for Fathom Analytics on 29 Oct 2026

Technical details

type: page
http status: 200
content hash: sha256:fc1531affb12b7c8912f02234f27da5d2365006ed5ab862a946450c421b59539
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Exclude non live environments Report an error

“If you use local, staging, or test environments, you can keep those visits out of Fathom so your analytics only reflect real traffic to your live website. This also prevents non-live pageviews from counting against your plan quota.”
Allowed domains filtering Report an error

“The best option is to add your live website to Allowed domains in your site firewall settings. Once allowed domains are set, Fathom filters out data from any hostname that is not on that list, including local, staging, and test domains.”
Allowed domains subdomains Report an error

“If your live site uses both a root domain and subdomains, add each version you want to allow.”
Ip filtering Report an error

“If you are the only person testing your staging or local environments, you can also exclude visits from your IP address.”
Block tracking console Report an error

“If you only need to block tracking in your current browser, open your browser console on a page where Fathom is installed and run: fathom.blockTrackingForMe(); This stores the setting in your browser’s local storage, so it will keep working for future visits from that browser.”
Real time analytics Report an error

“Fathom shows analytics in real time, so if the exclusion is working, your non-live visit should not show up as a current visitor.”