epic: broadcast platform support

[bokelley]

As O-N-X and other linear TV providers launch on AdCP, we are finding issues that we need to address to make some of the nuances work.

3.0 — Implemented (PR #2046)

Creative delivery

• Ad-ID industry identifier on creative assets #2036 — Ad-ID industry identifier on creative assets
• Broadcast spot creative format in reference agent #2037 — Broadcast spot creative format in reference agent

Buy lifecycle

• Agency Estimate Number on media buys #2038 — Agency Estimate Number on media buys

Measurement

• Measurement maturation windows for broadcast TV #2039 — Measurement maturation windows for broadcast TV
• Measurement window progression in delivery reporting #2040 — Measurement window progression in delivery reporting (window_update, supersedes_window, is_final)
• Formalize media buy terms for measurement determinism #1964 — Formalize media buy terms for measurement determinism

Delivery transparency

• Third-party tracker support inference from format definitions
• Delivery data completeness (is_final, measurement_window, supersedes_window on packages)
• Structured video requirements (schema-aligned field names, 12 new fields)

Documentation & storyboards

• Broadcast TV channel docs (broadcast.mdx)
• Media buy docs: broadcast product discovery, accountability, task reference examples
• Broadcast seller storyboard with comply scenarios (full cycle with window_update examples)
• Testable JSON snippets (20 new validated examples across broadcast, CTV, video)
• What's New in 3.0 — rc.3 to 3.0 highlights section

3.1 — Proposed solutions

• Measurement source attribution on delivery reports #2041 — Measurement source attribution on delivery reports
• Radio/audio broadcast format support and loudness requirements #2072 — Radio/audio broadcast format support and loudness requirements (AES TD1008)

3.1 — Needs input from broadcast sellers

• Multi-party measurement reconciliation for broadcast #2042 — Multi-party measurement reconciliation for broadcast
• Measurement vendor data latency profiles #2043 — Measurement vendor data latency profiles

Independent of release

• Training content: broadcast TV concepts and exercises #2047 — Training content: broadcast TV concepts and exercises
• test:json-schema should handle AdCP macros in URI fields #2049 — test:json-schema should handle AdCP macros in URI fields

Context (Greg @ O-N-X, 2026-04-09)

Key feedback from broadcast seller integration:

• No VAST for broadcast — need the spot file (H.264/MPEG4 HD)
• Ad-ID is required — ties rotation instructions to creatives
• Agency Estimate Number is "the most important number" — must travel with order and Ad-IDs
• VideoAmp data arrives ~15 days after broadcast
• Data is fed-duplicated (deduped across set-top box, smart TV, panel sources)
• Measurement accounts for Live + 7-day DVR playback
• They guarantee and reconcile as data arrives

Context (Sam Sousa, 2026-04-11)

• Audio loudness for OTA broadcast (-24 LUFS per ATSC A/85) is correct for TV but too quiet for audio-only
• AES TD1008 recommends -18 LUFS for audio interstitials/advertisements
• Creative reuse across channels means source should target -18 LUFS; playout normalizes anyway
• Radio broadcast needs similar format treatment to TV broadcast (no trackers, Ad-ID, physical delivery)