Order lines as stored
Every row Valero Law Group's 2026-07 report is judged against - not the summary a finding prints, the actual rows. Would be is what today's code would map the raw product name to; where that differs from Product, the row was written by an older import and that is the whole answer.
| Product | Would be | Raw name on the order | Order | Line items | Live | Ran in 2026-07 | Flights | Impressions a month |
Budget a month |
Ad spend |
|---|---|---|---|---|---|---|---|---|---|---|
| YouTube | YouTube | YouTube+ Video Ads | 50052, 52972 | 118566, 126654, 126655, 126656, 126657, 126658, 126659, 128407, 128408, 133021, 133022, 133023, 133024, 133025 | yes | yes |
2025-11-05 → 2026-09-30 2025-11-05 → 2026-09-30 2025-11-05 → 2026-09-30 2025-11-05 → 2026-09-30 2025-11-05 → 2026-09-30 2025-11-05 → 2026-09-30 2026-01-05 → 2026-09-30 2026-04-08 → 2026-09-30 2026-05-01 → 2026-07-10 2026-07-01 → 2026-09-30 2026-07-01 → 2026-09-30 2026-07-01 → 2026-09-30 2026-07-01 → 2026-09-30 2026-07-01 → 2026-09-30 |
543,809 |
Flights: none recorded means the row predates build 42, which is when each order's own window started being kept. Until it is re-read, the period test falls back to the merged span and a gap between two flights is invisible.