- How do I install aerni/fathom in a Laravel project?
- Install it with Composer using the package's Composer name and then publish its config with php artisan vendor:publish. You add a single config or environment value for your shared Fathom site URL and refresh the control panel. There are no migrations, queue workers, scheduled tasks, or asset build steps involved. The whole install and review cycle realistically takes under an hour.
- Does aerni/fathom actually track page views or send data to Fathom?
- No. Despite the generic Laravel integration blurb, this package is a Statamic control-panel addon whose entire scope is surfacing a link to a shared Fathom dashboard. There is no analytics ingestion, no API client, and no persistence. If you need tracking, add Fathom's script snippet to your layout or use a dedicated Fathom API client instead.
- Which Statamic and Laravel versions does aerni/fathom support?
- Because it is a Statamic addon, the Laravel version follows transitively from Statamic's own constraint, so check the exact statamic/cms version in your composer.lock first. The addon must declare compatibility with Statamic majors such as v4 and v5, and the last tagged release was in May 2024. Confirm the constraints in the package's composer.json and whether CI tests them before adding it to an existing estate.
- How do I configure the Fathom share URL for the control panel link?
- Publish the addon config, then set the shared Fathom site URL or share token in your .env file and matching config key. After changing the value, run php artisan config:clear so the control panel picks up the new link. There is nothing else to configure, since the package only renders a hyperlink.
- Is aerni/fathom the same package as aerni/statamic-fathom?
- Yes. The Composer package name is aerni/fathom, while the source repository is aerni/statamic-fathom. Both refer to the same Statamic control-panel addon, so install docs and issue trackers may use either name interchangeably.
- Can I use aerni/fathom in a plain Laravel app without Statamic?
- No. The addon registers itself through Statamic's AddonServiceProvider and declares a control-panel nav or utility entry, so it provides no Laravel-generic surface to reuse. If your application is not Statamic-based, this package simply does not apply. A documented bookmark or a short custom nav item is the practical equivalent.
- Is the Fathom share token exposed to the browser by this addon?
- A Fathom share token is semi-public by design, because anyone holding the link can view the shared dashboard, so treat it accordingly regardless of how it is rendered. Whether the link is produced server-side or inside a Vue control-panel component, the value ends up in the client. Never put a private Fathom API key in this configuration; ask the maintainer which one is expected.
- Can I restrict which control panel users see the Fathom nav item?
- This is not documented clearly, so verify it before relying on it in a multi-user control panel. Statamic addon nav entries can be gated by permissions or roles, but whether this package does so is a question for the maintainer. If your CP is shared with clients or lower-privilege editors, test with each role explicitly.
- What are good alternatives to aerni/fathom for Fathom Analytics in Laravel?
- For tracking, use Fathom's official embed script in your Blade layout or a maintained Fathom API client if you need to query stats server-side. For the dashboard link itself, a 30-line custom Statamic nav item or a saved browser bookmark replaces this addon entirely. Weigh that against the overhead of carrying a third-party dependency for one hyperlink.
- Is aerni/fathom actively maintained and safe to use in production?
- Technical risk is low since the addon sits in the presentation layer and cannot break your request lifecycle. The real concern is abandonment: a single maintainer, roughly 3 stars, no dependents, and a last release in May 2024 means no early warning if Statamic majors change the control-panel surface. Pin the version, review it during Statamic upgrades, and have a composer remove rollback ready—it requires no cleanup.