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, the hosting and certificate configuration each domain resolves to, and the ISPs whose traffic to a domain is declining.
Traffic Health has two tiers. Both tools work on any network with Traffic Health enabled, but some resources and includes need Traffic Health Premium — marked below, and listed in full under Free vs. Premium. A Premium request on a non-Premium network does not error: it returns an empty result with an explanatory note. If Traffic Health is not enabled at all, both tools return INVALID_ARGUMENT: Traffic Health is not enabled for this network. On a network without Premium, the premium-only types and includes are not listed in the tool descriptions at all — the model only sees the baseline set — and calling one anyway returns a note rather than data. The description a model sees is chosen when it lists tools and is cached by clients; a request for a Premium type on a network without Premium always returns the note.

​
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. Requires: Traffic Health (Read Only) Ask for it: “Which of my tracking domains have open remediation tasks?” · “Is any ISP’s traffic to my domains dropping?” Parameters Example
Resource types Returns Every list type returns a uniform wrapper: Gotchas
  • Only uptime_incidents and domain_reputations truly paginate. hosting and ssl_certificates carry the total/has_more/page/page_size envelope but return one page of 50 rows that cannot be paged: narrow with domain. domains, tasks and isp_trends return the full set and omit those fields. ip_reputations returns at most 100 incidents and omits them too. When has_more is true on a paginated type, page with page or narrow with domain, status, or from/to.
  • Parameters that don’t apply to the chosen type return an error, not silence. Passing page (above 1) or page_size to a non-paginated type, domain to a type that isn’t domain-scoped, or expires_within_days to anything but domains/ssl_certificates returns INVALID_ARGUMENT naming the types that do accept it.
  • An empty isp_trends result means no US pair with at least 100 clicks (30 days back) is declining, not that there is no traffic. Only declining pairs are returned, and only when yesterday’s clicks are down against all three comparison days (conversions and revenue are reported but not tested).
  • Unknown include names, an invalid type, and dates not in YYYY-MM-DD form return INVALID_ARGUMENT listing the valid values. Pass domain without a scheme (track.acme.com); include is case-insensitive.
  • Timestamps are UTC — formatted strings, YYYY-MM-DD HH:MM:SS (e.g. 2026-12-22 14:08:06). The one exception is the assignments → usage window on the other tool, which follows the network timezone. Fields are omitted when unset.
  • For a domain’s identity and config (ID lookup, primary/assignable flags, redirect settings) rather than its health, use get_entity/list_entities with type=tracking_domain — that works on networks without Traffic Health too.
Item fields by type
A single object — not wrapped in the list envelope.
hostingssl_certificates
domain_reputationsip_reputationsThe remediation object 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. Requires: Traffic Health (Read Only) Ask for it: “What’s going on with track.acme.com, and what’s at risk if it goes down?” Parameters Example
Includes Returns The situation summary is always returned, with or without include:
www. is resolved for you. Monitored domains are stored under one exact URL. If acme.com is not monitored but www.acme.com is (or the reverse), the lookup retries the other spelling once, and every response carries resolved_domain, the spelling that matched. Compare domains on resolved_domain, not on what you passed in, or one domain can look like two.
Each requested include is added under its own key: An include that cannot be loaded comes back as { "note": "..." } under its key without failing the call (Could not load <include>.). assignments and mismatches apply only to tracking domains: for a URL that is not one of the network’s tracking domains, assignments returns the note Assignments apply only to tracking domains; this URL is not a tracking domain for the network. and mismatches returns No tracking domain found for this URL. usage is omitted when the domain has no traffic row or the lookup fails. The uptime_incidents, domain_reputation and ip_reputation includes return page 1 at the default page size of 100 rows and cannot be paged (no page or page_size is passed through). 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: Gotchas
  • Only monitored domains resolve here. A domain that appears in list_traffic_health(type=domains) but isn’t monitored returns INVALID_ARGUMENT: Domain with url … is not present in list of monitored domains.
  • The usage window follows the network timezone, unlike the UTC timestamps everywhere else in Traffic Health. It carries its own timezone field so the two can’t be confused.

​
Free vs. Premium

A Premium-only request on a network without Premium returns an empty result and a note, rather than an error:

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.