Filament Mixpanel Laravel Package

Getting Started

1. Install/update the plugin and ensure filament-analytics-core is at least 3.1 if you intend to use the new navigation group override.
2. Register the plugin in your Filament panel provider as usual, e.g. ->plugin(Plugin::make()).
3. First use case: place the analytics settings page inside one of your panel’s existing navigation groups:

   use Vendor\Package\Plugin;
   
   public function panel(Panel $panel): Panel
   {
       return $panel
           ->plugin(
               Plugin::make()
                   ->navigationGroup('Analytics')
           );
   }
   

4. If you do nothing, the settings page keeps the package’s translated default navigation group.

Implementation Patterns

• Static group placement: chain navigationGroup('Reports') during plugin registration to keep analytics settings alongside related panel resources.
• Dynamic group placement: pass a Closure when the group should depend on panel/user context:

  Plugin::make()->navigationGroup(fn () => auth()->user()?->isAdmin() ? 'Admin' : 'Insights')
  

• Panel-level integration: configure the plugin in each Filament panel where the settings page should appear, since navigation groups are panel-specific.
• Upgrade path: bump filament-analytics-core to 3.1+ before relying on navigationGroup(); otherwise keep the default translated group.
• Keep defaults when consistency matters: omit navigationGroup() if you want the package’s translated group and less coupling to your panel’s navigation structure.

Gotchas and Tips

• navigationGroup() only affects the plugin’s settings page navigation placement; it does not rename or restructure the package’s underlying analytics features.
• The method requires filament-analytics-core 3.1. If you see the default translated group despite calling it, check the core package version first.
• Prefer a Closure only when the group genuinely needs runtime evaluation; static strings are simpler and easier to reason about in panel configuration.
• Keep group names aligned with your existing Filament navigation labels to avoid duplicate-looking groups caused by casing or translation differences.
• When upgrading, test panel navigation in each panel/provider where the plugin is registered, especially if multiple panels share the same auth/user context.