Measurement

Analytics, Safety & Reporting

Use analytics to understand audience behavior and delivery quality; use official sources as truth for safety alerts.

IridesceuxHVNCommandCloudflare

Audience Intelligence

Monitor live concurrency, uniques, arrivals/exits, watch time, retention, market distribution, program carryover, referral sources, device/delivery health and ad performance. Command preview sessions are designed not to count as audience sessions.

Advertiser reporting workflow

  1. Verify campaign and creative IDs are correct before airing.
  2. After air, review plays/completions/market/program distribution.
  3. Review proof-of-play/as-run data.
  4. Export or summarize only the metrics you can support with collected telemetry.
  5. Do not claim precise demographic facts you do not actually collect.

Safety & Weather Desk

  1. Refresh official alert feeds for the target market.
  2. Open the authoritative alert details.
  3. If AI-assisted wording is used, treat it only as a draft summary.
  4. Verify the draft against the official alert.
  5. Preview the on-air safety graphic.
  6. TAKE for the affected market only, unless the alert is actually national.
  7. Clear when the warning expires/is cancelled, and preserve the log.
Never invent emergency facts. AI should summarize authoritative alert content, not decide whether an emergency exists.
Safety system scope: the automated NWS monitor currently checks official alerts at configured representative coordinates for each HVN market. That is useful assistance, but it is not a substitute for an authoritative full-DMA emergency-alerting system. Keep automatic TAKE off unless you have deliberately reviewed the event allowlist, coverage model, and operator procedure.
v20.4 fix: safety expiration comparisons now normalize ISO timestamps correctly, and on-air expiration times use each market's configured time zone instead of treating every market as Eastern Time.