- What is filament-pixel used for?
- filament-pixel is a Filament plugin that adds an admin settings page for Meta (Facebook) Pixel configuration in a Laravel application. It stores pixel IDs and related settings through spatie/laravel-settings so you can manage tracking scripts from the panel instead of hardcoding snippets in Blade views. It is aimed at teams already using Filament who want a native settings UI for analytics and conversion tracking.
- How do I install filament-pixel in a Laravel Filament app?
- Install it with Composer using composer require jeffersongoncalves/filament-pixel, then register the plugin in your Filament panel provider. The package follows standard Filament plugin registration, so it fits into the existing PanelProvider::plugin() flow. Check the README for any publish or migrate steps tied to spatie/laravel-settings.
- Which Laravel and Filament versions does filament-pixel support?
- The package is built for Laravel applications using Filament panels, and the evaluation notes target Filament v3. Newer features such as navigationGroup() require filament-analytics-core 3.1 or later. Always confirm the exact Laravel, Filament, and PHP constraints in the package's composer.json before upgrading, because Filament navigation APIs differ between major versions.
- Do I need to publish migrations for spatie/laravel-settings?
- Because filament-pixel uses spatie/laravel-settings, your application needs the settings storage configured, which usually means publishing and running the laravel-settings migration if you have not already done so. Follow the package README for the exact publish tags and migration commands. If your project already uses spatie/laravel-settings, you likely only need to confirm the settings table and cache configuration.
- How do I configure my Meta Pixel ID and tracking script from the admin panel?
- Once the plugin is registered, open the Pixel settings page in your Filament admin panel and enter your Meta Pixel ID and any script or event configuration the form exposes. The values are saved through spatie/laravel-settings, so they are available to your frontend injection logic without editing code. Clear any settings cache after changes if your deployment caches settings.
- How do I move the Pixel settings page into a custom Filament navigation group?
- Call Plugin::make()->navigationGroup('Analytics') in your panel provider, where the string can be replaced with a Closure for per-panel or localized labels. This places the Pixel settings page inside an existing navigation group instead of the package's default translated group. The method requires filament-analytics-core 3.1 or later, and leaving it out keeps the default behavior unchanged.
- Can I use filament-pixel with multiple Filament panels or tenants?
- The plugin is registered per Filament panel, so multi-panel applications can register it only where Pixel settings should be managed. For multi-tenant setups, whether settings are shared or tenant-specific depends on how you configure spatie/laravel-settings and the package's settings class. Use the navigationGroup() Closure if the group label needs tenant or locale-aware logic, and test navigation rendering in each panel.
- How should I test Meta Pixel tracking before production?
- Use a staging or test Meta Pixel ID first, then open your site and confirm the pixel script appears in the page source and fires the expected PageView or custom events. Browser tools such as Meta Pixel Helper and the Meta Events Manager test events view are useful for verification. Avoid sending production conversion data from local or staging environments.
- Is filament-pixel safe for production and who should access the settings?
- Treat Pixel settings like any other analytics configuration and restrict the Filament settings page to trusted admin roles through your panel's authorization policies. The pixel ID and script are public on the frontend by design, so access control is about preventing unauthorized changes, not hiding the ID. Also review your Content Security Policy to ensure the Meta Pixel script is allowed to load.
- How is filament-pixel maintained and what alternatives should I consider?
- Maintenance is relatively light because the plugin is an admin UI layer over spatie/laravel-settings and filament-analytics-core, but you should track those transitive dependencies, especially the core 3.1+ floor for navigationGroup(). Alternatives include hardcoding the Meta Pixel snippet in Blade, building your own Filament settings page, or using another analytics package with a Filament integration. Choose the plugin if you want a native Filament settings UI without custom code.