Measurement vendor data latency profiles

[bokelley]

Parent: #1919
Related: #2039 (measurement windows), #1972 (measurement agents)

Problem

Greg (O-N-X) told us VideoAmp data arrives ~15 days after broadcast. We don't know if this is:

• A VideoAmp-specific number
• Standard across all broadcast measurement vendors
• Variable by market size, source type, or window

The measurement window concept (#2039) includes expected_availability_days per window, which may be sufficient. But if different vendors deliver the same window on different timelines, buyer agents need to know.

Questions for Greg / broadcast sellers

1. Is 15 days standard? Does Nielsen deliver on the same timeline? Comscore?
2. Does it vary? By market size (top 25 DMA vs long tail)? By source type (STB vs ACR vs panel)?
3. Is there a contractual SLA? Do measurement vendors commit to a delivery timeline, or is 15 days just typical?
4. What happens when data is late? Does the vendor notify? Is there a penalty? Does reconciliation slide?

What we have today

• expected_delay_minutes on reporting-capabilities.json — works for digital latency, technically works for 15 days (21,600 minutes) but misrepresents the concept
• expected_availability_days proposed in Measurement maturation windows for broadcast TV #2039 on measurement windows — better fit

Hypothesis

If expected_availability_days is on the measurement window definition and the measurement vendor is identified on the terms, that may be enough. The vendor's delivery timeline is implicitly declared by the seller when they publish their product's measurement windows.

Per-vendor latency profiles may only matter if a buyer is comparing the same window across different vendors — which is a measurement agent concern (#1972), not a media buy concern.

Blocked until

Input from broadcast sellers on vendor-specific timelines.