- How do I install rocramer/nova-matomo-analytics in Laravel Nova?
- Install it with composer require rocramer/nova-matomo-analytics, publish the package config and assets, then register the card in your NovaServiceProvider. You populate the config file with your Matomo URL, site ID, and API token. You need a licensed Nova installation, and you should run the install in a spike branch first to confirm it renders on your Nova major.
- Which Laravel Nova versions does this Matomo analytics card support?
- The last tagged release is v0.5.0 from April 2021, and there is no stated supported Nova major in the available context. Nova's card and asset APIs have changed across majors, and the package has no public evidence of being tested against current Nova, Laravel, or PHP. Treat whether it installs and renders on your Nova version as the primary feasibility question and answer it in a spike.
- Is this package an iframe embed or a Matomo Reporting API client?
- The documentation is inconsistent. The description describes iframe embedding of Matomo widgets with token-based access for private instances, while the v0.5.0 changelog describes card aggregation changes and a renamed avg_time_generation metric, which implies a Reporting API client. Those are different implementations with different security reviews, scaling models, and failure modes, so read the source before planning. If it turns out to be an iframe, also confirm Matomo permits framing and that your CSP frame-src and X-Frame-Options allow the Matomo origin.
- Where is the Matomo API token stored and who can read it?
- The token lives in the published config file on the server, alongside the Matomo URL and site ID. The risk is that if the card builds signed iframe URLs or writes values into browser-visible attributes, any Nova user can read the token in devtools. Confirm the token is read-only, scoped to the minimum site, and rotatable before rollout.
- Does this card respect Laravel Nova's authorization and permission model?
- There is no reason to believe the card honors Nova's per-resource permission model. Assume that dashboard visibility implies analytics visibility for every Nova user who can see the card. If you need per-role or per-site access, plan to add your own canSee gate around the card registration and test it.
- What happens if Matomo is unreachable or times out?
- Failure behavior is not documented: an unreachable Matomo could yield a blank card, a cached value, or an exception in the dashboard render path. A broken dashboard is worse than no card, so test this in staging by blocking the Matomo origin. Decide up front whether you want fail-closed or fail-open behavior.
- How do I configure date ranges and widgets for the Matomo cards?
- The published config file holds the Matomo URL, site ID, and API token, and the card is described as offering configurable date ranges and widgets for visitors, page views, and other metrics. Check the source for the exact constructor and config keys before promising specific ranges. If you want 180- or 365-day ranges, confirm Matomo retention covers them and decide whether query cost lands on Matomo or your app.
- Is rocramer/nova-matomo-analytics actively maintained and safe for production?
- It has 22 stars, zero dependents, and its last release was April 2021, so no ecosystem has validated it against current Nova, Laravel, or PHP. The technical risk is medium-high and concentrated in abandonment and credential handling rather than code quality. Assume a fork is in your future, and keep the card strictly at the edge of the stack as an internal ops pulse view, never a source of truth for billing, SLAs, or external reporting.
- What are the alternatives to rocramer/nova-matomo-analytics for Matomo analytics in Laravel Nova?
- You can build a small custom Nova card against the Matomo Reporting API, embed Matomo dashboards directly with an iframe, or use a maintained analytics card from another vendor. The package itself is a sub-day integration, so the real comparison is maintenance cost against a fork. A custom card gives you explicit control over token handling, authorization, caching, and failure behavior.
- How should I test this Matomo Nova card before rolling it out?
- Spike it on staging with a read-only Matomo token and your production Nova major and PHP version. Verify that it installs and renders, check whether it is an iframe or Reporting API client, and confirm where the token can be read. Then test authorization visibility, Matomo timeout behavior, and aggregation semantics so the numbers on the dashboard cannot silently change.