A privacy- and compliance-focused analytics suite bundling analytics, a tag manager, and a consent manager, with private-cloud and on-premises options.

INTEGRATES: bigquery · google-ads · looker-studio · powerbi · gtm-server-side · cookiebot · optimizely

Piwik PRO forked from the open-source Piwik project in 2013 and evolved into a proprietary analytics suite aimed at organizations with hard compliance requirements — public sector, healthcare, finance. Every plan bundles four modules: Analytics, Tag Manager, Consent Manager, and a Customer Data Platform for audience building and activation. Because the consent manager is native, consent state gates collection directly rather than through third-party glue.

Data model. Piwik PRO is session-based, closer to Universal Analytics than to GA4’s flat event stream. Everything is an event (page view, download, outlink, custom event, conversion), and events roll up into sessions; dimensions and metrics are scoped to either event or session level. Custom events use the classic category/action/name/value shape — category and action required, name and value optional. A session starts with a visitor’s first event and ends after 30 minutes of inactivity; that timeout is fixed and cannot be changed. New sessions are also forced by User ID changes, campaign-parameter changes (configurable), optionally referrer changes, or the new_visit=1 tracker parameter. Sessions cap at 5,000 events or 12 hours by default, and sessions spanning midnight are counted in both days — worth knowing when daily totals don’t sum to period totals.

Implementation notes. Billing is per “action,” so budget against total events, not sessions. Deployment is via the Piwik PRO container (tag manager and tracker in one snippet), and the docs cover a first-party collector setup for hybrid server-side collection. Raw-data export is a paid add-on: daily batch delivery to BigQuery (exports start at 4 AM UTC), plus AWS S3, Azure Blob, and SFTP destinations. Documented integrations include Looker Studio, Power BI, Google Ads, Search Console, Google Sheets, server-side Google Tag Manager, Google Consent Mode v2, Cookiebot, and several A/B testing tools; there is even a first-party MCP server for querying analytics from Claude.

Pricing changed materially in 2025. The long-running free Core plan was retired — it transitioned to the paid Business plan (from EUR 35/month, up to 2M monthly actions, 25-month retention, EU cloud in Sweden). Enterprise now comes in three tiers from EUR 366/month billed annually, with HIPAA BAAs and private-cloud hosting on the higher tiers. If your migration plan assumed “free GA4 alternative,” that positioning no longer holds; a 30-day trial replaces it.

Its differentiation remains deployment and residency, not analytical novelty: EU hosting by default, choice of data location, and private-cloud or on-premises deployment for Enterprise customers. Migrating from Universal Analytics is conceptually easy (same session/event mental model); migrating from GA4 means re-thinking event parameters into custom dimensions.

Use it when procurement, residency, or sector regulation rules out US-cloud analytics and you still need a full-featured suite with tag and consent management in one contract. Look past it when you want open-source code you can audit and run yourself (that’s Matomo or Snowplow), you need a free tier, or you want a lightweight tool without enterprise process.