- What is danilopolani/filament-plausible-widget and what does it do?
- It is a Filament 3 dashboard widget that pulls Plausible Analytics metrics such as visitors, pageviews, bounce rate and visit duration into your Laravel admin panel. It queries the Plausible API through a service and renders a native-looking card, with configurable date ranges, multiple sites, caching and translations. It is best treated as a presentation-layer convenience for teams already using Laravel, Filament and Plausible.
- How do I install and register the Plausible widget in a Filament 3 panel?
- Install it with Composer, publish the config, provide your Plausible API key and site ID, then register the widget in your Filament panel provider. The integration is usually a short spike measured in hours, not weeks, but you should still test it in a non-production environment first. Add access control and secret handling before exposing it to real admin users.
- Does this package support Laravel and Filament version compatibility?
- The package is built for Filament 3, so pin it and verify its Composer constraints against your Laravel, PHP and Filament versions. Adoption is currently weak, with around 20 stars and zero dependents, so treat Filament major upgrades as explicit compatibility gates. Run a smoke test that renders the dashboard with the widget enabled before upgrading Filament.
- Does it work with self-hosted Plausible or only Plausible Cloud?
- The widget queries the Plausible Stats API, so confirm whether your target endpoint is Plausible Cloud or a self-hosted instance during your spike. Self-hosted compatibility depends on the API endpoint configuration and should be verified rather than assumed. If the endpoint is configurable, point it at your self-hosted Stats API and compare the output with Plausible directly.
- How are the Plausible API key and site ID configured, and are they kept secure?
- You supply a Plausible API key and site ID through the published config, and because the token is used server-side it must be stored as an environment secret rather than committed. The package is a small convenience layer and does not remove your responsibility for token scopes, rotation or access review. Restrict dashboard visibility through Filament panel authorization, since analytics visibility is also a privacy concern.
- Can I display multiple Plausible sites in one Filament dashboard?
- Multiple sites are supported via a Plausible API key, with site IDs configured in the package config. In a multi-tenant admin panel, verify that each panel or user only sees the sites they are authorized to view. The package does not provide tenant scoping by itself, so site selection and authorization must be handled in your Filament setup.
- Does the widget cache Plausible API requests and handle rate limits or API failures?
- The package publishes config for caching and polling intervals, so enable short-lived caching and request timeouts to avoid rate limits when several admins load the dashboard. You should explicitly test how the widget behaves when the Plausible API is unavailable and confirm that a failure does not break the whole admin dashboard. Do not rely on it for high-frequency or SLA-bound reporting.
- How do I change the date range and translate the widget labels?
- The date range is configurable for today, 7 days, 30 days or a custom range, and labels and headings are fully translatable. Publish the config and translation files, then adjust the range and locale strings per panel or application. Check that custom ranges and translations render correctly in a non-production environment first.
- Is there a test suite or release policy, and what happens when Filament v4 is released?
- The public context shows weak adoption, zero dependents and unclear test or CI coverage, so do not assume a formal release policy or Filament v4 support. Pin the package, add a smoke test for dashboard rendering with the Plausible API unavailable, and keep a fork or custom-widget contingency. Assign an internal owner for upgrade testing and document the fallback path.
- Is this package a good alternative to embedding Plausible or building a custom widget?
- It is a reasonable alternative if you already standardize on Laravel, Filament and Plausible and want a small internal reporting card without an iframe. If compatibility fails or you need SLA-bound reporting, build a thin custom Filament widget against the Plausible Stats API instead of forcing the package. It is not a strategic dependency for customer-facing, billing or compliance reporting.