etracker vs Offen Fair Web Analytics

Compare etracker and Offen Fair Web Analytics on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics, Matomo

etracker

Germany· Web Analytics

Needs review

Shortlist etracker when you need German-hosted marketing-grade web analytics with a cookieless default, integrated tag/consent tooling, and optional ad conversion sync. Skip when you must self-host open source (prefer Matomo) or only need lightweight pageview charts (prefer Plausible or similar). Treat ePrivacyseal consent-free claims as vendor-audited posture—confirm with your counsel and DPIA.

Cookieless default trackingEU/DE hosted (IPHH)ePrivacyseal (claimed)Tag + consent suiteAd conversion syncSaaS only (not self-host)

View listing Visit Website

Offen Fair Web Analytics

Germany· Web Analytics

Needs review

Shortlist when you want self-hosted, Apache-2.0 analytics that only measures after opt-in, encrypts events in the browser, and lets visitors open their own data in the Auditorium. Skip when you need cookieless full-coverage metrics, session replay/heatmaps, or zero-ops managed EU hosting—consider Plausible, Pirsch, or Friendly Analytics instead.

Opt-in onlyBrowser E2E encryptionSelf-hostedApache-2.0Visitor data accessBerlin-based project

View listing Visit Website

Highlighted rows differ between the two products.

etracker vs Offen Fair Web Analytics: Snapshot
Feature	etracker	Offen Fair Web Analytics
Country of origin	Germany	Germany
Category	Web Analytics	Web Analytics
Open source	No	Yes
Self-hosted	No	Yes
Headquarters	Germany	Germany
Legal entity	JustRelate Deutschland GmbH (Charlottenburg HRB 218235); product brand JustRelate etracker / etracker	Public legal notice lists Frederik Ring, Berlin (offen.software); product authors Frederik Ring and Hendrik Niefeld—no separate GmbH name verified on imprint
Governing law	Not listed	Germany (indicative from Berlin imprint)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Low	Low
Hosting / residency	Primary analytics processing on etracker's own servers in Germany/EU with housing at IPHH Internet Port Hamburg GmbH (vendor: no third-party access to apps/data for housing). Optional customer-enabled outbound paths to Google/Meta/TikTok/Microsoft Ads (conversion upload) and Google Looker Studio connectors—not core storage hosts.	Product is operator self-hosted (your VPS/cloud/on-prem). No Offen multi-tenant analytics SaaS or vendor subprocessor list for visitor events. Related marketing site (offen.software) names Hetzner Online GmbH (Germany) as host—not the analytics data path. Optional community deploys include Heroku (operator choice).
Summary	German SaaS web and marketing analytics from JustRelate: cookieless default tracking, integrated tag/consent management, e-commerce and ad conversion sync on EU-hosted servers.	Open-source, self-hosted web analytics with opt-in consent, browser-side end-to-end encryption, and a shared Auditorium so visitors can see and control their own usage data.
Tags	analytics privacy gdpr cookieless marketing-analytics saas consent-management e-commerce	analytics privacy gdpr open-source self-hosted opt-in e2e-encryption

At a glance: etracker vs Offen Fair Web Analytics
At a glance	etracker	Offen Fair Web Analytics
HQ / legal entity	JustRelate Deutschland GmbH, Berlin (product ops Hamburg)	Not listed
Product type	Web & marketing analytics SaaS (+ tag/CMP modules)	Not listed
Hosting	Own servers, IPHH housing, Hamburg/Germany	Not listed
Open source	No	Not listed
Self-hosted	No	Not listed
Commercial model	Usage-based SaaS licence (hit tiers); trial commonly offered	Not listed
HQ / authors	Not listed	Berlin, Germany (Frederik Ring & Hendrik Niefeld)
License	Not listed	Apache-2.0 (code/docs); logo CC-BY-NC-ND-4.0
Delivery	Not listed	Self-host only (binary, Docker, community deploys)
Consent model	Not listed	Opt-in only; first-party cookies
Default retention	Not listed	6 months (configurable shorter)
Funding note	Not listed	NLnet NGI support (project-stated)

Key capabilities: etracker vs Offen Fair Web Analytics
Key capabilities	etracker	Offen Fair Web Analytics
Cookieless default tracking	Yes	Not listed
EU/DE hosted (IPHH)	Yes	Not listed
ePrivacyseal (claimed)	Yes	Not listed
Tag + consent suite	Yes	Not listed
Ad conversion sync	Yes	Not listed
SaaS only (not self-host)	Yes	Not listed
Opt-in only	Not listed	Yes
Browser E2E encryption	Not listed	Yes
Self-hosted	Not listed	Yes
Apache-2.0	Not listed	Yes
Visitor data access	Not listed	Yes
Berlin-based project	Not listed	Yes

etracker

Cookieless session analytics (consent-oriented default)
Server-side session tokens link interactions without analytical cookies or device fingerprinting by default; IP truncation and daily-rotating hashes limit long-term recognition. Suits sites that want visit/conversion metrics under legitimate interest while keeping optional hybrid cookies behind consent.
Integrated tag and consent management
One product surface to load etracker and third-party tags and sync them with consent rules, reducing dual maintenance between a separate CMP and GTM. Best when marketers need gated Maps/ads tags without rebuilding the full Google stack.
Server-side conversion sync to major ad platforms
Upload conversions measured in etracker to Google Ads, Meta, TikTok, and Microsoft Ads so bid algorithms receive server-side signals. Customer-controlled outbound path—useful for paid media, but introduces destination-platform processing outside German housing.
E-commerce, UX scrollmaps, and multi-level drill-downs
Shop funnels from product list to order (including vouchers and abandonment), scrollmaps projected on pages, and reports with multi-dimension drill-downs plus attribution model switching. Aimed at merchandising and growth teams, not just pageview counters.
First-party tracking domain and BI exports
Optional own-subdomain tracking (including Let's Encrypt workflow docs) to reduce ad-blocker and ITP loss; connectors/API/SFTP-style raw data paths toward Looker Studio, Power BI, and warehouses. Ops teams still configure domains and data pipelines themselves.

Offen Fair Web 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.

Assurance & compliance: etracker vs Offen Fair Web Analytics
Assurance & compliance	etracker	Offen Fair Web Analytics
Independent security / privacy audit	Vendor claimed ePrivacyseal materials and vendor pages describe independent ePrivacy Consult audit of consent-free cookieless analytics posture; not a full public penetration-test report. Vendor also claims regular infrastructure pen tests.	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.
ISO 27001	Partial IPHH housing described as ISO/IEC 27001:2013-certified. No public organisation-level ISO 27001 certificate for etracker/JustRelate analytics found in materials reviewed.	Not found No public ISO 27001 certification claim found on official site or docs.
SOC 2 / SOC 3	Not found No public SOC 2/SOC 3 report located on official trust/security pages reviewed.	Not found No public SOC 2/3 report found.
GDPR / EU data protection	Vendor claimed EU/DE controller-processor setup; cookieless default under legitimate interest; Art. 28 DPA on registration; privacy notice + objection patterns documented.	Vendor claimed EU authors; opt-in, data minimization (no IP/UA), visitor access/erasure, short default retention, Datensparsamkeit framing. Self-host means operator remains controller—confirm your legal basis and notice.
US CLOUD Act exposure (indicative)	Partial EuropeanStack assessment: German entity, no known US parent, own-server housing at IPHH (no public AWS/GCP/Azure analytics store) → core exposure low. Partial because optional conversion sync and Google connectors can send data to US-group destinations when enabled by the customer. Not legal advice.	Partial EuropeanStack assessment: no known US parent; product not delivered as US-hosted vendor SaaS. Operator-chosen infrastructure (including optional Heroku/US cloud) can still create CLOUD Act paths for stored ciphertext/metadata. Not legal advice.
Data processing agreement (B2B)	Vendor claimed Vendor states DPA/AV concludes on account registration; public DPA PDFs and in-app DPA under Settings → Data processing agreement.	Not applicable No multi-tenant vendor analytics processing relationship documented; operator self-hosts and is typically controller. Custom development/support via offen.software is separate from a standard SaaS DPA.
ePrivacyseal (privacy seal)	Vendor claimed Vendor and ePrivacy listing materials assert seal for consent-free cookieless mode under GDPR/TDDDG. Scope is privacy/consent posture, not a general security cert.	Not listed
EU AI Act	Not applicable Product is web/marketing analytics, not an AI-system offering as primary positioning.	Not applicable Web analytics metrics product; not an AI system product.

Considerations & known limitations: etracker vs Offen Fair Web Analytics
Considerations & known limitations	etracker	Offen Fair Web Analytics
Consent-free claims still need local legal review	Medium ePrivacyseal and vendor guidance support cookieless default under TDDDG/GDPR, but hybrid cookies, marketing tags, and non-German supervisory interpretations can change the picture. Operators remain responsible for DPIA and notices.	Not listed
Optional conversion sync / BI connectors to US platforms	Medium Core storage is claimed German; enabling Google/Meta/TikTok/Microsoft conversion upload or Looker Studio connectors creates additional processing at those destinations. Map each integration in your transfer assessment.	Not listed
Limited public enterprise security certs	Low No public SOC 2 or org-level ISO 27001 package found; IPHH housing ISO and ePrivacyseal are the main published assurance artefacts. May slow enterprise security questionnaires.	Low Procurement checklists that require vendor ISO 27001/SOC 2 will stall; evidence is open source and design docs, not cert registry entries.
SaaS-only, closed source	Low No self-host path. Exit requires export/API planning; multi-year usage contracts are common in this category—confirm terms on the vendor site.	Not listed
No exhaustive public subprocessor register	Low Housing (IPHH) is named; a full live subprocessor schedule (support tooling, email, etc.) was not found as a single public table. Request under NDA/procurement if required.	Not listed
Opt-in undercounts absolute traffic	Not listed	High Visitors who never consent generate no events. Growth and content KPIs will not match cookieless tools or GA-style default measurement—treat as design, not a misconfiguration.
You own uptime, backups, and secrets	Not listed	Medium No managed Offen cloud. Operators must run HTTPS/subdomain layout, set OFFEN_SECRET for stable sessions, configure SMTP for resets, and back up SQLite/SQL—plus avoid reverse proxies that log IPs if minimization is a goal.
E2E crypto is vendor-claimed architecture	Not listed	Medium Browser-side encryption and server inability to decrypt are core claims from project docs/README, not independently audited in public materials found. Security-sensitive orgs should review source or commission assessment.
Hosting choice reintroduces cloud jurisdiction	Not listed	Medium Self-host on US-group cloud or Heroku means CLOUD Act/subprocessor analysis shifts to your host even though Offen itself is Berlin-based OSS without a vendor SaaS region map.
Essential metrics only	Not listed	Medium No heatmaps, session replay, advanced funnels, or product-analytics warehouse features. Wrong tool if the shortlist criterion is UX research depth rather than fair traffic statistics.

Fit

etracker

Best fit when

EU/German organisations replacing GA4 to reduce consent-mode data loss and US-linked analytics storage
Performance marketers needing campaign attribution plus server-side conversion upload to major ad platforms
E-commerce teams measuring product-to-checkout funnels, vouchers, and abandonment in one privacy-oriented SaaS
Agencies managing multi-account portfolios that want integrated tag and consent management without a separate CMP licence stack
Publishers and regulated sectors that require a German processor, Art. 28 DPA, and documented objection mechanisms

Poor fit when

Teams that must self-host open-source analytics with full infrastructure control (Matomo, Offen, etc.)
Sites that only need minimal cookieless pageviews without shop, UX, or paid-media depth
Procurement that requires published SOC 2 or organisation-level ISO 27001 for the analytics vendor before shortlisting
Buyers expecting a durable free-forever tier comparable to Google Analytics

Consider instead when

When: You need open-source self-host or full data-plane control on your own infrastructure
Consider: Matomo (self-host or Matomo by Stackhero / Friendly Analytics managed)
etracker is closed-source SaaS only
When: You want a lightweight EU cookieless counter without marketing suites
Consider: Plausible Analytics, Wide Angle Analytics, or digistats Analytics
Simpler product surface; fewer e-commerce and ad-sync features
When: You stay fully inside Google Ads optimisation and accept consent/US-transfer tradeoffs
Consider: Google Analytics 4
Deeper Google ecosystem wiring; different privacy posture

Offen Fair Web Analytics

Best fit when

Public-sector, media, NGO, or mission-driven sites that need visitor-visible transparency and strict opt-in
EU teams that must keep analytics off third-party trackers and can run a small always-on instance
Operators who want first-party subdomain cookies, CSP-aware embedding, and no IP/User-Agent collection
Organisations evaluating fair-processing design over maximum measurement coverage
Teams comfortable with SQLite or SQL self-host ops (binary or Docker) and publishing their own privacy notice

Poor fit when

Product or growth teams that require near-complete traffic measurement without consent friction
Needs for heatmaps, session replay, funnels, or ad-ecosystem attribution comparable to Hotjar/Mixpanel/GA
Buyers seeking a vendor-managed multi-tenant analytics cloud with SLAs and a signed vendor DPA as processor
Large enterprises that require public ISO 27001/SOC 2 or third-party security audit packs before shortlist

Consider instead when

When: You want privacy-oriented analytics with managed EU hosting and lower consent friction
Consider: Plausible Analytics or Pirsch Analytics
Typically optimised for simpler cookieless or low-friction models and hosted plans; less radical visitor Auditorium design than Offen.
When: You need EU hosted privacy analytics with operator support and less self-host burden
Consider: Friendly Analytics
European catalog peer oriented to hosted privacy analytics; compare consent model and feature depth to Offen’s opt-in + E2E approach.
When: You need deep product analytics, funnels, or session UX tooling rather than fair traffic metrics
Consider: Hotjar, Mixpanel, or a full GA4 stack (with legal review)
Different category: richer product/UX analytics, different jurisdiction and subprocessor profile.

Open questions for due diligence

etracker

Will procurement receive a current subprocessor list covering support, email, and any non-IPHH infrastructure?
Does JustRelate publish an organisation-level ISO 27001 or SOC 2 report for the analytics service (beyond IPHH housing)?
For your jurisdictions outside Germany, does counsel accept the cookieless legitimate-interest posture without a consent banner?
Which optional outbound integrations (ads conversion upload, Looker Studio, third-party tags) will you enable, and how are those transfers documented?

Offen Fair Web Analytics

Will your traffic and KPI model tolerate opt-in-only measurement after a pilot on a non-critical property?
Where will you host the instance (EU on-prem/VPS vs US-group cloud), and who holds OFFEN_SECRET and DB backups?
Do procurement rules require third-party audits or ISO/SOC that Offen does not publish?
Do you need a signed vendor DPA as processor, or is controller-only self-host acceptable to counsel?
Is subdomain + CSP (script-src/frame-src + unsafe-inline styles for the banner) feasible on your main site?