Piwik PRO vs June
Side-by-side trajectory, velocity, and editorial themes.
Piwik PRO ships steady fortnightly fix releases with quiet integration improvements.
Recent releases (18.59 through 18.66) follow a tight bi-weekly cadence dominated by analytics bug fixes — chart tooltips, scheduled-report PDF rendering, sorting and pagination edge cases — interleaved with smaller integration improvements: Google Ads account-switching, expanded AI-referral domain detection, sequential-audience sort and filter, in-app contact form. No directional moves in this window.
The product is in maintenance-and-polish mode, focused on the edges where reports, exports, and integrations break. The most signal-bearing recent change is broader Google Ads account management plus more domains classified as AI-driven traffic — small hints at where buyers are asking for sharper analytics.
Expect Piwik PRO to keep shipping defect-density patches at this cadence, with what feature growth there is concentrated in AI-traffic attribution and Google Ads tooling rather than core analytics primitives.
June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.
See more alternatives to Piwik PRO →
See more alternatives to June →