etracker vs Matomo by Stackhero

Compare etracker and Matomo by Stackhero 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

Matomo by Stackhero

France· Web Analytics

Needs review

Shortlist when you want full Matomo on a dedicated French-operated bare-metal instance with one-click updates and hourly billing—especially if you prefer unlimited site/seat product framing over hit-metered multi-tenant SaaS. Skip when you need EU-only with no US region option, root/SSH access, or a minimal cookieless counter—consider self-hosted Matomo, Friendly Analytics, or Plausible instead.

Managed MatomoDedicated instanceFrench PaaS operatorISO 27001 (claimed)Automatic DPAEU or US region

View listing Visit Website

Highlighted rows differ between the two products.

etracker vs Matomo by Stackhero: Snapshot
Feature	etracker	Matomo by Stackhero
Country of origin	Germany	France
Category	Web Analytics	Web Analytics
Open source	No	Yes
Self-hosted	No	No
Headquarters	Germany	France
Legal entity	JustRelate Deutschland GmbH (Charlottenburg HRB 218235); product brand JustRelate etracker / etracker	Stackhero (RCS Paris 512 366 378, VAT FR92512366378), 1 rue de Stockholm, 75008 Paris, France
Governing law	Not listed	French law; courts at registered head office (per Terms of service)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Low	Medium
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.	Primary compute: Stackhero bare-metal cloud, customer-chosen region EU (France) or USA. Backups: stored in the EU per Matomo FAQ; encrypted atomic images retained up to ~3 months. Not built on AWS/GCP/Azure as the stated compute substrate. Payment processor (unnamed) handles card data; privacy policy mentions third-party messaging/stats tools without a full named subprocessor table.
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.	French PaaS-managed Matomo on dedicated bare-metal instances: unlimited sites until capacity, one-click updates, EU or US region choice, with hourly billing and an automatic DPA.
Tags	analytics privacy gdpr saas cookieless marketing-analytics consent-management e-commerce	analytics privacy gdpr saas matomo open-source france managed-hosting iso-27001

At a glance: etracker vs Matomo by Stackhero
At a glance	etracker	Matomo by Stackhero
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	Hourly instance billing; free trial; no standard commitment
HQ	Not listed	Paris, France (1 rue de Stockholm, 75008)
Legal entity	Not listed	Stackhero — RCS Paris 512 366 378
Stack	Not listed	Open-source Matomo on dedicated Stackhero VM
Hosting regions	Not listed	EU (France) or USA; backups in EU (vendor FAQ)
Certifications	Not listed	ISO 27001:2022 claimed (BAB #254338)

Key capabilities: etracker vs Matomo by Stackhero
Key capabilities	etracker	Matomo by Stackhero
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
Managed Matomo	Not listed	Yes
Dedicated instance	Not listed	Yes
French PaaS operator	Not listed	Yes
ISO 27001 (claimed)	Not listed	Yes
Automatic DPA	Not listed	Yes
EU or US region	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.

Matomo by Stackhero

Dedicated bare-metal Matomo instance
Each customer gets an isolated VM on Stackhero’s own bare-metal cloud (Stackhero DC OS), not shared multi-tenant Matomo. Local disks and included Redis are positioned for high IOPS and heavy traffic—fit teams that outgrow noisy-neighbor shared analytics clouds.
Unlimited sites, members, segments, and goals until capacity
Stackhero does not meter websites, team seats, segments, or goals as product SKUs; you scale by instance size (published up to 16 vCPUs / 64 GB RAM). Retention is limited by disk, not a fixed product TTL—plan storage for long history.
One-click Matomo updates and managed ops (no SSH)
Stackhero delivers Matomo updates for dashboard application; firewall IP rules are customer-configurable. SSH is intentionally unavailable on the managed service—good for reduced surface area, poor fit if you need custom OS packages.
Custom domain, GeoIP2, and dedicated notification email
Point matomo.yourdomain.com with TLS 1.3/ECDSA, ship visitor location via bundled GeoIP2, and send unlimited Matomo reports/alerts through a per-instance email path—reduces glue work after first deploy.
Atomic encrypted daily backups (EU vault)
24-hour atomic image backups (plus event-driven backups on upgrades) are validated, then encrypted (OpenPGP ECDH/Curve25519) and retained up to three months. Vendor FAQ states backups are stored in the EU even when regions differ—confirm dual-region implications for US instances.
Hourly billing with EU or US region choice
Spin services up/down with hourly charging and a single monthly invoice; free trial without payment method. Choose European (France) or USA placement at create time—region is a first-class control for residency, not a hidden default.

Assurance & compliance: etracker vs Matomo by Stackhero
Assurance & compliance	etracker	Matomo by Stackhero
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 ISO 27001 and bug-bounty openness claimed; no public independent no-logs audit report specific to analytics found.
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.	Vendor claimed Vendor publishes ISO/IEC 27001:2022 certificate #254338 from the British Assessment Bureau (PDF). Not re-verified against the issuer’s public register in this draft.
SOC 2 / SOC 3	Not found No public SOC 2/SOC 3 report located on official trust/security pages reviewed.	Not found No SOC 2/3 claim found on certifications/privacy/GDPR pages reviewed.
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 French entity; public GDPR & DPA page; customer controller / Stackhero processor model; EU region option for service data.
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 French entity, no known US parent, non-hyperscaler bare-metal hosting claimed. Medium/partial because USA is a first-class hosting region; EU-only only when the customer creates the service in Europe. Backups stated as EU-stored. 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.	Vendor claimed DPA applies automatically with Terms of service; PDF downloadable from the GDPR & DPA page.
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 hosting; not positioned as an AI system product.

Considerations & known limitations: etracker vs Matomo by Stackhero
Considerations & known limitations	etracker	Matomo by Stackhero
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.	Not listed
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
Optional US hosting region	Not listed	Medium Platform offers USA placement alongside France/EU. Mis-selected region or unclear contract language can put visitor analytics outside the EU. Procurements that require EU-only must pin region at create time and in the order form.
EU backups when primary is US	Not listed	Medium FAQ states backups are stored in the EU. If an instance runs in the USA, confirm whether visitor data is dual-homed (US primary + EU backup) and how that affects DPIA and transfer tools.
No SSH / managed-only host	Not listed	Low Cannot install arbitrary system software or agents; support hours stated as CET office hours for basic platform support—not full Matomo application consulting.
Limited named subprocessor list	Not listed	Medium Privacy policy mentions third-party tools and a payment processor without a detailed public subprocessor register. Request the annex in diligence if procurement requires named processors.
ISO certificate vendor-published	Not listed	Low ISO 27001:2022 is claimed with a public PDF and BAB certificate number; validate scope, sites, and validity dates with the certification body before treating it as verified.
Matomo privacy configuration is yours	Not listed	Low Hosting in the EU does not auto-configure consent, IP anonymization, or cookieless modes. Controllers remain responsible for Matomo GDPR tooling and site policy.

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

Matomo by Stackhero

Best fit when

Teams that want Matomo’s full analytics/admin surface without running OS or Matomo upgrades themselves
Buyers who prefer a dedicated VM and capacity-based limits over multi-tenant hit metering
Orgs consolidating Matomo with other Stackhero-managed open-source services under one French operator
Projects that need hourly elasticity and the ability to stop billing with one click
Controllers who will configure Matomo privacy features themselves and want a signed/automatic DPA plus ISO 27001 claims

Poor fit when

Requirements that forbid any US hosting option or dual-region backup stories—platform publicly offers USA regions
Teams that need SSH, custom kernels, or non-Matomo system agents on the host
Buyers seeking only a lightweight cookieless pageview product (Plausible-class tools are simpler)
Organizations that must self-host inside their own cloud account with no third-party PaaS operator
Use cases needing a named public subprocessor register beyond Stackhero’s high-level privacy/GDPR pages

Consider instead when

When: You want Swiss Matomo-as-a-Service with cookieless defaults and CH product hosts
Consider: Friendly Analytics
Different operator, residency story, and privacy defaults; still Matomo-based.
When: You need enterprise analytics packaging beyond plain managed Matomo
Consider: Piwik PRO
Compare modules, contracts, and hosting regions independently.
When: You only need a minimal open-source-friendly counter with simple SaaS UX
Consider: Plausible Analytics
Far less Matomo depth; different product surface.
When: You require full root control and in-house residency guarantees
Consider: Self-hosted Matomo on your own EU IaaS
Maximum control; you own updates, backups, and hardening.

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?

Matomo by Stackhero

Will the order form and DPA annex permanently pin the Matomo instance to the EU (France) region with no US failover?
For US-region instances, what exact data is copied to EU backup vaults and under which transfer mechanism?
Who is the unnamed parent company referenced on the About page, and is there any US ownership or PE?
Can ISO 27001 certificate 254338 be validated on the British Assessment Bureau (or successor) public register for current scope/dates?
Which payment, support, and website analytics providers process Stackhero account data (named subprocessor list)?