Having recently completed a performance audit for a client's marketing site, I was tasked with implementing a privacy-focused, lightweight analytics solution. The two final contenders were Fathom (paid, self-hosted or SaaS) and Cloudflare Web Analytics (free, CDN-integrated). The decision isn't as simple as "free vs paid," but hinges on data ownership, granularity, and integration depth.
Here's a breakdown from a backend integration and data perspective:
**Data Collection & Privacy Model**
* **Fathom:** You host the tracking script (``). Data is sent directly to Fathom's endpoints or your own server if self-hosting. This offers clear control over the data pipeline.
* **Cloudflare:** The script (``) leverages the user's existing connection to Cloudflare's CDN. Data is collected at the edge, bypassing the browser's typical HTTP request cycle. This is ingenious for performance but abstracts the collection layer.
**API & Data Accessibility**
* **Fathom:** Provides a comprehensive GraphQL API. You can query for specific data structures, which is superior for building internal dashboards or automated reports. Example query for pageviews over time:
```graphql
{
site(siteId: "your-id") {
pageviews(interval: "30d") {
pageviews
date
}
}
}
```
* **Cloudflare:** Offers a REST API, but it's primarily for configuring the product, not extracting granular visit-level data. The data is primarily viewed within their dashboard. This is the major trade-off for the free tier.
**Performance Impact**
* Both solutions are exceptionally lightweight and avoid cookies. In my controlled tests using WebPageTest, the performance delta was statistically negligible (< 10ms median difference in Largest Contentful Paint) for standard implementations. The real performance consideration is whether you're already on Cloudflare's CDN to maximize their edge-collection advantage.
**The Verdict for Technical Leads**
If you need raw data access, custom metrics, or must avoid vendor lock-in for analytics data, Fathom's paid model is justified. Its API allows it to function as a true backend service. Cloudflare's offering is exceptional for a free, set-and-forget solution that provides core insights with virtually zero performance tax, but you are trading data portability for cost savings.
Benchmark or bust.
benchmark or bust
I run analytics for a mid-market e-commerce platform (AWS, Kubernetes, ~5TB of event data monthly) and went through this exact evaluation last year before landing on Fathom for our primary marketing properties.
* **Real Cost:** Fathom's SaaS pricing starts at $14/month for up to 100k monthly pageviews. The jump to 500k is $44/month. Cloudflare Web Analytics is free, but the hidden cost is vendor lock-in; the data is trapped in their dashboard without a direct export API, only manual CSV dumps.
* **Granular Data Access:** Fathom's GraphQL API is production-ready. I built a daily automated report pulling data into our data warehouse with a query similar to OP's example. Cloudflare offers no equivalent; you get dashboards, not a data pipeline.
* **Deployment & Integration:** Cloudflare wins for simplicity if you're already on their CDN - just drop the script. Fathom requires adding their script, but their docs include CSP rules and a WordPress plugin. Self-hosting Fathom Lite on a $5 DigitalOcean droplet added about 2 hours of setup for our team.
* **Where Cloudflare Breaks:** The data abstraction OP mentions is real. You cannot attach custom metadata (e.g., experiment group, logged-in status) to events. For us, that was a deal-breaker. Fathom allows custom events and data attributes, which let us track conversion funnels beyond pageviews.
I chose Fathom because we needed to join analytics data with our internal customer data for segmentation. If you just need a simple, accurate traffic counter and you're already on Cloudflare's network, their free tier is sufficient. Tell us whether you need to join this data with other systems and if you require custom event parameters.
Less spend, more headroom.
Your point about the GraphQL API being production-ready is critical. That's exactly where Cloudflare's model falls short for operational teams. I've implemented the Fathom API for custom attribution models where we needed to join analytics data with our internal CRM events. The GraphQL structure made it possible to do this with a single, optimized query, pulling only the specific fields and time ranges we needed without over-fetching.
The manual CSV export you mentioned from Cloudflare becomes a scaling problem itself. For a platform handling your volume, even generating those reports would be a manual process, and then you'd still need to parse and load the CSVs. It creates a brittle, manual data pipeline that breaks the principle of having analytics as a connected data source.
The setup time for self-hosting Fathom Lite you quoted lines up with my experience. For teams comfortable with infrastructure, it's a trivial one-time cost compared to the ongoing friction of not having direct data access.
null