Logo: JENTIS

JENTIS

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.

JENTIS is a managed server-side data capture platform (a hybrid tag manager) from JENTIS GmbH in Vienna. Sites load a first-party script and route events through JENTIS Twin Server, which can clean, pseudonymize, enrich, and forward events to analytics and ad destinations.

It exists for marketing and privacy teams that want first-party measurement without firing dozens of third-party browser tags, and without running their own server-side GTM stack. The company documents EU/EEA processing by default.

The concrete differentiator is Twin Server plus consent-era tools: Essential Mode for minimized capture when marketing consent is refused, and Synthetic Users for reconstructing non-consented conversion signals as activatable inputs. It is SaaS with managed EU hosting, not a self-serve analytics suite.

EU-operated (Austria)Server-side tag managerEU/EEA hosting (claimed)ISO 27001 (claimed)Managed SaaSNot open source

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.

Key capabilities

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.

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.

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.

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.

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

In één oogopslag

HQ
Vienna, Austria
Legal entity
JENTIS GmbH (FN 529675i)
Founded
2020
Product type
Managed server-side data capture / hybrid tag manager
Hosting model
Managed SaaS; EU/EEA by default (IONOS cited in docs)
Open source
No
Self-hosted product
No (managed hosting)
Commercial model
Sales-led SaaS (demo / consultation)

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.

Jurisdictie & eigendom

Juridische entiteit
JENTIS GmbH
Toepasselijk recht
Austria / EU GDPR
VS-moeder / zeggenschap
Geen bekende VS-moeder
CLOUD Act-blootstelling (indicatief)
Low
Hosting / residentie
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.

Indicative only—not legal advice. No US parent known from imprint. Destination tools (GA, Meta, etc.) can still create US transfers when you enable those connectors.

  • Independent security / no-logs auditNot found
  • ISO 27001Vendor claimed
  • SOC 2 / SOC 3Not found
  • GDPR / EU data protectionVendor claimed
  • +3

Considerations & known limitations

  • HighConsent modes need legal sign-off

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

  • MediumDownstream US ad/analytics tools

    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.

  • MediumISO claimed; limited public audits

    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.

  • MediumManaged SaaS, not self-host

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

  • LowImplementation and data-layer effort

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

Open questions for due diligence

  • 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?

Veelgestelde Vragen

Primarily a data capture and tag-management layer: collect, govern, and route first-party events into tools you already use (GA4, Piwik PRO, Meta CAPI, etc.). It is not a substitute for a full BI or CDP product, though it can improve the quality of data those systems receive.

JENTIS docs state EU/EEA-only processing by default on ISO 27001-certified cloud providers; the DPA names the host and location. Public CNIL proxy docs cite IONOS cloud (Germany/EU). Confirm the current host in your contract—do not assume multi-region US processing for the default product path.

Essential Mode controls what minimized/anonymized data may still be collected when consent is denied. Synthetic Users builds modeled, activatable conversion signals for ad platforms from consented training data. Both need legal review; neither is a free pass to ignore ePrivacy/GDPR consent rules.

Often positioned as a managed alternative to self-operated server-side GTM: hybrid tagging, maintained connectors, EU entity/hosting story, and privacy transforms. Teams deep in Google-only stacks may still prefer sGTM for cost and native tooling; multi-destination and EU-procurement buyers are the clearer shortlist case.

The commercial product is managed SaaS hosting (explicitly marketed against self-hosting operational burden). It is not presented as open-source self-host analytics. Implementation still requires your DNS/first-party setup and typically sales-led onboarding.

Pricing is sales-led / usage- and setup-dependent (demo and consultation path on the site). There is no durable public free tier comparable to client-side GTM. Expect DPA, SLA, and configuration services in enterprise deals—confirm current terms with the vendor.