- How do I install filament-cookie-consent in my Laravel app?
- Install it with composer require jeffersongoncalves/filament-cookie-consent, then run the package migrations so spatie/laravel-settings can persist the banner configuration. Register the plugin class in your Filament panel provider's plugins() array. The banner markup and its CSS/JS assets are injected through Filament render hooks, so you do not need to edit any Blade templates.
- Which Filament, Laravel and PHP versions does filament-cookie-consent support?
- The compatibility table maps 1.x to Filament 3, 2.x to Filament 4 and 3.x to Filament 5. The current 3.x line targets Laravel 11 or newer and PHP 8.2 or newer. Check the README table and your composer.lock before bumping a panel, because a major Filament upgrade usually means switching package branches.
- Does filament-cookie-consent make my site GDPR and CCPA compliant?
- It gives you the mechanics of consent - a configurable banner, opt-in/opt-out consent types and a Google Consent Mode v2 signal - but it is not a complete compliance solution on its own. The default consent type is info, which is notice-only with no Allow/Decline buttons, so you must deliberately switch to opt-in or opt-out. There is no evidence of granular purpose categories, consent-record persistence (timestamp, policy version, categories), revocation propagation, pre-consent blocking of non-Google scripts, or a CCPA Do Not Sell/Share mechanism. Treat the compliance claim as a starting point and validate it with your legal team.
- Can I use it on my public marketing site or only inside the Filament panel?
- It is built for Filament panels and hooks the banner into panel render events, so out of the box it covers authenticated panel users rather than your public site. Google Consent Mode only matters where your Google tags actually run, which in most organisations is the public marketing site, not the admin panel. If that public surface is your legally material consent point, you will likely need a separate solution there.
- How do I customize the banner colors, position, theme and text?
- Everything is managed from a Filament settings page backed by spatie/laravel-settings, including colors, position, theme and banner content, so copy changes do not require a deploy. Because those values live in the database, they sit outside your repository and outside code review, which matters if you have strict change control. Note that the remote CSS and JS asset URLs are also configurable from that page.
- Does it support multiple languages for the consent text?
- Yes, multi-language support is listed as a core feature, and the banner content is stored through the settings package. You configure the text per locale in the settings page, or publish and adjust the package language files for your panel's locales. Verify the actual locale switching behaviour in a staging panel before relying on it for regulated copy.
- Does it work with Google Tag Manager, gtag and Google Consent Mode v2?
- Version 3.7.0 adds a Compliance section with a consent type setting and a Consent Mode v2 toggle that pushes default consent signals to the dataLayer. That only works if those defaults render before filament-gtm or filament-gtag load, and the package depends on render hook ordering that is documented only in a release note. Panel plugin registration order, custom theme hooks or a future plugin injecting head assets can break that ordering, so test your tag manager in staging. Also confirm the feature is relevant to your setup, since many teams run Google tags on the public site rather than in the panel.
- How do I safely upgrade to 3.7.x and which migrations must I run?
- 3.7.0 requires the underlying jeffersongoncalves/laravel-cookie-consent ^4.2, adds a new migration for the compliance settings, and needs php artisan migrate after updating. Because a minor release forces a major dependency bump plus a schema change, pin an exact version instead of floating ^3.7. Review the parent package's 4.x changelog for config, view and asset-path changes and confirm the transitive floor resolves in your lockfile. Upgrading does not change existing behaviour - installs stay in notice-only info mode until you flip the consent type yourself.
- Is filament-cookie-consent production-ready and what are the maintenance risks?
- It is a small package with a single maintainer, minimal stars and dependents, and no commercial backing or SLA, so plan for the possibility of maintaining your own fork. Version discipline has been loose: a Filament constraint bump shipped as a patch previously, and 3.7.0 ships a required migration plus a major transitive bump as a minor. Pin exact versions, read release notes before every upgrade, and review the database-driven asset URLs since banner behaviour is partly controlled outside code review. Run upgrades in staging because the install is now a two-package, multi-migration operation.
- What are the alternatives to filament-cookie-consent?
- The main alternatives are hand-rolling a small Blade banner with your own cookie and consent-record table, or adopting a dedicated consent management platform when you need granular purpose categories, audit records and CCPA Do Not Sell/Share flows. This package's niche is admin UX for a banner inside a Filament panel plus a Consent Mode v2 emitter. Pick it if that is precisely your need, and pick something broader if your public marketing site is the real compliance surface.