Filament Gtm Laravel Package

Product Decisions This Supports

• Admin information architecture (IA) for analytics/settings surfaces: Plugin::make()->navigationGroup(string|Closure) lets product teams place the settings page inside an existing panel navigation group instead of a translated default group. This supports decisions about how analytics configuration is surfaced to admins, operators, and tenant owners without forking the package or writing custom Filament pages.
• Build vs. buy for admin configuration UI: The package continues to absorb low-differentiation admin plumbing (navigation registration, group labels, localization defaults). That strengthens the case for buying/using the package rather than building a bespoke settings screen, provided the rest of the analytics feature set fits.
• Multi-panel and white-label readiness: A Closure-based navigation group is useful when group names must be computed per panel, tenant, or role. This supports roadmap items for agency/multi-tenant deployments where each panel needs its own grouping logic.
• Localization and UX consistency: The default translated group is retained when the option is unused, so existing installs keep current behavior. Product can defer IA changes without a migration or forced UX shift.
• Release sequencing / dependency planning: The feature requires filament-analytics-core 3.1. This is a concrete upgrade dependency to schedule rather than an invisible transitive constraint.

When to Consider This Package

Consider adoption when:

• You are running a Filament panel and need an analytics/settings surface that admin users can configure without custom code.
• Your panel already has a defined navigation taxonomy and you need third-party or package-provided pages to fit into it rather than appearing in an isolated default group.
• You operate multiple panels or tenant-specific panels and want navigation grouping driven by a closure (panel context, tenant, role) rather than hard-coded strings.
• You want localized defaults out of the box, with the option to override only where your IA demands it.
• You can accept the filament-analytics-core 3.1 dependency floor; confirm the rest of your Filament/PHP version matrix is compatible before committing.

Look elsewhere or defer when:

• You are not on Filament, or you have no plans to expose analytics settings inside an admin panel.
• You need deeper customization of the settings page structure, not just its navigation placement — this release is a placement hook, not a page-composition API.
• You are pinned below filament-analytics-core 3.1 and cannot upgrade; the feature will be unavailable, though the default behavior remains intact.
• Your navigation groups are managed entirely by a custom panel provider that already re-groups pages; the added value may be marginal.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk capability release, not a strategic pivot. It lets the analytics settings page live inside your existing admin navigation instead of a separate default group, which makes the admin experience cleaner and more consistent. There are no breaking changes: teams that do nothing keep the current translated group. The only planning item is a dependency floor on filament-analytics-core 3.1.

For engineering: Plugin::make()->navigationGroup(string|Closure) adds an explicit, opt-in hook for navigation grouping, including closure-based resolution for multi-panel or tenant-aware setups. Default behavior is preserved, so this is a non-breaking, additive change. Verify the filament-analytics-core 3.1 requirement against your lockfile, and treat the closure form as the supported path for dynamic group names rather than reaching into panel configuration directly.

Recommendation: Adopt the release on the normal upgrade cadence. Use the string form where IA is static; use the closure form where group naming depends on panel or tenant context. Do not treat this as a reason to re-evaluate the build-vs-buy decision on its own — it is an incremental improvement that reduces one more reason to hand-roll admin settings pages.