Insights vs JENTIS

Vergleichen Sie Insights und JENTIS nach Funktionen, Rechtsraum, Nachweisen und Einsatzpassung.

Beide als Alternativen zu: 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
Insights vs JENTIS: Überblick
MerkmalLogo: InsightsInsightsLogo: JENTISJENTIS
HerkunftslandAustriaAustria
KategorieWeb AnalyticsWeb Analytics
Open SourceJaNein
Self-HostedNeinNein
HauptsitzNicht angegebenAustria
RechtsträgerNicht angegebenJENTIS GmbH
Anwendbares RechtNicht angegebenAustria / EU GDPR
US-Mutter / KontrolleNicht angegebenKeine bekannte US-Mutter
CLOUD-Act-Exposition (indikativ)Nicht angegebenNiedrig
Hosting / ResidenzNicht angegebenProduct: 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.
Zusammenfassung

Austrian privacy-first hosted web analytics: page views and custom events without cookies or stored visitor IPs, with an MIT open-source JS client (backend uses Google Firebase).

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
Auf einen Blick: Insights vs JENTIS
Auf einen BlickLogo: InsightsInsightsLogo: JENTISJENTIS
HQNicht angegebenVienna, Austria
Legal entityNicht angegebenJENTIS GmbH (FN 529675i)
FoundedNicht angegeben2020
Product typeNicht angegebenManaged server-side data capture / hybrid tag manager
Hosting modelNicht angegebenManaged SaaS; EU/EEA by default (IONOS cited in docs)
Open sourceNicht angegebenNo
Self-hosted productNicht angegebenNo (managed hosting)
Commercial modelNicht angegebenSales-led SaaS (demo / consultation)
Key capabilities: Insights vs JENTIS
Key capabilitiesLogo: InsightsInsightsLogo: JENTISJENTIS
EU-operated (Austria)Nicht angegebenJa
Server-side tag managerNicht angegebenJa
EU/EEA hosting (claimed)Nicht angegebenJa
ISO 27001 (claimed)Nicht angegebenJa
Managed SaaSNicht angegebenJa
Not open sourceNicht angegebenJa

Insights

  • Cookie-Free Tracking

    Insights requires no cookies, eliminating the need for intrusive consent banners that can deter up to 20% of visitors from engaging further. Page views log automatically, capturing basics like visit duration and exit pages, all anonymized. This keeps sites faster and user-friendly while providing actionable data. (62 words)

  • Custom Event and User Flow Tracking

    Developers can track interactions precisely: form submissions, video plays, scrolls past thresholds. The Insights.js library enables flexible event payloads, building detailed user journeys. Unlike basic privacy tools, it handles complex web apps, showing sequences from landing to conversion without personal identifiers. Documentation includes code samples for common setups. (68 words)

  • Built-In GDPR Compliance

    No IP storage, no personal data retention—Insights sidesteps common pitfalls that led to fines against Google Analytics users. It complies with GDPR, CCPA and PECR out of the box. Transparency reports detail exact data points collected, and Firebase sub-processors handle only anonymized loads. European hosting via Austrian firm ensures data stays in compliant jurisdictions. (72 words)

  • Lightweight and Transparent Code

    The script loads under 10KB gzipped, outperforming bulkier rivals. Full event tracking remains performant even on low-end devices. Source code for the client-side tracker is public on GitHub, allowing audits. Pricing transparency matches: flat monthly rates based on event volume, cancellable anytime without overages. (58 words)

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: Insights vs JENTIS
Assurance & complianceLogo: InsightsInsightsLogo: JENTISJENTIS
Independent security / no-logs auditNicht angegeben
Not found

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

ISO 27001Nicht angegeben
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 3Nicht angegeben
Not found

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

GDPR / EU data protectionNicht angegeben
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)Nicht angegeben
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)Nicht angegeben
Vendor claimed

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

EU AI ActNicht angegeben
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: Insights vs JENTIS
Considerations & known limitationsLogo: InsightsInsightsLogo: JENTISJENTIS
Consent modes need legal sign-offNicht angegeben
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 toolsNicht angegeben
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 auditsNicht angegeben
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-hostNicht angegeben
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 effortNicht angegeben
Low

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

Passung

Insights

Best fit when

Nicht angegeben

Poor fit when

Nicht angegeben

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

Insights

Nicht angegeben

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?