Check out my comparison chart of pageviews vs. unique visitors.

integration_ian_2 · 2026-08-03T16:46:17Z

Hey everyone, I've been neck-deep in configuring Fathom's API to feed data into our internal dashboards, and it got me thinking about a fundamental metric distinction that's easy to gloss over. I built a custom comparison chart tracking **pageviews** against **unique visitors** over a 90-day period, and the divergence was more significant than I initially assumed for our content-heavy sites. For those automating reports or building triggers, understanding this gap is crucial. If you're using a webhook to send "traffic spike" alerts to a Slack channel based purely on pageviews, you might be missing the story about actual audience reach. A single visitor refreshing a live blog during an event can inflate pageviews, while unique visitors tell you about new audience acquisition. Here's a basic outline of the logic I used to pull and compare the data via the API, which you could adapt for Zapier or Make: ```javascript // Example structure for a custom connector script // Fetch pageviews data (aggregate) const pageviewsData = await fetchFathomData('aggregations', { entity: "pageview", entity_id: "your_site_id", aggregates: "pageviews", date_grouping: "day" }); // Fetch unique visitors data (requires 'visitors' aggregate) const visitorsData = await fetchFathomData('aggregations', { entity: "pageview", entity_id: "your_site_id", aggregates: "visitors", date_grouping: "day" }); // Compare and chart the two time-series datasets // A widening gap suggests high engagement per visitor. // A close correlation suggests broader, shallower traffic. ``` A few practical takeaways from my build: * **For marketing automation:** Use unique visitors as a primary trigger for "new audience" campaigns. Pageviews are better for engaging "returning user" flows. * **For CRM sync:** I pipe unique visitor counts (on key pages) into contact records if we can associate them via UTM parameters, giving sales context on account engagement depth. * **Pitfall to avoid:** Fathom's API endpoints for `aggregations` are powerful, but ensure you're requesting the correct aggregate (`pageviews` vs. `visitors`). I once built a connector that used the wrong one, making our reports misleading for weeks. The chart really highlighted how our tutorial pages have a high pageview-to-unique ratio (people return multiple times), whereas our news posts have a near 1:1 ratio (lots of one-time readers). This insight directly changed how we structure our automated content promotion workflows. Has anyone else built similar comparative analytics or run into surprises when distinguishing between these two core metrics in their automations? I'm always curious about different implementation approaches. api first

Page 3 / 3 Prev

Fathom Reviews

Last Post by helenb 2 months ago

31 Posts

30 Users

0 Reactions

138 Views

RSS

helenb

(@helenb)

Estimable Member

Joined: 3 months ago

Posts: 128

04/08/2026 3:42 pm

You're right about the two freshness SLAs causing problems. It makes me think about bookkeeping, where we need end-of-day snapshots but also real-time data for payment reconciliations. Is it better to have two separate API calls scheduled, or one call that serves both with a buffer?

ReplyQuote

Page 3 / 3 Prev

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed