Piwik Bundle Laravel Package

Product Decisions This Supports

• Instrumentation approach: decide between a maintained Symfony-side tracking integration and hand-rolled Twig snippets or a client-side tag manager. This package is commodity glue around Matomo/Piwik tracking code injection — the decision is "adopt glue vs. own ~50 lines," not a strategic platform bet.
• Build vs buy: buy is defensible only when the maintenance signal is good. 3.5.0 is a positive signal (active CI, dependency hygiene, forward framework compatibility) but the functional surface is unchanged, so it doesn't move the needle on capability.
• Roadmap / platform upgrade: the Symfony 8.x allowance in 3.5.0 is the one roadmap-relevant item — it keeps the integration viable if your platform plan includes a Symfony 8 upgrade. If Symfony 8 is not on the roadmap, this release changes nothing for you.
• Use cases it serves: consent-aware page-view tracking, goal/e-commerce tracking hooks, multi-site or multi-tenant tracking IDs, and centralized control of tracking configuration across many templates and environments.
• Scope caveat: this is a Symfony bundle, not a Laravel package — no Laravel service provider, no config/publish idiom. In a Laravel-first codebase the realistic decision is "write the small integration ourselves" rather than adopt a Symfony bundle.

When to Consider This Package

Consider it when:

• You run Symfony (or a hybrid stack with Symfony bundles) and want Matomo/Piwik tracking wired through configuration instead of copy-pasted template snippets.
• You want tracking IDs and options out of application code and centrally managed per environment.
• You value a dependency that is actively maintained: 3.5.0 shows continued QA investment (PHPUnit 10.x, composer-require-checker in GitHub Actions) and forward compatibility (Symfony 8.x).
• You need confidence the package will track upcoming framework upgrades rather than pin you to an EOL Symfony major.

Look elsewhere when:

• You are Laravel-first. No first-party support, and the glue is cheap enough to own.
• You need server-side event dispatch with queues, retries, and consent primitives (Matomo Measurement Protocol / HTTP API). A bundle that injects client tracking JS does not cover that.
• Your analytics stack is GA4, Segment, Snowplow, or warehouse-first — this is Matomo-specific.
• You require vendor security attestations or guaranteed support SLAs; a small, single-maintainer package won't provide them.

Adoption risks:

• 3.5.0 raises dev-side requirements (PHPUnit 10.x) and bumps dependency constraints. Runtime constraints are effectively unchanged for consumers, but re-run your suite and confirm no transitive major is pulled in.
• Maintainer concentration (effectively one active maintainer) remains the primary long-term risk — the maintenance releases reduce, but do not remove, it.
• No breaking changes, deprecations, or new features in 3.5.0; upgrading from 3.4.x should be a no-op at the application level.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost integration that wires Matomo analytics into a Symfony codebase. The new 3.5.0 release is maintenance-only — no new features, no breaking changes, no customer-visible impact. Its value is reassurance: the package is alive, its CI is being hardened, and it now permits the next Symfony major, which de-risks a future platform upgrade. Recommendation: keep it as-is, allocate no roadmap capacity, and treat ongoing upkeep as infrastructure hygiene rather than a product investment.

For engineering: 3.5.0 is housekeeping — PHPUnit 10.x, package structure cleanup, composer-require-checker added to CI, and Symfony 8.x now allowed. Expect zero migration work from 3.4.2; the practical tasks are verifying dependency resolution and re-running the test suite. The Symfony 8 allowance is the only forward-looking change and should be validated in a branch before you rely on it. If the team is Laravel-only, this is not the right dependency — a short spike to implement equivalent tracking configuration in-house will be cheaper than carrying a Symfony bundle for one feature.