Alceris Analytics vs Offen Fair Web Analytics

Cookieless aggregation without IP storage

Per the privacy policy, Alceris does not set cookies, session IDs, or similar client storage; IPs are not logged; the full User-Agent is not stored. Only aggregated fields such as page URL, referrer, parsed browser/OS, language, and timezone-based country are retained—aimed at sites that want stats without an analytics cookie banner.

One-line async script, deferred events, WordPress plugin

Install via a single async script from alceris.com with your site data-id (docs include a deferred alceris() queue so early events are not lost). WordPress operators can use the official plugin and paste the dashboard site ID. SaaS-only—there is no self-hosted server package.

Realtime pageviews and custom events with metadata

Pageviews and events are processed immediately into the dashboard. Custom events are sent with alceris('event', name, { ...metadata }), useful for button clicks, form steps, or content attributes without building a full product-analytics stack.

UTM campaigns, outbound links, and cross-domain flows

UTM parameters are extracted for campaign reporting; outbound link clicks are tracked automatically; cross-domain tracking follows visitors across owned domains. Scope is web traffic measurement—not session replay or heatmaps.

Optional Google Search Console and first-party proxy

Connect Search Console to import query impressions, clicks, and terms (data removed on unlink). Docs also describe reverse-proxying script.js and the img.alceris.com data endpoint through your own domain so ad-blockers are less likely to drop hits—at the cost of operating that proxy yourself.

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.