- How do I install vincentbean/laravel-plausible in a Laravel app?
- Install it with Composer using composer require vincentbean/laravel-plausible, then publish the package config if you need to customize domain or API host settings. Set the required Plausible environment variables in your .env file and clear cached config. On Laravel 11 and newer, package discovery should register the service provider automatically; older versions may require manual provider registration.
- Does laravel-plausible support Laravel 13?
- Release 2.4.0 adds Laravel 13 support according to the changelog, which is an additive compatibility update rather than a behavior change. Confirm in composer.json whether the illuminate/support constraints were widened to include Laravel 13 or replaced the previous floor. Also check that your Laravel 10, 11, or 12 app remains supported and note the minimum PHP version before upgrading.
- How do I track custom events with the Plausible facade?
- Use the package facade to send custom events to Plausible's Events API, typically by passing an event name and any supported properties or URL context. The exact method signature is defined in the README and package source, so verify it against the version you install. Because server-side event dispatch makes outbound HTTP calls, consider whether you need to queue this work for high-traffic paths.
- Can I use laravel-plausible with a self-hosted Plausible instance?
- Yes, the package is described as supporting self-hosted Plausible instances. Configure the Plausible API host or domain setting through the published config file or environment variables so requests go to your instance instead of plausible.io. Verify the exact config key in the README for your installed version.
- Does laravel-plausible send analytics requests synchronously or through a queue?
- The overview does not state whether laravel-plausible dispatches events synchronously or via a queued job. Server-side tracking means outbound HTTP from your request lifecycle, so check the source and docs for queue support and whether queueing is opt-in. If it is synchronous, wrap calls in your own job for latency-sensitive or high-volume endpoints.
- Is laravel-plausible cookie-free and GDPR-friendly?
- Plausible Analytics is designed to be privacy-friendly and cookie-free, and this package is a thin Laravel integration for sending pageviews and events to it. The package does not by itself solve consent management, event taxonomy, or PII review for your application. If you send server-side events, review whether URLs or user identifiers are included and redact them where your compliance posture requires it.
- How do I add the Plausible tracking script to Blade views?
- The package provides Blade helpers for adding the Plausible tracking script, so you can include the helper in your main layout head section. Configure your Plausible domain in the package config or environment variables. For self-hosted Plausible, confirm the script source points at your instance if the helper supports overriding it.
- What Laravel and PHP versions does laravel-plausible require?
- The overview does not list exact Laravel and PHP version constraints, but release 2.4.0 adds Laravel 13 support. Check the package composer.json for illuminate/support and php requirements, and review the CI matrix to see which Laravel and PHP combinations are actually tested. Do not assume declared compatibility equals tested compatibility for your exact stack.
- How are Plausible API errors handled by laravel-plausible?
- The provided overview does not specify whether Plausible API errors are thrown, logged, or swallowed. Analytics failures are often non-fatal, which can lead to silent data loss if nothing monitors them. Review the package code for its HTTP client error handling and add logging or monitoring around event dispatch if you need visibility.
- Is vincentbean/laravel-plausible maintained, and what if it is abandoned?
- The package appears to be maintained by a single named maintainer with a narrow release cadence tied to Laravel majors. The code surface is small, so vendoring or forking is a realistic fallback if it is abandoned. Record maintainer concentration as an accepted risk and check the license, open issues, and recent releases before adopting it.