Weave Code
Insights Laravel Package
capell-app/insights
Insights is a Capell module for Laravel that adds analytics and reporting to your admin panel, giving editors and site owners visibility into content performance and activity through concise dashboards, metrics, and summaries.
Cookie-light, GDPR-aware web analytics built into your Capell admin — page views, clicks, visitor journeys, and consent, with no third-party scripts and no data leaving your server.
Frequently asked questions about Insights
- How do I install capell-app/insights in a Laravel application?
- Install the package with Composer using composer require capell-app/insights, then publish its config file and migrations and run php artisan migrate. The service provider is expected to be auto-discovered, so no manual registration should be needed. Pin an explicit version such as 1.0.48 rather than floating on a caret constraint, and install into a sandbox branch first so you can review the published migrations before they touch a real database.
- Does Capell Insights send my application data off-host or collect telemetry?
- The public documentation does not describe any outbound telemetry or vendor endpoint, and the package appears designed to read data already stored in your own application to build dashboards and summaries. However, collection scope, storage location and retention are not fully documented, so review the published config file and the source before deploying. If you handle regulated or personal data, treat outbound transmission as an open question and confirm it with the maintainers in writing.
- Which Laravel and PHP versions does capell-app/insights support?
- The authoritative answer is the composer.json constraints on php and illuminate/* packages, so check those against your pinned runtime before installing. Verify the package against your actual stack, for example PHP 8.2 or newer with Laravel 10, 11 or 12, and run your own test suite rather than relying on the package description. Because the release notes for recent patch versions are empty, do not assume framework support has stayed unchanged across those releases without checking the diff.
- Do I need Capell CMS or Filament to use Capell Insights?
- Insights is published under the Capell vendor namespace and is positioned as a first-party module for Capell-based Laravel applications, so it may assume host application primitives such as Filament, Livewire or Capell CMS structures. If you are running a generic Laravel product, the value proposition is unproven and any hard dependency should be treated as an architecture decision rather than an install detail. Confirm whether the package is a library you embed or a module that expects a host application before committing.
- What changed between Insights v1.0.44 and v1.0.48?
- The release notes for those four patch versions contain no content beyond a compare link, so the changelog alone cannot tell you whether the changes are bugfixes, reverts or hotfixes. Diff the compare URL release by release and read the published migrations directly, because a patch release can still alter production schema. If any of the four revisions modified an already-published migration, treat it as a breaking change regardless of the version number.
- Can I add custom metrics and widgets to the Insights dashboard?
- Yes. The package exposes an extensible API for defining custom metrics and registering your own dashboard widgets alongside the built-in ones. That makes it possible to track application-specific events or content signals that the default reporting views do not cover. Review the extension points in the source first, since the API surface is not documented in detail and may change between patch releases.
- How do I configure data retention and data sources in Capell Insights?
- Insights ships configurable data sources and retention settings, which you control through the published config file. After publishing, set the retention windows that match your privacy policy and storage budget, then make sure the package's scheduled jobs or Artisan commands are registered so old records are pruned on time. Verify pruning actually runs in staging before enabling the package in production.
- What database tables and migrations does Capell Insights add?
- The package ships publishable migrations that create its own tables for storing collected metrics and aggregated reporting data. Read every emitted migration line by line before running them, especially when absorbing several patch releases at once, since published migrations are the one artefact where a patch version can still change production schema. Plan a rollback path using migrate:rollback for any new tables before you deploy.
- Will Capell Insights slow down my Laravel application in production?
- The package reads application data to build dashboards, so query counts and page timings are the things to measure. Deploy to staging with production-shaped data volumes, compare timings with the package enabled and disabled, and watch for global middleware, route registrations or scheduled jobs that could add overhead on every request. Then release behind a feature flag and monitor for a full release cycle before removing it.
- Is capell-app/insights actively maintained and what are the alternatives?
- Maintenance, roadmap and security response are controlled by a single vendor, and there is no published support SLA or security policy visible in the material reviewed. There is also no evidence of a maintained test suite or CI matrix you can inspect for Laravel version coverage, which is a real risk for a package that touches production data. Alternatives include building lightweight reporting views yourself, using a general-purpose Laravel analytics package, or adopting an external product analytics service if off-host collection is acceptable to you.
Weaver
How can I help you explore Laravel packages today?