Filament Plausible Widget Laravel Package

Product Decisions This Supports

• Feature decision: embedded analytics in admin — helps decide whether to surface Plausible KPIs (visitors, pageviews, top pages, referrers, countries) directly inside Filament for content, marketing, and ops teams, reducing context switching.
• Build vs. integrate — supports a cheap “integrate first” experiment: this package is MIT-licensed and narrow in scope, so it can be trialed against a custom Filament widget that would otherwise take roughly 1–3 dev days plus ongoing API maintenance.
• Roadmap for internal tooling — can serve as a low-effort phase 1 analytics panel. If usage validates, later replace with a BI tool or warehouse-backed dashboard; if not, remove it without strategic loss.
• Framework upgrade planning — v3.2.0 adds Laravel 12 support, which means the widget does not block a Laravel 12 migration and does not become a "remove before upgrade" chore. This lowers the cost of keeping it on the roadmap and removes a common reason these convenience tools get ripped out during upgrade cycles.
• Use-case validation — tests whether lightweight traffic visibility is a real workflow need or a nice-to-have. Success should be measured by repeat admin usage, not installation.
• Analytics stack ROI — reinforces Plausible as a privacy-friendly analytics choice by putting its metrics where teams already work, increasing the value of an existing Plausible subscription.
• Vendor/dependency policy — provides a concrete case for deciding how much the team will rely on small, single-maintainer packages for non-critical admin conveniences. The v3.2.0 release is a small positive signal: the maintainer is still merging outside contributions, not abandoning the package mid-upgrade.

When to Consider This Package

• You already run Filament as an admin panel and Plausible for analytics, with API access available.
• You are on, or planning to move to, Laravel 12 — v3.2.0 explicitly supports it, so the widget is not a blocker for a framework upgrade.
• You need a lightweight, read-only stats widget for non-analysts: daily traffic checks, top pages, referrers, and geography.
• You want a low-cost, low-lock-in experiment; MIT licensing means the code can be forked or replaced if needed.
• You can accept small-community risk: low star count, few dependents, and limited support. Treat it as convenience tooling, not critical infrastructure. The Laravel 12 release improves the maintenance outlook but does not change the package's category or support expectations.
• You can verify Filament/PHP version compatibility (the new release covers Laravel, not necessarily the Filament major you run) and test the widget in staging before exposing it to stakeholders.
• Look elsewhere if you need deep analytics, funnels, cohorts, multi-source dashboards, client-facing reporting, SLAs, enterprise support, or granular permissions. Native Plausible reporting or a BI tool is a better fit for executive reporting and historical analysis.
• Also look elsewhere if you are not on Filament, not using Plausible, or cannot accept a dependency with low adoption and limited maintainer redundancy.

How to Pitch It (Stakeholders)

• Executive summary: A small MIT-licensed Filament widget that puts Plausible traffic KPIs inside the admin dashboard the team already uses. It is a low-cost, low-risk trial, not a strategic platform bet. Treat it as a convenience layer, not a source of truth. The latest release (v3.2.0) adds Laravel 12 support, so adopting it does not create a future upgrade liability.
• For engineering: The integration is narrow. Pin the version (v3.2.0 or later for Laravel 12), store the Plausible API token in environment/secrets management, isolate it behind our own dashboard component where practical, add smoke tests, and monitor upstream releases. The v3.2.0 change is additive compatibility only — no breaking changes reported — so there is no migration work beyond the version bump. Fallback is a small custom widget if maintenance stalls.
• For product/ops: Faster daily checks on content and campaign performance without leaving Filament. Validate whether teams actually use it before investing in a broader analytics dashboard.
• Decision ask: Approve a time-boxed spike behind a feature flag, targeting the Laravel 12–compatible release. Success criteria: recurring admin usage, no API/security issues, and acceptable maintenance overhead; otherwise remove it.