Health Center
The JENTIS Health Center helps you detect and investigate tags with unusually high failure rates or dropped triggers in your server-side tag manager container.
It provides a centralized view of tag health, recent issue history, and notification settings, enabling teams to identify problems earlier and reduce the impact of broken or degraded tag execution.
Overview
Health Center monitors tag execution and highlights tags that show signs of degraded behavior. A tag may be marked as unhealthy when it has an elevated failure rate or when triggers are dropped before the tag can run.
Filtering by tool or container
Health Center supports two primary scopes:
Container level
Shows tag health across the entire server-side container. Use this to understand overall container health and identify broad problems.
Tool level
Shows tag health for tags associated with a specific tool. Use this when investigating issues related to a particular integration, destination, or vendor.
Filtering helps reduce noise when a container contains many tags or when ownership is split across different teams.
Tag status
Each monitored tag has a health status that reflects its current behavior.
The status view allows you to:
Review the current health of each tag
Filter tags by tool
Filter tags at the container level
Identify tags with active or recent issues
Compare healthy, degraded, and failing tags in one place
A tag’s status is based on observed execution behavior. When the Health Center detects an abnormal failure rate or trigger drops, the tag may be flagged with an issue.
24-hour issue history
Health Center includes a rolling 24-hour history for each tag.
The history view shows:
Periods with high failure rates
The number of dropped triggers
Recent changes in tag health
Whether an issue is ongoing or has already recovered
Issues and UI notifications
When the Health Center detects abnormal tag behavior, it creates an issue in the UI.
Issues are displayed directly in the Health Center interface to draw attention to tags that may require investigation.
An issue may indicate:
A high tag failure rate
A sudden increase in failures
Dropped triggers
A recurring or unresolved tag health problem
Use issues as the starting point for investigation. After selecting an issue, review the affected tag, recent history, and any related configuration changes.
Email notifications
The Health Center can send email notifications when issues are detected.
Notification settings allow you to configure:
Who receives Health Center emails
A suppression window to avoid repeated notifications for the same or similar issues
Notification recipients
Recipients should usually include the team or individuals responsible for maintaining server-side tags.
Recipients can be either active user accounts within the DCP or custom email addresses. The recipients can be set in the "Settings" sub-menu of the Health Center.
Suppression window
The suppression window controls how often email notifications are sent for recurring issues.
For example, if a tag continues to fail after an issue has already triggered an email, Health Center will wait until the suppression window expires before sending another notification for that issue.
This helps teams focus on meaningful alerts without receiving repeated emails for the same ongoing problem.
Limitations
Health Center detects observed tag health issues based on execution behavior. It does not automatically determine the root cause of a failure.
A detected issue may require further investigation into:
Tag configuration
Trigger conditions
Server-side container configuration
Vendor endpoint availability
Authentication or permission problems
Network or request-format errors
Last updated
Was this helpful?