Weave Code
Laravel Server Analytics Laravel Package
ohseesoftware/laravel-server-analytics
Server-side analytics for Laravel that tracks page views, referrers, UTM parameters, and visitor data without client-side JavaScript. Lightweight, privacy-friendly, and easy to integrate with a simple API and dashboard-ready storage.
Server side analytics for your Laravel application or website.
Frequently asked questions about Laravel Server Analytics
- What is ohseesoftware/laravel-server-analytics?
- It is a server-side analytics package for Laravel applications and websites. It records page views, referrers, UTM parameters, and visitor data without relying on client-side JavaScript. The package is designed to be lightweight and privacy-friendly.
- Does laravel-server-analytics require client-side JavaScript?
- No. The package is built for server-side tracking, so it does not require client-side JavaScript to capture analytics. That makes it suitable for server-rendered pages and privacy-sensitive sites.
- Does v4 require Laravel queue workers?
- Version 4.0.0 moves request tracking onto Laravel's queue system, so tracking runs in queued jobs. Applications should have queue workers running to process those jobs. If you do not already run queues, v4 adds an operational dependency on workers.
- Which Laravel and PHP versions does it support?
- The v4.0.0 release notes do not state the supported Laravel and PHP version matrix. You should confirm compatibility in the package metadata, README, or composer.json before upgrading. Do not assume the same support matrix as v3 without checking.
- What analytics data can laravel-server-analytics track?
- It tracks page views, referrers, UTM parameters, and visitor data. Tracking is handled server-side rather than through a browser script. Storage is described as dashboard-ready, meaning you can build reporting on top of the recorded data.
- How do I install laravel-server-analytics in a Laravel app?
- Install it with composer require ohseesoftware/laravel-server-analytics. Then follow the package's installation instructions for configuration, migrations, and any required setup. For v4, make sure queue workers are running so tracking jobs are processed.
- Is laravel-server-analytics privacy-friendly?
- It is designed to be privacy-friendly because tracking happens server-side without client-side JavaScript. However, privacy compliance still depends on what visitor data you store, how long you retain it, and your legal basis for processing. Review the package's data collection against your own requirements.
- How do I upgrade laravel-server-analytics from v3 to v4?
- Treat v4 as a breaking major release because the public API changed to support tracking requests via queued jobs. Inventory all tracking call sites, pin v3.8.1 while you prepare, and upgrade in a non-production environment first. The release notes do not include a detailed migration guide, so validate call sites and queue behavior carefully.
- What are the production risks of queued analytics tracking?
- Queued analytics can fail silently if jobs are not monitored, retried, or dead-lettered. Payloads must be serializable, and retries must be checked for duplicate records or lost events. You should also confirm whether event timestamps are preserved from request time or assigned when the job runs.
- Is there still a synchronous tracking option in v4?
- The v4.0.0 release notes say tracking requests are moved onto a queued job, but they do not state whether a synchronous path remains. Check the package documentation or source before relying on synchronous writes. If immediate reporting consistency matters, test the queued behavior in your environment.
Weaver
How can I help you explore Laravel packages today?