Fathom Analytics integration
Fathom Analytics is on the map, not in the product yet.
Pageviews, visits, and time on page from Fathom, attributed to published content by pathname.
How it works
Fathom Analytics connects with a Bearer API key. We call the aggregations endpoint grouped by pathname to pull pageviews, visits, and average duration for each published page, which is exactly the shape content measurement needs. The one operational quirk is Fathom's rate limit of 10 aggregation requests per minute, so the sync runs as a slow, patient batch rather than a burst.
In the loop, Fathom is the measure step for teams who chose the simplest serious analytics on the market. Each published page accumulates a traffic record, and pages that earn attention get flagged for internal links and follow-ups while pages that do not get queued for rework. The polling is slower than other analytics connections; the resulting picture is just as complete.
Best forTeams on Fathom Analytics who want published pages measured without adding a heavier analytics stack.
Setup, step by step
- In Fathom, create an API token under API settings in your account.
- Paste the token into SearchHandled's Fathom connector.
- Select the Fathom site that matches the site we publish to.
- Review the first aggregation pull, which arrives in batches over the following minutes.
Best practices
Expect the slow batch rhythm
Fathom allows 10 aggregation requests a minute, so a large content library syncs over minutes, not seconds. The schedule is built around this, and a sync in progress is normal, not stuck.
Keep pathnames stable
Attribution keys on pathname. If you restructure URLs, the history stays with the old path, so coordinate URL changes with redirects and expect the new path to build its own record.
Treat the token as a full credential
Fathom API tokens grant account-level API access. We store yours encrypted and never display it after setup, and you can revoke and reissue it in Fathom at any time.
Use duration as the tiebreaker
Two pages with similar pageviews can differ sharply in average time on page. We include duration in content evaluation because it separates pages that answer the query from pages that merely attract it.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
10 aggregation requests per minute
The aggregations endpoint is limited to 10 requests a minute, so pulling stats for many pages quickly is not possible and bursts get rejected.
How we handle itThe sync is built as a slow batch poller that works through pages inside the limit. Every page gets its numbers; a full refresh just takes minutes instead of seconds, which the schedule accounts for.
usefathom.com
Pathname grouping ties data to URLs
Aggregations grouped by pathname mean a renamed URL starts a fresh record, and the old path keeps the history, which can make a moved page look new.
How we handle itWe track URL changes made through the pipeline and join old and new paths in reporting where we know about the move, and we flag unexplained pathname breaks for review.
usefathom.com
Questions teams ask
- Why does a full Fathom sync take longer than other analytics?
Fathom limits aggregation queries to 10 per minute, so we poll in slow batches by design. The data is complete once the batch finishes, and scheduled refreshes keep it current thereafter.
- Can SearchHandled change our Fathom settings?
We only read aggregation reports. The connection makes no changes to your sites, settings, or tracking, and revoking the token in Fathom cuts access instantly.
- What metrics do you actually use?
Pageviews, visits, and average duration per pathname. That is enough to judge which published pages earn and hold attention, which is what feeds the opportunity engine.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Fathom Analytics matters moves it up the rollout.