Order lines as stored
Every row Ram Jack of Eastern Virginia'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Live Chat | Live Chat | Live Chat | 44807 | 119581 | yes | yes | 2025-11-20 → 2026-09-30 | |||
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 44807 | 118056 | CANCELED | yes | 2025-11-07 → 2026-09-30 | 66,666 | ||
| Performance Max | Performance Max | Performance Max Ads | 44807 | 121176 | yes | yes | 2026-01-01 → 2026-07-31 |
$12,250 total |
||
| YouTube | YouTube | YouTube+ Video Ads | 44807 | 118058 | CANCELED | yes | 2025-11-06 → 2026-09-30 | 18,750 |
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.