etracker vs Stormly

Compare etracker and Stormly on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics

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

Stormly

Netherlands· Web Analytics

Needs review

Shortlist Stormly when you need Dutch-contracted, e-commerce-first product analytics: SKU-aware report packs, Shopify/Adobe-oriented setup, inbox-style AI anomaly narratives, and a public DPA. Skip when you need cookieless privacy web stats only (consider Plausible, Simple Analytics, or Pirsch), open-source self-hosting, verified ISO/SOC on a public cert page, or a subprocessor chain free of US-group cloud and Azure OpenAI.

E-commerce product analyticsSKU-aware reportsAI anomaly insightsShopify / Adobe CommerceNL entity + public DPASaaS (not self-host)

View listing Visit Website

Highlighted rows differ between the two products.

etracker vs Stormly: Snapshot
Feature	etracker	Stormly
Country of origin	Germany	Netherlands
Category	Web Analytics	Web Analytics
Open source	No	No
Self-hosted	No	No
Headquarters	Germany	Netherlands
Legal entity	JustRelate Deutschland GmbH (Charlottenburg HRB 218235); product brand JustRelate etracker / etracker	Monon B.V. (Lutmastraat 1-3, 1072 JL Amsterdam; KvK 76248747 per Terms)
Governing law	Not listed	Netherlands (Dutch law; Amsterdam courts)
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.	Client analytics subprocessors (Security Architecture): Hetzner (EU); Amazon AWS (US company, vendor states EU regions only for encrypted analytics backups); Vultr (US company); Microsoft Azure OpenAI (US company, vendor states EU Azure region). Plans market EU data residency. Controller privacy policy also references Vultr/AWS for account data, AuthSMTP EU + Amazon SES USA for email, Stripe for payments; marketing site uses Google Analytics and Hotjar.
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.	Dutch SaaS product analytics for e-commerce teams: SKU-aware reports, AI-assisted anomaly and root-cause insights, and Shopify/Adobe Commerce/Segment/GTM-oriented connections under Monon B.V. (Amsterdam).
Tags	analytics gdpr e-commerce cookieless privacy marketing-analytics saas consent-management	analytics gdpr e-commerce product-analytics ai shopify

At a glance: etracker vs Stormly
At a glance	etracker	Stormly
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	No
Self-hosted	No	Not listed
Commercial model	Usage-based SaaS licence (hit tiers); trial commonly offered	Free tier + monthly plan + custom; trial path on paid
HQ / entity	Not listed	Monon B.V., Amsterdam, Netherlands
Category	Not listed	E-commerce product analytics (SaaS)
Hosting (public)	Not listed	Hetzner; AWS EU-region backups; Vultr; Azure OpenAI EU region (vendor docs)
Self-host	Not listed	No
Governing law	Not listed	Dutch law; Amsterdam courts

Key capabilities: etracker vs Stormly
Key capabilities	etracker	Stormly
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	Yes
E-commerce product analytics	Not listed	Yes
SKU-aware reports	Not listed	Yes
AI anomaly insights	Not listed	Yes
Shopify / Adobe Commerce	Not listed	Yes
NL entity + public DPA	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.

Stormly

AI agent for trends, anomalies, and root-cause style digs
Stormly positions an AI agent that watches connected e-commerce data for trends and anomalies (for example conversion drops or product spikes), then delivers plain-language findings—often to the inbox—with root-cause style exploration for questions like mobile conversion drops or regional return spikes. AI assistant access is plan-dependent; the public DPA documents Azure OpenAI (Microsoft) handling of assistant queries with a 30-day retention window and property stripping rules. Best for merchandising and growth leads who want narrative answers without waiting on a data team.
SKU-aware e-commerce report library (plus custom builds)
Ready reports target commerce questions: New Arrivals Performance (early SKU winners/laggards), Unviewed & Unsold Products, cart abandonment and revenue contribution by product/category, Conversion Journey and funnels by device/region, A/B test insights, Aha Moment Discovery, cross-selling analysis, and broader library items (retention, CLV, forecasting, SQL report, and more). Vendor materials state custom reports are included without a separate fee when a needed view is missing—useful for mid-market retailers that outgrow generic event charts.
Shopify, Adobe Commerce, Segment, and GTM-oriented connections
Homepage setup emphasizes linking Shopify, Adobe Commerce, or Segment quickly, with Google Tag Manager also listed among integrations. The DPA describes additional programmatic paths (JS library, import, custom endpoints, third-party sources). Fits stores already on common commerce stacks; teams on exotic storefronts should validate event coverage and product-feed depth in a pilot before replacing an existing analytics stack.
End-user tracking with IP anonymization defaults
Per the DPA, IP addresses for end-user analytics are not stored in full: the last octet is removed and geo/timezone are derived from the anonymized value. Web integrations automatically capture first-party cookie user ids, page/referrer/UTM context, and device metadata; app properties depend on client or CDP configuration. This is still full product analytics (not cookieless aggregate-only web stats)—clients remain responsible for consent banners and lawful basis for shopper tracking.
Public DPA, security architecture, and Dutch contracting
B2B buyers can download a Data Processing Agreement (effective 2023-09-06) and a Security Architecture page listing subprocessors, encryption expectations, backup retention (analytics backups up to six months), and logical tenant isolation. Contracts and DPA are governed by Dutch law with Amsterdam courts. Useful for EU procurement packages—but US-group subprocessors (AWS, Vultr, Azure OpenAI) still require transfer and CLOUD Act diligence.

Assurance & compliance: etracker vs Stormly
Assurance & compliance	etracker	Stormly
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 Security Architecture describes encryption, monitoring, isolation, and vulnerability contact (security@stormly.com); no public third-party audit PDF 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.	Not found No public ISO 27001 certificate located on official legal/security pages reviewed.
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 located on official 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 NL entity; public privacy policy and DPA (GDPR-oriented); IP last-octet anonymization for end-user analytics; SCCs language for restricted transfers in DPA.
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 EU entity / no known US parent, but public client subprocessors include AWS, Vultr, and Microsoft Azure OpenAI (US-group companies). Account path historically also lists Amazon SES and Stripe. Residency claims do not remove US-group legal exposure. Indicative only—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 Downloadable DPA PDF linked from stormly.com/dpa (effective 6 September 2023); audit rights and subprocessor notice described; Security Architecture lists subprocessors.
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.	Partial Product includes an AI assistant via Azure OpenAI; not positioned as a high-risk AI system marketing claim. Buyers should map AI assistant use to their own AI Act / internal AI policy—vendor does not publish a full AI Act conformity package on the pages reviewed.

Considerations & known limitations: etracker vs Stormly
Considerations & known limitations	etracker	Stormly
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.	Medium Enterprise security questionnaires may stall without ISO 27001/SOC 2 packs. DPA offers information/audit rights—plan time for NDA evidence requests.
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
US-group cloud and AI subprocessors	Not listed	Medium Despite Dutch HQ and EU residency marketing, client data paths publicly include AWS, Vultr, and Microsoft Azure OpenAI. Transfer tooling (SCCs) and encryption of backups are documented, but CLOUD Act / US legal process risk remains a diligence item for sovereignty-sensitive buyers.
Azure OpenAI retains assistant context 30 days	Not listed	Medium AI queries and aggregate report results are stored on Microsoft Azure OpenAI for 30 days per DPA. Property stripping reduces some identifiers, but misconfigured event properties could still expose sensitive content—govern AI use and property hygiene.
Controller privacy policy vs security architecture drift	Not listed	Low Privacy policy (controller, effective 2019) still emphasizes Vultr USA wording in places, while Security Architecture (client data) lists Hetzner/AWS/Vultr/Azure. Ask for a single current subprocessor and region matrix at contract time.
Not a privacy web-analytics substitute	Not listed	Low Full product analytics with cookies/identifiers for web integrations—not a cookieless aggregate counter. Consent UX remains on the client.

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

Stormly

Best fit when

Merchandising, product, UX, and growth teams on Shopify or Adobe Commerce who need SKU, cart, and assortment analytics without a dedicated data science org
Retail brands that want ready e-commerce report templates (new arrivals, unviewed/unsold, funnels, A/B, aha moments) plus vendor-built custom reports
EU buyers who want a Dutch legal entity, Amsterdam courts, and a downloadable DPA/Security Architecture package
Teams that value AI-generated trend/anomaly narratives delivered to the inbox more than building every chart from a blank event schema
Stacks already using Segment or Google Tag Manager as the event pipe into analytics

Poor fit when

Publishers or marketing sites that only need lightweight privacy-friendly page analytics (not product/SKU depth)
Orgs that require open-source self-hosting or full control of a private analytics warehouse as the default
Procurement policies that forbid US-group subprocessors (AWS, Vultr, Microsoft Azure OpenAI) even when EU regions are claimed
Assurance programs that require public ISO 27001/SOC 2 evidence before pilot (not found on vendor pages reviewed)
Companies operating blockchain products/services—restricted by Stormly’s terms

Consider instead when

When: You only need privacy-oriented website metrics (pageviews, sources) rather than SKU-level product analytics
Consider: Plausible Analytics, Simple Analytics, or Pirsch Analytics
EU web-analytics peers; different category from e-commerce product analytics
When: You need deep general-purpose product analytics, large ecosystem, and mature multi-product SaaS event modeling
Consider: Mixpanel or Amplitude
US incumbents; stronger breadth, different jurisdiction and commercial model
When: You primarily need free/universal marketing acquisition reporting already embedded in the stack
Consider: Google Analytics (incumbent) or dual-run GA for marketing + Stormly for product/merch
GA is not SKU-first product analytics; Stormly is not a GA replacement for every report

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?

Stormly

Can Stormly provide a current region map (which data classes live on Hetzner vs Vultr vs AWS) under NDA for our DPIA?
Are ISO 27001, SOC 2, or penetration-test summaries available on request for enterprise security review?
Which event properties from our Shopify/Adobe feed are excluded from Azure OpenAI prompts by default in our tenant?
Do custom report builds and SQL access sit only on the custom tier, and what SLAs apply?
Has the 2019 controller privacy policy been superseded for hosting wording relative to the Security Architecture list?