Fathom

What Is Fathom Analytics?

Fathom Analytics is a privacy-first, cookieless web analytics platform built as a simpler, more ethical alternative to Google Analytics. Launched in 2018 by Jack Ellis and Paul Jarvis, Fathom answers a single question that most analytics suites bury under hundreds of reports: how is my website actually doing? It tracks the numbers that matter, such as visitors, page views, top pages, referrers, and conversions, on one fast-loading dashboard, and it does so without cookies, without collecting personal data, and without the consent banners that heavier trackers require.

The product's defining promise is compliance by design. Because Fathom does not use cookies or store personally identifiable information, its makers position it as compliant with privacy regulations such as GDPR, CCPA, ePrivacy, and PECR, which means most sites running Fathom do not need to show a cookie consent pop-up for analytics at all. That single characteristic, no consent banner required, is the reason many privacy-conscious businesses, agencies, and independent creators have migrated to it.

Fathom is a hosted SaaS analytics service, not a browser extension and not a plugin you install into a CMS. You add a small JavaScript snippet to your site, and Fathom collects aggregate, anonymized traffic data on its own infrastructure. The dashboard is intentionally minimal: rather than overwhelming you with the sprawling, multi-tabbed interface of an enterprise analytics suite, it surfaces the handful of metrics most site owners check daily and lets you filter and segment them quickly.

It helps to understand who Fathom is for. The platform deliberately targets founders, bloggers, small businesses, agencies, and privacy-minded organizations who want trustworthy traffic numbers without the legal and ethical baggage of surveillance-style analytics. It is not trying to be a product-analytics platform with funnels, cohorts, and session replay; it is trying to be the cleanest possible answer to basic web analytics questions. That focus shapes everything about the product, from its lightweight tracking script to its single-page dashboard, and it is exactly why Fathom appeals to people who found Google Analytics both overwhelming and uncomfortable from a privacy standpoint.

How Fathom Analytics Works

Fathom works by loading a tiny JavaScript snippet on each page of your website. When a visitor lands on a page, the script sends an anonymized event to Fathom's collection endpoint, recording the page view along with high-level, non-identifying context such as the referrer, the broad device type, and the country derived from the IP address at the moment of collection. Crucially, Fathom does not store the IP address or set any cookie, so there is no persistent identifier following a visitor from page to page or visit to visit.

Because there is no cookie and no cross-site identifier, Fathom counts unique visitors using a privacy-preserving method rather than by tagging each browser. The makers have publicly described building their own approach to de-duplicate visits without retaining personal data, so the dashboard can still show a sensible unique-visitor count while remaining anonymous. This is the central engineering trade-off of the privacy-first analytics category: you give up the precise, individual-level user tracking of cookie-based tools in exchange for aggregate numbers that are genuinely anonymous and require no consent.

The data flows into Fathom's hosted dashboard, where it is presented on a single screen. You see a traffic graph over your chosen time range, your most popular pages, where visitors came from (referrers and UTM campaigns), the countries and devices they used, and any events you have defined. Events in Fathom are lightweight conversion markers, such as a newsletter signup, a purchase, or a button click, that you trigger with a small snippet of code so you can tie traffic to outcomes without building complex funnels.

Fathom also offers practical features that matter for accuracy and reliability. It provides email and PDF reports, shareable public dashboards so you can make your stats transparent to clients or readers, and an uptime monitoring add-on. To dodge the ad blockers and tracker blockers that increasingly strip out third-party analytics, Fathom supports serving its script through a custom domain or a CNAME on your own domain, which makes collection more robust while still keeping the data anonymous. The script itself is deliberately small, often cited as a fraction of the size of a full Google Analytics tag, which means it has a negligible effect on page load and Core Web Vitals.

A useful way to picture the workflow is to follow a single site from setup to daily use. An owner signs up, adds one site to their Fathom account, and pastes the provided snippet into their site's template, optionally routing it through a custom domain to evade blockers. From that moment, every page view is recorded anonymously. The owner defines a couple of events for the actions that matter, such as a trial signup, then opens the dashboard each morning to see how yesterday's traffic and conversions looked. There are no cookie banners to maintain, no data-processing agreements to chase for basic analytics, and no sprawling configuration to keep current.

How to Tell if a Website Uses Fathom Analytics

Fathom leaves a small but recognizable footprint. Because StackOptic analyzes a URL from the server side, it inspects the same signals you can check by hand with browser tools, View Source, or a detection extension. As with all privacy-focused, lightweight analytics, the footprint is intentionally minimal, and self-hosting or custom-domain proxying can hide the most obvious tell, so it is worth combining several signals.

The Fathom script domain. The strongest standard signal is a script request to cdn.usefathom.com, typically loading a file such as script.js. Seeing a <script> tag whose source is cdn.usefathom.com is close to definitive proof of Fathom on a default setup.

The data-site attribute. Fathom's script tag usually carries a data-site attribute containing a short site identifier (a few uppercase letters). Spotting data-site alongside the Fathom script reinforces the detection.

The collection beacon. When a page loads, the script fires a small network request to a Fathom collection endpoint. In the DevTools Network tab you can watch for this beacon to the Fathom domain (or to a custom domain that proxies it) as the page loads.

Custom-domain CNAMEs. Because Fathom encourages routing the script through your own subdomain to avoid blockers, some sites load the script from a first-party domain rather than cdn.usefathom.com. In that case the obvious domain signal disappears, and the script's distinctive structure and the data-site attribute become the more reliable tells.

Here is how to check each signal yourself:

Method	What to do	What Fathom reveals
View Source	Right-click, "View Page Source" and search for "usefathom"	The cdn.usefathom.com script tag and data-site attribute
Browser DevTools	Open the Network tab and reload the page	Requests to cdn.usefathom.com or a custom-domain collection beacon
DevTools Console	Inspect loaded scripts and globals	The Fathom script and any fathom tracking object on the page
Wappalyzer	Run the extension on the live page	Identifies "Fathom" under analytics
BuiltWith	Look up the domain	Current and historical Fathom detection

A fast command-line check is curl -s https://example.com | grep -i "usefathom". If that returns a match, you are almost certainly looking at Fathom. For the broader methodology, see our guides on how to find out what analytics a website uses and how to find out what technology a website uses.

It is worth being honest about the limits of detection here. Privacy-first analytics tools are deliberately lightweight, and because Fathom supports custom-domain proxying specifically to beat ad blockers, a determined site can serve the script from its own domain and avoid the obvious usefathom.com request entirely. When that happens, no detector can be perfectly certain from the domain alone, and a careful analyst falls back on the structure of the script and the shape of the collection beacon rather than guessing. Server-side analysis helps because it fetches the unmodified HTML directly, without a browser's ad blocker stripping the tag before you ever see it, but it cannot manufacture a signal that a site has intentionally disguised. The practical takeaway is that a clear cdn.usefathom.com reference is strong evidence, its absence is not proof Fathom is missing, and combining signals always beats trusting one.

Key Features

• Cookieless, anonymous tracking. No cookies, no personal data, and no cross-site identifiers, which removes the need for an analytics consent banner on most sites.
• Single-screen dashboard. Visitors, page views, top pages, referrers, countries, and devices on one fast, uncluttered view.
• Lightweight script. A very small tracking snippet with negligible impact on page speed and Core Web Vitals.
• Event and conversion tracking. Simple, code-triggered events to connect traffic to outcomes like signups and purchases.
• Custom-domain support. Serve the script through your own domain to reduce ad-blocker loss while staying anonymous.
• Shareable dashboards and reports. Public dashboards plus email and PDF reports for clients and stakeholders.
• Uptime monitoring. An optional add-on to watch site availability alongside traffic.

Pros and Cons

Pros

• Strong privacy posture: cookieless and anonymous by design, marketed as compliant with GDPR, CCPA, and similar regulations.
• Usually eliminates the analytics cookie-consent banner, simplifying compliance and improving the visitor experience.
• Extremely lightweight script that barely affects load times.
• Clean, fast dashboard that answers everyday questions without a learning curve.

Cons

• A paid product with no indefinitely free tier, unlike Google Analytics.
• Intentionally limited depth: no funnels, cohorts, session replay, or granular individual-user analysis.
• Privacy-preserving counting trades some precision for anonymity, so figures differ from cookie-based tools.
• Less third-party integration tooling than the dominant analytics ecosystem.

Fathom Analytics vs Alternatives

Fathom sits firmly in the privacy-first, lightweight corner of the analytics market. The table below compares it with common alternatives.

Platform	Privacy model	Depth	Best for
Fathom	Cookieless, anonymous, no banner needed	Essential metrics	Privacy-minded founders, blogs, agencies
Plausible	Cookieless, anonymous, open source	Essential metrics	Privacy-minded teams wanting open source
Google Analytics 4	Cookie-based, consent usually required	Very deep, event-based	Free, full-featured marketing analytics
Matomo	Configurable; can be cookieless or self-hosted	Deep, GA-like	Teams wanting ownership and depth
Plausible/self-hosted	Cookieless, fully self-hosted	Essential metrics	Maximum data ownership

If you suspect a site uses a different privacy-focused tool, the closest comparison is Plausible, which shares Fathom's cookieless philosophy but is open source and self-hostable. For a heavier, configurable option, Matomo offers Google-Analytics-style depth with strong privacy controls.

Use Cases

Fathom is most at home for owners who want trustworthy traffic numbers without surveillance-style tracking or compliance overhead. Bloggers and independent creators use it to see which posts resonate and where readers come from, all on a dashboard they can check in seconds. Small businesses and SaaS founders use its events to tie marketing traffic to signups and sales while sidestepping cookie banners.

It also suits agencies that manage many client sites and want a simple, shareable analytics view per client, privacy-focused organizations in regulated or sensitive sectors that cannot justify cookie-based tracking, and any team that prioritizes fast page loads and a clean visitor experience over deep behavioral analysis. For competitive research, detecting Fathom on a prospect's site is itself a meaningful signal: it suggests an organization that takes privacy seriously and has deliberately rejected heavyweight tracking, which is useful context when profiling a company's values and technology choices.

Consider a few concrete scenarios. A solo founder launching a product might run Fathom from day one so they can watch traffic and trial signups without standing up a complex analytics stack or worrying about consent law. A content-driven media brand concerned about reader trust might switch from Google Analytics to Fathom specifically to remove the cookie banner and advertise its privacy stance. A consultancy might standardize on Fathom across client engagements, handing each client a shareable public dashboard so reporting is transparent and effortless. In each case the common thread is a desire for honest, lightweight measurement that respects visitors.

From a sales-intelligence perspective, identifying Fathom across a list of prospects helps segment the market by mindset. Companies that choose cookieless analytics tend to value privacy, simplicity, and performance, which can shape how a vendor positions a pitch. To understand how detecting a site's stack feeds qualification more broadly, see what is technographics and using tech-stack data to qualify leads.

Frequently Asked Questions

Does Fathom Analytics use cookies?

No. Fathom is built to be cookieless and does not store personally identifiable information or set persistent identifiers on visitors' browsers. That design is the foundation of its privacy claims and is why most sites running Fathom do not need a cookie-consent banner for analytics. It counts unique visitors using a privacy-preserving method rather than by tagging each browser with a cookie.

How can I tell if a website uses Fathom for free?

View the page source and search for usefathom, looking for a <script> tag pointing at cdn.usefathom.com and a data-site attribute. In DevTools, the Network tab will show a request to the Fathom domain as the page loads. Free tools like Wappalyzer and BuiltWith confirm it, and a single curl -s URL | grep usefathom works from any terminal. Note that sites proxying the script through a custom domain may not show the obvious usefathom.com request.

Is Fathom Analytics GDPR compliant?

Fathom markets itself as compliant with major privacy regulations including GDPR, CCPA, ePrivacy, and PECR, because it does not use cookies or collect personal data. This is the reason many sites can run it without a consent banner for analytics. As always, overall compliance depends on your full data-processing picture and any other trackers you run, so treat Fathom as a privacy-friendly building block rather than a guarantee covering your entire site.

Why do Fathom's numbers differ from Google Analytics?

Because Fathom is cookieless and anonymous, it counts visitors differently from cookie-based tools, and it does not silently drop traffic the way some consent-gated setups do. Differences are expected and do not mean either tool is wrong, they measure with different methods. Fathom also loses less data to consent banners but, like all third-party analytics, can be affected by ad blockers unless you serve its script from a custom domain.

Can Fathom track conversions and events?

Yes. Fathom supports lightweight events that you trigger with a small snippet of code to mark conversions such as signups, purchases, or key button clicks. These let you connect traffic and referrers to outcomes without building the elaborate funnels and cohorts found in product-analytics platforms. The approach keeps measurement simple while still answering whether your marketing is driving the results you care about.

Want to identify Fathom and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.