If you want website analytics that don’t put a cookie on your visitors, don’t require a consent banner, and don’t sell anyone’s data to fund the free tier, Fathom Analytics is one of the cleanest options available. It’s a hosted, privacy-first analytics tool built around a simple promise: useful numbers, zero personal tracking.
Setting it up takes about ten minutes, and most of that is deciding where to paste one line of code. This guide covers the full Fathom Analytics setup — adding the site, installing the script, verifying data, setting up goals and event tracking, and the privacy details that make Fathom genuinely cookie-free rather than just marketing-cookie-free.
Short answer: To set up Fathom Analytics, create an account, add your site to the dashboard, then paste the generated <script> tag (with defer) into your site’s <head>. That’s the entire install — no cookies, no consent banner needed, no tag manager required.
What Fathom Analytics Is (and Isn’t)
Fathom Analytics is a lightweight, privacy-focused analytics platform that gives you the metrics most site owners actually use — page views, unique visitors, referrers, top pages, and conversions — without building profiles of individuals. It’s designed as a simpler, ethical alternative to heavyweight tracking suites.
What makes it different:
- No cookies. Fathom counts visits without storing identifiers on the device, so there’s typically no banner to slow your pages down.
- No personal data harvesting. Its business model is paid subscriptions, not ad revenue — so its financial incentives don’t push toward collecting more about your visitors.
- One dashboard, fast to read. Everything important sits on a single screen. No hunting through nested reports, no setting up views before you can see basic traffic.
- A tiny script. The tracking snippet is small enough that its impact on page load is negligible — far smaller than a consent management platform plus a consent banner combined.
What it isn’t: a forensic, per-person journey tracker. If your work depends on following named individuals across months, Fathom intentionally won’t do that. For most sites — blogs, content sites, small SaaS, local businesses — the data you give up is the data you shouldn’t have been collecting in the first place.
Before You Start
Three things, none of them complicated:
- A Fathom account. It’s a paid tool with a trial period — you can evaluate before committing.
- The ability to edit your site’s HTML
<head>— directly, through your theme, or via a plugin. - Five minutes to verify data is flowing once installed.
No tag manager to configure. No data layer to plan. No DPA to file before you can start. That simplicity is part of what you’re paying for.
Step 1: Add Your Site and Get the Snippet
Inside your Fathom dashboard, add a new site and give it a name — your domain works. Fathom generates a unique site ID and a script tag that looks like this:
<script src="https://cdn.usefathom.com/script.js"
data-site="YOUR_SITE_ID"
defer></script>The defer attribute tells the browser to fetch the script without blocking page render. Keep it. Removing it to “make sure it loads” is the one change that will actually hurt your performance scores.
Step 2: Install the Script
Pick whichever method fits your stack. There’s no wrong answer here — the snippet is self-contained.
WordPress
The cleanest route: a lightweight “header scripts” plugin that lets you paste code into the <head> without touching theme files. Paste the Fathom snippet, save, done. If you prefer editing the theme directly, add it to header.php just before the closing </head> — but do it in a child theme, not the parent. A theme update will wipe anything in the parent’s files. If you’re already on a setup like this one, the same rule applies to every analytics script you install.
Static sites and frameworks
For static HTML, Astro, Next.js, Hugo, or similar: drop the script tag into your base layout or template head. Because it’s a single self-contained tag with no dependencies, there’s nothing else to wire up. The defer attribute handles async loading without any extra configuration.
Tag manager (optional)
You can deploy Fathom through a tag manager, but for a privacy-first stack it usually adds complexity without benefit. Fewer moving parts means fewer things to audit, fewer surfaces for a misconfiguration to break your data. Direct install is simpler and easier to verify.
Step 3: Verify Data Is Flowing
Open your site in a normal browser tab, then check Fathom’s real-time view. Your own visit should appear within seconds. If nothing shows up:
- Confirm the
data-siteID in your script matches the one in your dashboard exactly — copy-paste errors here are the most common cause of missing data. - Make sure the script is in the
<head>and not accidentally inside a comment or a caching exclusion. - Disable any ad blocker for the test, then re-enable it. Fathom is privacy-friendly, but some blockers still match analytics scripts by URL pattern regardless of what they do.
- Clear your page cache. If you’re on a caching plugin or CDN, you may be serving a pre-cached version of your
<head>that doesn’t include the new snippet yet.
To sidestep ad blockers entirely, Fathom supports serving the tracking script from your own domain — a technique sometimes called a custom domain or proxy setup. It’s optional, but it improves data completeness without compromising privacy.
Step 4: Set Up Goals and Events
Page views tell you what people read. Goals tell you whether they did what you wanted.
In Fathom, create a goal in the dashboard — something like “Newsletter signup” or “Contact form sent” — then trigger it in your code when the action happens:
// Fire when the conversion happens
fathom.trackEvent('Newsletter signup');The result is an aggregate count tied to the goal — not to a person. You learn how many sign-ups happened and where visitors came from, without building a profile of anyone. It’s the same outcome-focused thinking behind measuring SEO without user-level tracking — you get signal on what’s working without trading your visitors’ privacy to get it.
One practical note: if you’re migrating from Google Analytics, you’re used to goals requiring a destination URL or a funnel configuration. Fathom’s approach is simpler — fire an event in code when the conversion happens, and the dashboard records it. Less setup, but it does require a code change anywhere you want to track an action. If that’s a blocker, the migration guide covers how to think through the transition.
Fathom vs Other Privacy Tools
Fathom sits in a crowded, healthy field. Here’s how the main options compare:
| Tool | Hosting | Cookieless | Best fit |
|---|---|---|---|
| Fathom | Hosted (managed) | Yes | Owners who want zero maintenance |
| Plausible | Hosted or self-hosted | Yes | Open-source flexibility |
| Umami | Self-hosted | Yes | Full data ownership on your own server |
| Matomo | Hosted or self-hosted | Configurable | Deeper, GA-style reporting |
The key split is managed vs self-hosted. Fathom and the hosted version of Plausible mean you never touch a server — the trade-off is a monthly fee and your data living on someone else’s infrastructure. Umami on your own VPS gives you complete data ownership and no ongoing subscription cost, at the price of maintaining the server yourself. If you want to go that route, the Umami self-hosted guide walks through the full setup. For most people, managed is the right call — especially when the goal is simplicity.
Privacy and Compliance Notes
Fathom’s cookieless, no-personal-data architecture simplifies your compliance posture — but “simplifies” isn’t the same as “eliminates.” A few practical points:
- Consent banners: Tools that don’t store personal data typically don’t trigger the consent obligations that apply to tracking cookies under GDPR and PECR. Fathom publishes its legal reasoning on this. That said, obligations vary by jurisdiction — confirm against your own requirements before removing a banner.
- Privacy policy: List your analytics provider and describe what’s collected — even if the answer is “aggregated, non-personal data.” Transparency is both a legal good practice and a trust signal worth displaying.
- Data residency: If you operate under EU rules, confirm where Fathom processes data and whether EU-based handling is offered.
For a deeper look at how consent requirements interact with analytics tools, the GDPR consent banner guide covers what triggers the obligation and what doesn’t.
Frequently Asked Questions
Does Fathom Analytics use cookies?
No. Fathom counts visits without storing cookies or other persistent identifiers on the visitor’s device. That’s what lets most sites skip the analytics consent banner — there’s no cookie being set that requires disclosure.
Will Fathom slow down my site?
The tracking script is small and loads with defer, so it doesn’t block page render. The practical impact on Core Web Vitals is negligible. For comparison, a typical consent management platform plus its banner adds far more to load time than Fathom’s entire script.
Can I track conversions in Fathom?
Yes. Define goals in the dashboard and fire them with a trackEvent call when a conversion happens. Results are aggregated by goal — never tied to an individual visitor.
Is Fathom free?
No. Fathom is a paid, subscription-based tool. It offers a trial period so you can evaluate it before committing. The paid model is what funds the service — and keeps the business model away from monetizing visitor data. Check the current pricing page before signing up.
Does Fathom work without a tag manager?
Yes — and in most cases, that’s the recommended approach. One script tag in your <head> is all it takes. A tag manager adds overhead without adding capability for a tool this simple.
You’re Ready to Track Ethically
Fathom’s setup is genuinely as simple as it’s described. Add the site in the dashboard, paste one deferred script into your <head>, verify in the real-time view, then define a goal or two for the conversions that matter. That’s it. You get clean, fast, cookie-free analytics without the consent mechanics, the data layer planning, or the monthly renegotiation of what Google Analytics just changed.
If you’re weighing Fathom against the other privacy-first options before committing, the Matomo vs Plausible breakdown covers the open-source side of the field in detail. Pick the tool that fits how you actually work, not just how you hope you’ll work.
