Hub for running website analytics on your own servers with Matomo, Plausible or Umami, and how privacy law, consent rules, traffic volume and industry change the setup.
How self-hosting Matomo, Plausible or Umami changes GDPR and ePrivacy obligations: lawful basis, cookies versus cookieless tracking, IP anonymization, retention settings, data subject requests, and when a consent banner is still required.
Configuring analytics so French and similar regulators treat it as exempt from consent: the purposes allowed, anonymous statistics only, features that break the exemption such as User ID, heatmaps and session recording, and how Matomo documents the setup.
For hospitals, clinics and health tech vendors measuring patient-facing sites and portals: keeping tracking data off third-party ad platforms, separating public pages from authenticated portals, HIPAA safeguards for the analytics server and what to exclude from collection.
For agencies measuring public service sites: hosting analytics inside the government boundary, multi-site rollups across departments, accessibility of dashboards, records retention and why public bodies avoid sending visitor data to ad-funded platforms.
For banks, insurers and fintechs: excluding account and transaction pages from tracking, keeping data in approved jurisdictions, vendor risk reviews under DORA, retention aligned to policy and the access controls auditors expect on the analytics platform.
For universities and school districts measuring admissions, course and student portal traffic: FERPA and COPPA limits on student data, consent on EU campuses, multi-site analytics for faculties and campus hosting options.
For EU organizations removing US-hosted analytics after Schrems II and the regulator decisions on transfers: self-hosting in the EU, what still leaves the EU through CDNs and plugins, and the transfer documentation to keep.
For SaaS teams measuring the marketing site and signup funnel without sending data to ad platforms: Umami or Plausible for the website, when product analytics is a separate tool, campaign tracking and what enterprise customers ask about trackers.
For online stores: tracking orders, revenue, cart abandonment and campaign attribution on your own analytics server, Matomo's ecommerce features versus the Cloud-only revenue goals in Plausible, and plugins for Magento and WooCommerce.
Capacity planning for high-traffic sites: Matomo's published sizing for 1 million and 10 million monthly pageviews, separating app and database servers, archiving jobs, ClickHouse behind Plausible, and the operating effort each adds.
For intranets, internal portals and classified networks with no internet access: installing analytics from offline packages, updates without outbound connections, integrating with internal identity providers and what features depend on external services.
A requirements checklist for self-hosted web analytics: functional must-haves, hosting and data residency, identity and access, privacy and retention, integrations, operations and support, so a team can compare self-hosted options before choosing a platform.
Questions to put in an RFP or vendor brief for self-hosted web analytics: platform and edition fit, licence obligations, migration of existing data, hosting model, security evidence, support terms after go-live and how the fixed scope is defined.
Cost structure for self-hosted web analytics: subscription pricing published by SaaS vendors against self-hosted infrastructure, implementation, support and internal staff time, which drivers move each line, and when bringing in an implementation partner costs less than building alone.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.