Filament Hotjar Laravel Package

Product Decisions This Supports

• Panel IA and navigation design: Plugin::make()->navigationGroup(string|Closure) lets product/design decide where the analytics settings page lives in the admin panel — grouped with other settings, or surfaced alongside reporting modules. This is a small but real UX lever for information architecture in Filament-based admin surfaces.
• Multi-tenant / multi-panel packaging: Accepting a Closure means the navigation group can be resolved per-tenant or per-panel at runtime, which supports white-label and reseller scenarios where different customers expect different admin taxonomies.
• Build vs. buy on admin tooling: The package is a Filament plugin that extends filament-analytics-core. Choosing it means buying into the Filament plugin ecosystem rather than hand-rolling settings screens; this release reduces the customization work needed to make it feel native to your panel.
• Localization strategy: Default behavior is unchanged — the translated group is preserved unless overridden. That keeps i18n coverage intact by default and makes override an explicit, opt-in product decision rather than a side effect.
• Roadmap signal: Upstream dependency on filament-analytics-core 3.1 indicates the vendor is actively aligning the plugin with the core release train. Budget for coordinated upgrades across the two packages rather than treating them as independent.

When to Consider This Package

Adopt when:

• You run a Filament panel and need an analytics/settings surface without building one from scratch.
• Your panel already has (or will have) custom navigation groups, and leaving the analytics settings page in a default translated group would look bolted-on.
• You need per-tenant or per-panel navigation differences — the Closure form is the deciding factor here.
• You are already on, or can move to, filament-analytics-core 3.1+; this feature does not exist below that.

Look elsewhere or defer when:

• You are pinned to an older filament-analytics-core — the method is unavailable and there is no described fallback.
• You are not on Filament, or you have no appetite for a plugin dependency chain (plugin → core → Filament major versions).
• Your navigation taxonomy is fixed and the default translated group is already acceptable; this release delivers no value to you.
• You need guarantees this release does not make. The note describes only navigation grouping — it says nothing about analytics correctness, data retention, permissions, or performance. Do not read a minor version bump as validation of those.

How to Pitch It (Stakeholders)

To executives: A minor, non-breaking update to our admin analytics plugin. It lets us place the analytics settings page into our own navigation groups instead of a package-defined default, which makes the admin experience consistent for customers — particularly where different clients see differently organized panels. Low risk, low effort, no migration required; the default behavior is unchanged if we do nothing. The one dependency: it requires the companion core package at 3.1 or above, so it should ride along with that upgrade rather than trigger its own project.

To engineering: Plugin::make()->navigationGroup(string|Closure) is now available, with the pre-existing translated group retained as the fallback. The Closure variant is the interesting part — it should let us resolve the group dynamically per panel/tenant. Confirm our filament-analytics-core constraint permits 3.1 before scheduling, and verify whether the closure is evaluated per-request or cached, since that affects multi-tenant panels. Add a test asserting the default translated group still applies when we don't override, so we notice if a future release changes that default.