Offen Fair Web Analytics vs Simple Analytics

Opt-in only collection with first-party cookies

No analytics events are recorded until the visitor actively consents. Cookies are first-party and the tracker is meant to run on a same-site subdomain so third-party cookie restrictions and cross-site tracking models do not apply. Visitors who never opt in leave no usage trail—expect lower absolute volumes than cookieless tools that measure by default.

Browser-side end-to-end encryption of usage events

Clients encrypt usage data before it leaves the browser; the server stores ciphertext and cannot decrypt events alone. Only the visitor (via their cookie) and the matching operator account can open that visitor's data in the Auditorium. Practical impact: a compromised database or overly broad ops access does not yield plaintext browsing histories the way a typical self-hosted analytics DB would.

Auditorium for both operators and visitors

Operators see aggregates across pages where the installation is active (unique users/sessions, top pages, filters). Each opted-in visitor can open the same style of UI for their own data only, with plain-language metric explanations, and can delete data or fully opt out later. This is the fair design point: measurement is not a one-way glass.

Essential metrics without IP or User-Agent capture

Dashboards cover real-time activity, page views, unique users and sessions, bounce rate, returning users, top pages, referrers, UTM campaign/source, landing and exit pages, weekly retention, and load time. Location is country-level from timezone mapping; mobile share uses orientation capability—not IP geolocation or UA parsing. No heatmaps, session replay, or warehouse-grade product analytics.

Lightweight self-host: binary, Docker, SQLite or SQL

Production installs use a single binary (Linux/Windows/macOS) or the offen/offen image; docs also cover Heroku, Uberspace, and YunoHost. Default store is SQLite; MySQL and Postgres are supported. AutoTLS can request Let's Encrypt certificates. Config is environment variables or offen.env. You own uptime, backups, SMTP for password reset, and the subdomain layout.

Multi-site accounts, teams, and short retention

One installation can cover multiple websites with shared team access. Default retention is six months with automatic deletion; operators can shorten retention (e.g. 12 weeks, 30 days, 7 days) knowing shorter values purge older events on startup. Consent banner appearance is customizable; UI locales include EN, DE, FR, ES, PT, and VI.

Cookieless metrics without visitor IDs or stored IPs

Collects pageviews, referrers, UTMs, time-on-page, and scroll depth without cookies, localStorage, fingerprints, or stored IP addresses. Unique visits are inferred from referrer hostname matching, not device IDs. Built for sites that want analytics without a consent banner solely for this tool—and without building visitor profiles.

Country from time zone, not geo-IP

Country-level location is derived from the visitor’s IANA time zone rather than IP lookup, so IPs can be dropped end-to-end. City/region is not available; some border and multi-country zones can mis-tag. Useful when legal teams reject IP-based geolocation even when hashed.

Cookieless layer beside GA4 and BI stacks

Positioned to measure traffic lost when consent is denied in cookie-based tools. Import historical Google Analytics data; export via Stats/Export APIs and integrations toward Looker Studio, Power BI, and warehouse workflows so analysts can compare consented vs observed traffic without replacing every GA report.

Lightweight script, events, goals, and ad-blocker bypass

Vendor claims a single script under 5 KB. Supports events, automated events (e.g. downloads, outbound links), goals, filters, email reports, and robot/referrer-spam controls. Ad-blocker resilience is via first-party proxy or custom subdomain CNAME—not automatic immunity for every blocklist.

Team access, SSO, and EU-operated SaaS

Hosted product from Simple Analytics B.V. (Amsterdam) with role-oriented team features on higher tiers and documented SAML SSO for Okta and Microsoft Entra. No official self-host edition—operations and residency follow the vendor’s EU infrastructure and public subprocessor list.