JENTIS vs Pirsch Analytics

Comparez JENTIS et Pirsch Analytics sur les capacités, la juridiction, les garanties et l'adéquation pour les acheteurs européens.

Tous deux listés comme alternatives à: Google Analytics

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
Voir la ficheVisiter le site web

Les lignes surlignées diffèrent entre les deux produits.

JENTIS vs Pirsch Analytics: Aperçu
CaractéristiqueLogo: JENTISJENTISLogo: Pirsch AnalyticsPirsch Analytics
Pays d'origineAustriaGermany
CatégorieWeb AnalyticsWeb Analytics
Open sourceNonOui
Auto-hébergéNonNon
SiègeAustriaNon indiqué
Entité légaleJENTIS GmbHNon indiqué
Droit applicableAustria / EU GDPRNon indiqué
Maison mère / contrôle USAucune maison mère US connueNon indiqué
Exposition CLOUD Act (indicative)FaibleNon indiqué
Hébergement / résidenceProduct: 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.Non indiqué
Résumé

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.

Cookie-free web analytics from Emvi Software GmbH in Germany: hash-based visitor IDs, open-source core, Hetzner-hosted SaaS with funnels, events, and agency white-label.

Tags
server-side-trackinggdprtag-managementfirst-party-datamartechaustria
server-side-trackinggdpranalyticsweb-analyticscookie-freeprivacyopen-sourcesaasgermany
En un coup d'œil: JENTIS vs Pirsch Analytics
En un coup d'œilLogo: JENTISJENTISLogo: Pirsch AnalyticsPirsch Analytics
HQVienna, AustriaNon indiqué
Legal entityJENTIS GmbH (FN 529675i)Non indiqué
Founded2020Non indiqué
Product typeManaged server-side data capture / hybrid tag managerNon indiqué
Hosting modelManaged SaaS; EU/EEA by default (IONOS cited in docs)Non indiqué
Open sourceNoNon indiqué
Self-hosted productNo (managed hosting)Non indiqué
Commercial modelSales-led SaaS (demo / consultation)Non indiqué
Key capabilities: JENTIS vs Pirsch Analytics
Key capabilitiesLogo: JENTISJENTISLogo: Pirsch AnalyticsPirsch Analytics
EU-operated (Austria)OuiNon indiqué
Server-side tag managerOuiNon indiqué
EU/EEA hosting (claimed)OuiNon indiqué
ISO 27001 (claimed)OuiNon indiqué
Managed SaaSOuiNon indiqué
Not open sourceOuiNon indiqué

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.

Pirsch Analytics

  • Real-Time Dashboard and Core Metrics

    The intuitive dashboard shows pageviews, unique visitors, bounce rates, sessions, referrers, devices, browsers, operating systems, and locations in real time. Filters let users slice data by time, tags, or events with one click. Saved views and time comparisons speed analysis. Automatic email reports and traffic spike alerts keep teams informed without constant checks. Data exports to CSV provide flexibility.

  • Advanced Analytics Tools

    Beyond basics, Pirsch tracks custom events like button clicks or signups, sets conversion goals, and maps multi-step funnels to spot drop-offs. A/B testing and segmentation use tags for attribution. Session exploration reveals individual paths, including outbound links, downloads, and 404s. Webhooks integrate with other apps. E-commerce revenue tracking and custom event metrics add depth for Plus and Enterprise users.

  • Seamless Integrations and Customization

    Add via JS snippet, server-side API, or plugins for WordPress, Shopify, Webflow, Laravel, Drupal, Framer, React, Vue, Angular, and Go. Import historical data from competitors. White-label with custom domains, themes, logos for agencies. Unlimited members, teams, and data retention. Enterprise offers SAML SSO, raw data access, and on-premise options. All plans include 100% data ownership.

Assurance & compliance: JENTIS vs Pirsch Analytics
Assurance & complianceLogo: JENTISJENTISLogo: Pirsch AnalyticsPirsch Analytics
Independent security / no-logs audit
Not found

No public independent no-logs or third-party security audit PDF located; ISO is the main public assurance claim.

Non indiqué
ISO 27001
Vendor claimed

Vendor states ISO 27001 / ISO 27001:2013 certification on site footer and privacy docs; certificate not independently verified in this draft.

Non indiqué
SOC 2 / SOC 3
Not found

No public SOC 2/3 report found on marketing or privacy docs.

Non indiqué
GDPR / EU data protection
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.

Non indiqué
US CLOUD Act exposure (indicative)
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.

Non indiqué
Data processing agreement (B2B)
Vendor claimed

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

Non indiqué
EU AI Act
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.

Non indiqué
Considerations & known limitations: JENTIS vs Pirsch Analytics
Considerations & known limitationsLogo: JENTISJENTISLogo: Pirsch AnalyticsPirsch Analytics
Consent modes need legal sign-off
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.

Non indiqué
Downstream US ad/analytics tools
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.

Non indiqué
ISO claimed; limited public audits
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.

Non indiqué
Managed SaaS, not self-host
Medium

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

Non indiqué
Implementation and data-layer effort
Low

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

Non indiqué

Adéquation

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.

Pirsch Analytics

Best fit when

Non indiqué

Poor fit when

Non indiqué

Open questions for due diligence

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?

Pirsch Analytics

Non indiqué