Health Center monitors tag execution, flags tags with elevated failure rates or dropped triggers, and notifies your team by email — so issues are identified early and their impact on your data is reduced.
Book a demoNo waiting for a gap to show up in Google Analytics or another downstream tool. Health Center flags issues with tags immediately after publishing, helping to avoid data gaps.
Health Center monitors how each tag executes and assigns it a health status. A tag is flagged when it shows an elevated failure rate, a sudden increase in failures, or when triggers are dropped before the tag can run. Active issues are indicated directly in the interface, so a broken tag is visible in Health Center rather than discovered later in your reports.
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.

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 — 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.


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.