etracker vs JENTIS

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

Both listed as alternatives to: Google Analytics

Logo: etracker

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)
Logo: JENTIS

JENTIS

Austria· Web Analytics

Needs review

Shortlist when you need managed server-side / first-party capture with EU-entity hosting and multi-destination activation (ads + analytics). Skip when you only want lightweight privacy analytics or free self-hosted tagging—consider Piwik PRO or etracker for EU analytics-first stacks, or Google sGTM if you will operate a Google-centric pipeline yourself.

EU-operated (Austria)Server-side tag managerEU/EEA hosting (claimed)ISO 27001 (claimed)Managed SaaSNot open source
etracker vs JENTIS: Snapshot
FeatureLogo: etrackeretrackerLogo: JENTISJENTIS
Country of originGermanyAustria
CategoryWeb AnalyticsWeb Analytics
Open sourceNoNo
Self-hostedNoNo
HeadquartersGermanyAustria
Legal entityJustRelate Deutschland GmbH (Charlottenburg HRB 218235); product brand JustRelate etracker / etrackerJENTIS GmbH
Governing lawNot listedAustria / EU GDPR
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)LowLow
Hosting / residencyPrimary 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: default EU/EEA-only processing on ISO 27001-certified cloud; docs cite IONOS cloud (Germany/EU). Exact host/region named in customer DPA. Optional non-EU instances may add non-EU subprocessors if selected. Marketing website separately uses Host Europe (DE) and US SaaS (HubSpot, Salesforce, Google) for corporate CRM/ads—not the Twin Server product path.
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.

Austrian managed server-side data capture and hybrid tag manager: first-party Twin Server collection, consent-aware routing, and ad activation for multi-tool MarTech stacks.

Tags
At a glance: etracker vs JENTIS
At a glanceLogo: etrackeretrackerLogo: JENTISJENTIS
HQ / legal entityJustRelate Deutschland GmbH, Berlin (product ops Hamburg)Not listed
Product typeWeb & marketing analytics SaaS (+ tag/CMP modules)Managed server-side data capture / hybrid tag manager
HostingOwn servers, IPHH housing, Hamburg/GermanyNot listed
Open sourceNoNo
Self-hostedNoNot listed
Commercial modelUsage-based SaaS licence (hit tiers); trial commonly offeredSales-led SaaS (demo / consultation)
HQNot listedVienna, Austria
Legal entityNot listedJENTIS GmbH (FN 529675i)
FoundedNot listed2020
Hosting modelNot listedManaged SaaS; EU/EEA by default (IONOS cited in docs)
Self-hosted productNot listedNo (managed hosting)
Key capabilities: etracker vs JENTIS
Key capabilitiesLogo: etrackeretrackerLogo: JENTISJENTIS
Cookieless default trackingYesNot listed
EU/DE hosted (IPHH)YesNot listed
ePrivacyseal (claimed)YesNot listed
Tag + consent suiteYesNot listed
Ad conversion syncYesNot listed
SaaS only (not self-host)YesNot listed
EU-operated (Austria)Not listedYes
Server-side tag managerNot listedYes
EU/EEA hosting (claimed)Not listedYes
ISO 27001 (claimed)Not listedYes
Managed SaaSNot listedYes
Not open sourceNot listedYes

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.

JENTIS

  • Hybrid server-side tag management

    One container for client- and server-side tags with first-party DNS; migrate data-layer logic and debug from browser hit to server dispatch without running your own sGTM fleet.

  • Twin Server capture and transforms

    Server-side session mirror that can pseudonymize, anonymize, enrich, and time-frame parameters before forwarding—usable as a CNIL-style proxy pattern when configured carefully.

  • Essential Mode for non-consent traffic

    Configurable minimized/anonymized capture when marketing consent is refused so sessions and conversions are not fully invisible—subject to DPO/legal sign-off per jurisdiction.

  • Synthetic Users for ad activation

    Models trained on consented first-party data produce synthetic conversion signals for Google, Meta, TikTok, and other ad APIs; measure impact with holdouts—legal basis is configuration-specific.

  • Managed EU connectors and raw export

    Vendor-maintained connectors across analytics, ads, and MarTech plus raw data export/API-style control; not a self-hosted open-source stack.

Assurance & compliance: etracker vs JENTIS
Assurance & complianceLogo: etrackeretrackerLogo: JENTISJENTIS
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 independent no-logs or third-party security audit PDF located; ISO is the main public assurance claim.

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 states ISO 27001 / ISO 27001:2013 certification on site footer and privacy docs; certificate not independently verified 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 public SOC 2/3 report found on marketing or privacy docs.

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

Austrian controller entity; product marketed as privacy-by-design processor with EU hosting, CMP hooks, and transform functions. Not legal advice—confirm config and 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

EuropeanStack assessment: AT entity and no known US parent; product hosting claimed EU-only (e.g. IONOS). Residual exposure via customer-chosen US destinations and any non-EU instance option. 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

Sample DPA via Customer Legal Hub; required for SaaS processing. Confirm signed version and subprocessor annex.

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

Core product is tag/data capture; Synthetic Users is ML-assisted but product is not marketed as a general-purpose AI system. Revisit if Synthetic Users becomes a primary regulated AI offering.

Considerations & known limitations: etracker vs JENTIS
Considerations & known limitationsLogo: etrackeretrackerLogo: JENTISJENTIS
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
Consent modes need legal sign-offNot listed
High

Essential Mode and Synthetic Users can re-open measurement when users refuse cookies; legality depends on jurisdiction, configuration, and DPO assessment—not automatic compliance.

Downstream US ad/analytics toolsNot listed
Medium

Even with EU capture, enabling Google/Meta/TikTok connectors can transfer personal data to US providers; use transforms/proxy patterns and transfer tools as required.

ISO claimed; limited public auditsNot listed
Medium

ISO 27001 is vendor-asserted; no independent public security/no-logs audit found. Request certificate, pen-test summaries, and full subprocessor list under NDA if needed.

Managed SaaS, not self-hostNot listed
Medium

No open-source self-host product path; ops simplicity trades for vendor dependency, sales-led pricing, and migration cost if you later leave.

Implementation and data-layer effortNot listed
Low

Migration from client-side tags still needs DNS, data layer, CMP mapping, and QA—vendor connectors reduce but do not eliminate engineering work.

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

JENTIS

Best fit when

  • E-commerce and multi-brand sites that lose conversion data to blockers, ITP, and consent drop-off
  • Performance marketing teams activating into Google, Meta, TikTok, and other ad APIs from first-party events
  • Analytics/DPO pairs that need data-point-level governance, CMP sync, and pseudonymization before third-country tools
  • Organizations preferring a managed EU capture layer over self-operated server-side GTM
  • Stacks that feed both EU analytics (e.g. Piwik PRO) and global ad platforms from one collection path

Poor fit when

  • Teams seeking free, open-source, or fully self-hosted analytics only
  • Lightweight privacy page analytics without ad activation or hybrid tag management
  • Buyers who cannot run sales-led procurement, data-layer work, and legal review of consent modes
  • Use cases that need a full CDP/BI product rather than capture and routing

Consider instead when

  • When: You primarily need EU privacy-focused web analytics (and optional self-host), not multi-destination ad activation

    Consider: Piwik PRO or etracker

    JENTIS can still sit in front of Piwik PRO; choose the analytics product when capture is not the bottleneck.

  • When: You are Google-only and will operate server-side GTM yourself

    Consider: Google Tag Manager (server-side) + GA4

    Lower cash cost; higher ops burden and different transfer/jurisdiction posture.

  • When: You need a full customer data platform or enterprise analytics suite

    Consider: Adobe Analytics or a dedicated CDP (e.g. Tealium)

    JENTIS is capture/routing at the start of the chain, not a CDP replacement.

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?

JENTIS

  • What is the exact production cloud provider, region, and subprocessor list on the current DPA annex?
  • Can the vendor produce a current ISO 27001 certificate and any independent penetration-test summary?
  • Has legal counsel approved Essential Mode and Synthetic Users for your markets (ePrivacy/GDPR basis)?
  • Which destinations will receive personal data vs pseudonymized/synthetic signals only?
  • What SLA, raw data retention, and exit/export terms apply to your tier?