Health Center monitors your tags performance in JENTIS and notifies your team immediately when something goes wrong.
Book a demoHealth Center flags issues with tags so you can publish with confidence.
No more waiting 48 hours for data to appear in Google Analytics, or discovering later that it never arrived. Health Center monitors every tag immediately after publishing and assigns it a real-time health status.
Tags are flagged when failure rates increase, failures spike unexpectedly, or triggers are dropped before execution. Active issues appear directly in the interface, so broken tags are caught in Health Center instead of showing up later as gaps in your reports.
For every monitored tag, Health Center records periods of high failure rates, the number of dropped triggers, and whether an issue is ongoing or has recovered. Detected issues appear in the interface as the starting point for investigation: from an issue, you review the affected tag, its recent history, and related configuration changes.

Health Center sends email notifications when issues are detected. Recipients can be platform user accounts or custom email addresses. A configurable suppression window prevents repeated emails for the same ongoing issue, and failure-rate thresholds and traffic-outage alert periods can be adjusted to your setup.
View tag health across an entire server-side container to identify broad problems, or filter by a specific tool when investigating a single integration, destination, or vendor. Filtering reduces the number of tags in view. This is particularly useful in containers with many tags, or when tag ownership is split across teams.
Health status is derived from how a tag actually behaves at runtime, not from its configuration. Health Center observes tag executions in the server-side container and flags deviations from normal behavior.
An issue is created for four conditions: a high failure rate, a sudden increase in failures, dropped triggers, or a recurring problem that remains unresolved. Recurring issues are tracked as such.
Failure rate is measured as the percentage of a tag's traffic that fails during evaluation, and thresholds are defined in adjustable buckets that apply account-wide to every container. Traffic-outage alerts are configured separately by time period and, unlike failure-rate thresholds, support per-container overrides.
Health Center detects issues, it does not determine root causes. A flagged tag directs investigation toward six areas: tag configuration, trigger conditions, container configuration, vendor endpoint availability, authentication or permission problems, and network or request-format errors.


Choosing JENTIS was like moving from a standard solution to a premium one. With Synthetic Users, we saw that even the best industry practices can be outperformed by next-generation approaches, tracking 40 points more ROAS in only three weeks and achieving 94% data accuracy. It’s given us a far stronger foundation for data-driven decision-making, with the added benefit of working alongside a committed European partner.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.
Health Center monitors tag execution in your server-side container. It flags tags with unusually high failure rates and tags whose triggers are dropped before execution, and assigns each monitored tag a health status based on its observed behavior.
Active platform user accounts and custom email addresses, in any combination. Recipients are configured in the Health Center settings.
No. Health Center detects and displays issues so your team can investigate them. The cause may lie in tag configuration, trigger conditions, container configuration, vendor endpoint availability, authentication, or request format — the fix depends on the cause.
Failure-rate thresholds apply account-wide across all containers. Traffic-outage alert periods support per-container overrides.
48 hours per tag, on a rolling basis. The history shows periods of high failure rates, the number of dropped triggers, and whether an issue is ongoing or has recovered.
No. A configurable suppression window controls how often notifications are sent for the same or similar ongoing issue.