Skip to main content
Traffic Health surfaces the operational health of the domains and IPs behind your tracking and conversion links — uptime, SSL, DNS and expiry incidents, blocklist reputation, the remediation tasks that need your attention, and the hosting/certificate configuration each domain resolves to. Two read-only tools cover the whole surface:

Free vs. Traffic Health Premium

Traffic Health has two tiers. Both tools are always available to any network with Traffic Health enabled, but a subset of resources and includes require Traffic Health Premium. On a network without Premium, a Premium-only request does not error — it returns an empty result with a note explaining the capability is unavailable, e.g.:
If Traffic Health is not enabled for the network at all, both tools return INVALID_ARGUMENT: Traffic Health is not enabled for this network.
Point-in-time timestamps in Traffic Health responses are formatted strings — YYYY-MM-DD HH:MM:SS in UTC (e.g. 2026-12-22 14:08:06). The one exception is the assignmentsusage window (from/to), which follows the network timezone to match run_performance_report and the portal; it carries its own timezone field. Fields are omitted when unset.

list_traffic_health

Lists Traffic Health resources network-wide, or scoped to a single domain. Set type to choose the resource; omit domain for a network-wide list or pass it to scope to one domain. Parameters: Resource types: Response envelope — every call returns a uniform wrapper:
Only uptime_incidents and domain_reputations honor page/page_size (default page size 100) for true pagination. hosting and ssl_certificates include the total/has_more/page envelope but return a single bounded page — they do not accept page/page_size. domains, tasks, and ip_reputations return the full set and omit those fields (ip_reputations is filtered in memory to premium-monitored IPs). When has_more is true on a paginated type, page with page, or narrow the result with the domain, status, or from/to filters.
Item fields by type: summary (a single object — not wrapped in the list envelope) domains tasks uptime_incidents hosting ssl_certificates domain_reputations (Premium) ip_reputations (Premium) The remediation object (on both domain_reputations and ip_reputations) turns a flag into an action — it’s the vendor-catalog detail behind the listing. The whole object is omitted when the catalog has no entry for the vendor; individual fields are omitted when blank.

get_traffic_health_domain

Returns the full Traffic Health picture for one domain in a single call — its current situation, plus on request its incidents, tasks, reputation, and configuration. Use list_traffic_health for network-wide rollups. Parameters: Includes: Response — situation summary (always returned, with no include): Response — composed includes: Each requested include is added to the situation summary under its own key: The assignments usage object reports the domain’s traffic and revenue over the trailing 90 days — the practical “blast radius” if the domain goes down. Unlike the point-in-time timestamps elsewhere in Traffic Health (which are UTC), this window follows the network timezone, matching run_performance_report and the portal:
get_traffic_health_domain only resolves domains that are monitored (present in the network’s monitored-domain list). A domain that appears in list_traffic_health(type=domains) but is not monitored returns INVALID_ARGUMENT: Domain with url … is not present in list of monitored domains.

Examples

Overall network health rollup
All open tasks across the network
Active uptime incidents for one domain in the last 30 days
Certificates expiring within the next 30 days
Domains flagged on a blocklist (Premium)
One domain’s full health picture with detail
A domain’s assignments and revenue exposure (Premium)assignments returns the assignment summary and a nested usage block (trailing-90-day traffic and revenue), so you can gauge what’s at risk while the domain is impaired:

Learn more about Traffic Health

See the Everflow Helpdesk for what Traffic Health monitors, when to use it, and how to act on domain incidents and tasks.