Filament Metrics Posthog Laravel Package

Product Decisions This Supports

• Admin UX / information architecture: Plugin::make()->navigationGroup(...) lets you place the analytics settings page inside an existing panel navigation group (e.g. "Insights", "Reporting", "Settings") instead of the package's default translated group. This is a small but real lever for keeping admin navigation coherent as the number of Filament plugins grows.
• Multi-panel product surfaces: Teams running several panels (admin, tenant, internal ops) can now position the same settings page differently per panel, so IA can match each audience rather than inheriting a package default.
• Build vs. buy for analytics settings UI: Confirms the package is actively maintained and configurable rather than a one-off scaffold — a point in favour of buying/adopting instead of hand-rolling a settings page and analytics config form.
• Roadmap signal, not a roadmap item: Supports the decision to keep the dependency current (requires filament-analytics-core 3.1) but does not by itself unlock new user-facing features.
• Branding/localisation decisions: Accepts a string|Closure, so group names can be computed per-tenant/per-locale at runtime — useful if you've committed to translated navigation or per-customer admin theming.

When to Consider This Package

• You already use Filament panels and want an analytics settings surface without building config forms and navigation plumbing yourself.
• You care about admin navigation consistency and want the analytics page to sit alongside your own grouped resources/pages rather than in a package-defined group.
• You're comfortable keeping filament-analytics-core pinned at 3.1+; on older core versions this release's only new capability is a no-op (the translated default group is retained).
• Look elsewhere or defer if:
  • You are not on Filament, or your admin surface is custom-built.
  • Your panel has a single flat navigation and no grouping — the feature adds nothing.
  • You need a reason to upgrade beyond cosmetics; this is a convenience/IA change, not a fix or capability expansion. There is no deprecation or breaking change here, so upgrade urgency is low.
  • You pin dependencies conservatively and don't want to take a paired core upgrade for a navigation nicety.

How to Pitch It (Stakeholders)

For executives: A minor, low-risk release. It lets our admin navigation stay tidy by filing the analytics settings page under our own menu groups instead of a package-imposed one. No breaking changes, no migration work, no new cost — purely a polish item that improves how the product feels to internal and customer-facing admins.

For engineering: Version 3.1.0 adds Plugin::make()->navigationGroup(string|Closure) to the Filament plugin, gated on filament-analytics-core 3.1. It is opt-in and backwards compatible: without it, behaviour is unchanged (translated default group). Because it accepts a Closure, group names can be resolved dynamically for multi-tenant or localised panels. Recommended action: bump core to 3.1 alongside the plugin, adopt the call in panels where navigation grouping matters, and skip it where it doesn't. No deprecations to track.