Fathom Laravel Package

Product Decisions This Supports

This package remains a workflow convenience layer, not a platform capability. The v1.2.0 release does not change what it is — it changes who can use it. The decisions it supports:

• Analytics vendor selection (Fathom vs. GA4 vs. Plausible). Because the addon is essentially a control-panel shortcut to a Fathom shared dashboard, evaluating it forces the actual strategic question: do we want cookieless, GDPR-friendly, EU-hosted analytics that removes the consent-banner dependency? If the answer is Fathom, this addon is the cheapest possible "editorial team can find the numbers" layer. If the answer is Plausible or GA4, the package is irrelevant and should be skipped without further diligence.
• Build vs. buy for CP integrations. The entire feature is a navigation entry (plus optional dashboard widget) linking to an external analytics URL. The build cost is a few hours of a Laravel dev; the buy cost is a Composer dependency from a single maintainer with 3 stars and 0 dependents. This is a textbook case where "build" is the lower-risk path unless the team is already comfortable with unmaintained micro-addons. v1.2.0 is a mild point in the package's favour here — the maintainer is still shipping — but the build alternative is still 30–50 lines.
• Editorial workflow prioritization. For content and marketing teams working in the Statamic CP, reducing analytics lookup from "open new tab, find bookmark, remember the shared URL" to "one click in the sidebar" is a genuine friction reduction. That is a small but measurable win in weekly reporting cadence — the kind of thing worth 30 minutes of setup, not worth a procurement cycle.
• Dashboard consolidation / "single pane of glass" roadmap bets. If the roadmap includes bringing key metrics into the CP, a link-out addon is a stopgap, not a destination. Adopting it is a signal that analytics-in-CP is a later concern, not a now concern.
• Platform upgrade sequencing (new). v1.2.0 adds Statamic 5 support and drops Statamic 4. That makes the package a small input into a "when do we move off Statamic 4" conversation: if you are on 4, this addon is now feature-frozen at the last 4-compatible release; if you are moving to 5, the addon is no longer a blocker. It should not drive the upgrade decision — it is a sidebar link — but it removes one line from the upgrade checklist.
• Not a decision this supports: anything about data residency, consent management, telemetry accuracy, or vendor lock-in at the site-tracking layer. The addon touches none of that — it only touches navigation.

Net: treat this as a configuration choice, not an architecture decision. The real decision is the analytics vendor; this package is a checkbox downstream of that. The release notes only narrow the compatibility window.

When to Consider This Package

Adopt when all of the following hold:

• You have already standardized on Fathom Analytics and have a shared dashboard URL for the team.
• Your editors/marketers live in the Statamic control panel daily and repeatedly ask "where do I see the traffic numbers?"
• You are on Statamic 5. v1.2.0 is the first release supporting it; Statamic 4 is no longer supported as of v1.2.0, so a Statamic 4 site must pin the previous 1.x line and accept that it is now frozen (no bug fixes, no security patches going forward).
• You accept a single-maintainer, low-adoption dependency (3 stars, 0 dependents) and are comfortable that a breakage costs you a menu link, not data, content, or uptime. The new release is evidence the maintainer is still active — a positive signal, but not a substitute for community pressure-testing that does not exist here.
• You want zero code and are fine with the addon's defaults rather than a bespoke integration.

Look elsewhere — or just build it — when:

• You are not on Fathom. There is no cross-vendor value here. Plausible, Umami, Matomo, and GA4 users get nothing.
• You are still on Statamic 4. v1.2.0 drops support, so the upgrade path is closed unless you upgrade Statamic first. Do not pin a frozen addon as a long-term strategy for a one-link feature; build the nav item instead and own it.
• You need metrics inside the CP (charts, KPIs, per-entry pageviews). This addon links out; it does not embed data. If the requirement is "see pageviews on the entry edit screen," you need a custom widget or a different integration, and this package will disappoint.
• Your dependency policy is strict. Zero dependents and 3 stars means no community pressure-testing and no ecosystem safety net. Teams with an approved-vendor list or an SBOM review will likely reject it — and reasonably so, given the build alternative is trivial.
• You need SSO/role-scoped analytics access. A shared-link addon cannot enforce per-role visibility into analytics; that is a Fathom account setting, not something this package solves.
• You are on a Statamic version outside the supported range. As of v1.2.0 the supported range is Statamic 5 only — verify the exact constraint from composer.json rather than the marketing copy before assuming.

The honest read is unchanged: the "consider" bar is low because the downside is low, but the "must-have" bar is also low because the feature is cosmetic. v1.2.0 moves it from "possibly abandoned" to "maintained, but narrow" — which is enough to keep it on the list for Statamic 5 / Fathom shops and enough to take it off the list for everyone else.

How to Pitch It (Stakeholders)

For executives (30 seconds): Our editorial team uses Fathom for privacy-first analytics — no cookie banner, GDPR-simple, which reduces legal overhead on every property we ship. This addon puts a one-click link to our Fathom dashboard inside the CMS, so the content team stops context-switching to find traffic numbers. Cost: a free, MIT-licensed Composer package and about 15 minutes of setup. Risk: minimal — if it breaks, we lose a sidebar link, not data or site availability. It does not change how we collect analytics; that decision is separate and already made. The maintainer shipped a v1.2.0 that adds Statamic 5 support, so it is actively kept alive.

For engineering: It is a thin Statamic addon — a nav item plus optional dashboard widget pointing at a configured Fathom shared URL. No tracking code, no data pipeline, no schema changes. v1.2.0 is a compatibility-only release: adds Statamic 5, drops Statamic 4. Consequences: on Statamic 5 this is a drop-in; on Statamic 4 we cannot upgrade past the previous 1.x tag and should treat that line as end-of-life. It is still a single-maintainer package (3 stars, no dependents), so the realistic objection remains maintenance hygiene rather than technical risk — and the release cadence helps a little there. Acknowledged trade-off: this is roughly 30–50 lines of equivalent custom code if we would rather own it. Recommendation: on Statamic 5 + Fathom, install it and move on; on Statamic 4, or under a strict dependency policy, spend the half-day and build the nav item ourselves so we own the maintenance and aren't tied to someone else's version matrix.

For the product narrative: This is a small, cheap proof point that we are tightening the content team's daily loop — fewer tabs, fewer bookmarks, analytics where the work happens. It is not a roadmap item and should not be sold as one. The new release does not add features; it keeps the addon current with our CMS, which is exactly the correct amount of ambition for a link in the sidebar. It is housekeeping that makes the analytics investment we already made more visible to the people who use it.