Migrating from client-side or legacy tracking to JENTIS is simple: our experts help you replace browser scripts with server-side data flows, ensuring fast setup with minimal IT effort. This delivers 100% accurate, privacy-compliant data across your stack, unaffected by blockers or consent gaps, enabling better decisions and higher ROAS.

How do I debug and troubleshoot?

Debugging with JENTIS is done directly in the platform’s preview and debug monitor, where you can inspect events, tags, and data flows in real time. This ensures fast error detection and correction, reducing downtime and guaranteeing high data quality.

Does JENTIS store raw data?

No, the customer processes data within their own JENTIS server environment; JENTIS provides the infrastructure and privacy-by-design features (like Essential Mode and Synthetic Users) to pseudonymize and securely handle data without storing it themselves.

How is data routed server-side?

Events are collected via the customer’s own first-party domain, processed in their dedicated JENTIS server environment (under the customer’s control), and then pseudonymized before being forwarded to chosen analytics and marketing tools.

How do tools and tags map in JENTIS?

Existing client-side tags are mirrored in JENTIS through its Data Layer Bridge, and tools (e.g., GA4, Meta, Google Ads) are configured server-side with ready-made or custom connectors. This ensures fast migration, automated tag setup, and precise, compliant data delivery to every platform.

Can I run Google Analytics 4 fully server-side with JENTIS?

JENTIS enables a 100% server-side GA4 setup, eliminating client-side dependencies, ensuring GDPR compliance, and delivering maximum data accuracy unaffected by blockers or browser restrictions.

Can I create region-specific tool instances (e.g., GA4 EU vs US)?

Yes, JENTIS lets you configure multiple instances of the same tool (like GA4) and route data region-specifically, giving you full flexibility to meet local compliance and business requirements.

‍

Will JENTIS improve my page speed?

Yes, by shifting heavy tracking scripts from the browser to the server, JENTIS reduces client-side load, improving website performance while still delivering complete and accurate data.

Where is my users’ data processed and stored?

All user data is processed on your own first-party domain and handled within your dedicated EU-based JENTIS server environment, ensuring GDPR compliance and full customer control.

‍

Does JENTIS provide SSO and which providers are supported?

Yes, JENTIS supports Single Sign-On (SSO) for Enterprise customers via SAML with major identity providers including Okta, Microsoft Azure AD, and Ping Identity. This allows organizations to manage users centrally and enforce their existing security and compliance standards.

‍

What happens if one of my downstream tools (e.g., GA) is unavailable?

If a downstream tool is temporarily down, JENTIS continues to capture all data on your server and forwards it once the tool is available again—ensuring no data loss and uninterrupted accuracy across your stack.

Does JENTIS support mobile app tracking?

Yes, JENTIS offers a lightweight App SDK for iOS and Android, enabling you to capture app events server-side with full consent handling, offline tracking, and direct integrations into your analytics and marketing tools. This replaces multiple SDKs with a single privacy-compliant solution while keeping data quality and performance high.

Does JENTIS integrate with my Consent Management Platform (CMP)?

Yes, JENTIS connects seamlessly with CMPs like OneTrust or Usercentrics and automatically adjusts tracking to each user’s consent choice. This guarantees GDPR compliance while still activating all legally permitted data.

Which integrations are available in JENTIS?

JENTIS offers 150+ native connectors across analytics, advertising, and martech platforms, including GA4, Meta, TikTok, Adobe, and many more. Custom connectors are also supported, ensuring real-time, accurate data delivery to any tool in your stack.

Can JENTIS run without non-essential cookies?

Yes, with Essential Mode, JENTIS operates fully without setting non-essential cookies, ensuring compliance while still capturing the maximum legally allowed data.

Which cookies does JENTIS set?

JENTIS only sets a few first-party cookies to ensure accurate tracking:

jts-rw (User-ID, 2 years)
jctr_sid (Session-ID, 30 minutes)
jts_log, jts_preview_version, jts_debug (debugging, only in preview mode)

In addition, JENTIS may use local/session storage for consent data and tracking states. No third-party cookies are ever set by JENTIS.

Does JENTIS support CNIL’s proxy requirements for tools like Google Analytics?

Yes, JENTIS fully supports the CNIL-recommended proxy setup. With the Twin Server and Essential Mode, JENTIS ensures that no full IP addresses are sent to Google, client/user IDs are replaced, referrers and tracking parameters can be removed, and browser/device information is pseudonymized—meeting CNIL’s proxy criteria for GA.

How does JENTIS help with GDPR and ePrivacy compliance?

JENTIS is built on Privacy by Design, processing all data in the customer’s EU-based first-party environment. Features like Essential Mode and Synthetic Users ensure you only capture legally permitted data without consent, while still maintaining high data quality for analytics and marketing.

What are Synthetic Users and how do they work?

Synthetic Users are AI-generated datasets that replace missing conversion data from non-consenting users. JENTIS models behavior based on consenting users’ data and privacy-safe predictors (like session length or browser type), then creates pseudonymized “synthetic” profiles that ad platforms like Google Ads can use to optimize bidding—boosting ROAS while staying GDPR-compliant.

What is Essential Mode and when should I use it?

Essential Mode lets you capture strictly necessary, anonymized data even without user consent, ensuring GDPR/ePrivacy compliance while avoiding blind spots in analytics. You should use it when consent rates are low or when you need a complete, unbiased view of your traffic for better marketing and attribution.

What is the Twin Server technology?

The JENTIS Twin Server mirrors the user’s browser session on a secure EU-based server, where data is cleaned, pseudonymized, and enriched before being sent to third-party tools. This proxy approach blocks direct data transfer (e.g., IPs, client IDs) to vendors, fulfills CNIL’s proxy requirements, and ensures GDPR-compliant server-side tracking.

How is server-side tracking different from client-side tracking?

In client-side tracking, scripts run in the browser, making data collection vulnerable to blockers, consent gaps, and performance issues. With server-side tracking, events are collected on your own first-party domain and processed in a secure EU server, delivering more accurate, compliant, and complete data.

What is JENTIS?

JENTIS is a European server-side tracking platform that gives companies full control over their first-party data. It ensures GDPR/ePrivacy compliance while delivering up to 97% data accuracy and higher ROAS by overcoming blockers, consent gaps, and third-party risks.

How can I set up a reverse proxy for JENTIS tracking?

To set up a reverse proxy with JENTIS, you configure a first-party subdomain (via DNS A-record) and route tracking requests through it to JENTIS, ensuring cookies and events remain first-party. JENTIS’ Twin Server then cleans, pseudonymizes, and forwards only compliant data to downstream tools, fulfilling CNIL proxy requirements and boosting Safari data quality.

Does JENTIS have a dedicated Data Protection Officer (DPO)?

Yes, our DPO is: DataCo GmbH, Sandstr. 33, 80335 München, Contact: privacy@jentis.com

Does JENTIS provide a Service Level Agreement (SLA)?

Yes, JENTIS offers enterprise-grade SLAs that cover uptime, support response times, and infrastructure reliability, ensuring customers receive guaranteed service quality and stability.

Is JENTIS ISO certified?

Yes, JENTIS is certified under ISO 27001 (latest 2023 standard), ensuring an audited Information Security Management System for its EU-based infrastructure.

Why do you recommend using the JENTIS DPA instead of our own?

JENTIS provides a lawyer-drafted, regulator-proof DPA tailored to our technology and GDPR/ePrivacy requirements. Using it ensures faster onboarding, avoids lengthy legal negotiations, and guarantees coverage of all technical and organizational safeguards already audited for ISO 27001 compliance.

Why is a Data Processing Agreement (DPA) required with JENTIS?

Because JENTIS processes tracking data on your behalf in a customer-controlled EU environment, GDPR requires a DPA under Art. 28 to define roles, safeguards, and responsibilities. This ensures full legal compliance, clear accountability, and proof of privacy-by-design measures like pseudonymization and Essential Mode.

Can the JENTIS Terms & Conditions be modified?

Yes, customers with Enterprise licenses can negotiate individual terms and conditions.

Can I export raw tracking data from JENTIS?

Yes, JENTIS lets you export raw event data via APIs or direct integrations into your own data warehouse. This gives you full ownership and flexibility while keeping data processing under GDPR-compliant safeguards.

How long is raw data available?

JENTIS does not permanently store your tracking data; it is only processed within your dedicated environment. For long-term use, raw event data is exported daily (e.g., via sFTP or warehouse integration) so that you retain full ownership and decide how long to store it.

How do I access the FTP server with my raw data?

You receive dedicated sFTP credentials from JENTIS to log in and download daily raw data exports in JSON or CSV format. From there, you can automate ingestion into your analytics or data warehouse environment under your full control.

Can I control which data JENTIS collects, and how can I access it (API or export)?

Yes, you decide which data points are collected through JENTIS’ tag and tool configuration. The data is then made available to you via secure daily exports (e.g., sFTP in JSON/CSV) or through API access, so you can integrate it directly into your data warehouse or BI systems.

Why does the raw data export show an empty consent value?

If a user does not give consent, JENTIS still records the event in Essential Mode but without consent flags, so the consent field appears empty. This ensures legal compliance while still giving you visibility into non-consented traffic for unbiased analytics.

How should I measure the impact of Synthetic Users on conversions?

Run A/B comparisons of your conversion and ROAS data before and after enabling Synthetic Users. This highlights the uplift from previously untracked, non-consenting users—for example, Giesswein achieved a 25% ROAS increase after activation.

What happens once the Synthetic User model has enough training data?

After training on consenting users’ behavior, the model can reliably generate synthetic conversions for non-consenting users. These pseudonymized datasets are then activated in platforms like Google Ads, closing attribution gaps and boosting ROAS while staying GDPR-compliant.

What setup is required before the Synthetic User model can start collecting data?

You need to enable Essential Mode in JENTIS, configure which consented and non-consented data points are collected, and integrate your target tools (e.g., Google Ads). Once this setup is in place, the model can begin gathering behavioral data from consented users to train on and later fill in gaps for non-consented users.

Do changes in the Synthetic User setup need to be published before they take effect?

Yes, like all JENTIS configurations, adjustments in the Synthetic User tool must be published in the platform to become active. This ensures that only reviewed and approved changes influence data collection and modeling.

Which tags are created after the Synthetic Users model is generated?

When you create a Synthetic Users model, JENTIS automatically adds a Synthetic Users tool with default data-gathering tags (User, Session, Pageview, Custom Event, Productview, Add to Cart, Order, Remove from Cart, Search). Alongside these, it provides Synthetic User variables such as a universal Click ID and tool-specific IDs (e.g., gclid, fbclid) for integrating with platforms like Google Ads and Meta.

How can I get started with JENTIS?

Getting started is simple: your IT team adds a lightweight JENTIS snippet and a DNS A-record to route tracking via your first-party domain. From there, you can migrate tags with the Data Layer Bridge, configure tools and CMPs, and run JENTIS in parallel with your existing setup to validate data before going live.

Do I need to switch my analytics tool?

No, JENTIS works with your existing analytics tools like GA4, Adobe, or Piwik PRO. It simply delivers more accurate, privacy-compliant data to them via server-side tracking, so you get better insights without changing your stack.

What resources are required to implement JENTIS?

You’ll need minimal IT support to add the DNS A-record and lightweight JENTIS snippet (1–2h each). From there, your tracking team maps existing tags via the Data Layer Bridge and configures tools and CMPs, typically within days, supported by JENTIS experts.

How is the pricing determined?

JENTIS pricing is based on your subscription plan and data volume, with contracts typically aligned to enterprise or annual agreements.