- Is alt-design/alt-cookies a Laravel package or a Statamic addon?
- It is a Statamic addon, described as Easy Cookies and Google Analytics for Statamic. It uses Statamic's addon lifecycle, config and view publishing, Antlers or Blade components, and Control Panel settings. Although it runs on Laravel, it is not a general-purpose Laravel package for arbitrary applications.
- How do I install and set up Alt Cookies on a Statamic site?
- Install it with Composer, publish the config and views, then inject the consent component into your site layout. You configure the Google Analytics measurement ID through the Statamic Control Panel. The integration is shallow, so time to a first working banner is typically measured in hours rather than days.
- Will Alt Cookies work in a standard Laravel app, an Inertia or Livewire SPA, or a headless API?
- No. The real integration boundary is Statamic's runtime, not Laravel's, so fit is effectively zero outside a Statamic site or Statamic-driven content surface. For a conventional Laravel app, Inertia or Livewire SPA, or headless API, treat this package as a non-starter unless Statamic is already in the stack.
- How does Alt Cookies gate Google Analytics until the visitor gives consent?
- Alt Cookies sorts cookies into categories and conditionally loads scripts, so the Google Analytics snippet is only loaded after the relevant consent is granted. The GA measurement ID is configured in the Statamic Control Panel. You should still verify the exact pre-consent behavior, especially if you depend on Google Consent Mode semantics.
- Which Laravel and Statamic versions does Alt Cookies support?
- The supplied evaluation does not list explicit version constraints, so check the package composer.json for its Laravel and Statamic requirements before installing. Statamic addons are tightly coupled to Statamic's major release cadence, including Control Panel, publishing conventions, and Antlers. Test on your target Statamic version rather than assuming compatibility.
- What is new in Alt Cookies v1.3.2-alpha?
- The alpha adds a Control Panel cookie scan that renders site pages to observe cookies set by JavaScript and the server. It also generates policy copy formatted for Bard with a preferences-reopen link hook, applies accept and reject without a page reload, adds a default consent state, and introduces an updateConsent() JavaScript API. These features are only on the pre-release 1.3 line.
- Should I use Alt Cookies v1.3.2-alpha in production or stay on stable 1.2?
- The 1.3.2 release is an alpha on a pre-release line with no production track record, and the package still has minimal adoption evidence. Stable 1.2 sites are unaffected unless they explicitly require an alpha. Use the alpha only if you need the new scan, policy copy, no-reload, or updateConsent() features and can thoroughly test a compliance-bearing component.
- Does Alt Cookies support Google Consent Mode v2?
- That is unverified. The default consent state and updateConsent() API suggest Consent Mode-style default and update semantics, but the notes provide no evidence of Consent Mode v2 support. You must test whether analytics_storage and ad_storage are denied before consent and whether updateConsent() maps to a gtag consent update call.
- Can visitors change or reopen cookie preferences without a page reload?
- Yes on v1.3.2-alpha, which adds no-reload application of accept and reject plus a preferences-reopen link hook in the generated policy copy. The changelog also states that nothing in the public JavaScript API has been removed or renamed since v1.2.7, so there is no forced migration. On older stable releases, confirm reload behavior in your own testing.
- Is Alt Cookies a full consent management platform for GDPR audits?
- No. It provides a consent banner, Google Analytics gating, and, in the alpha, cookie discovery and policy drafting, but there is no vendor or tag registry, no stated consent-record retention for auditability, and no multi-jurisdiction category model beyond what the banner exposes. It also generates a server-side cookie scan, which has load, environment-targeting, and potential credential or PII exposure implications. For audit-grade consent records or complex multi-jurisdiction needs, plan to build additional controls or use a dedicated consent management platform.