Order lines as stored
Every row Allegheny Trucks'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Meta | Meta | Meta Display & Video Ads | 54000 | 129951 | yes | yes | 2026-05-07 → 2026-10-31 | 40,000 | ||
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 54000 | 129956 | CANCELED | yes | 2026-05-01 → 2026-10-31 | 100,000 | ||
| Social Mirror | Social Mirror | Social Mirror Ads | 54000 | 129953 | CANCELED | yes | 2026-05-01 → 2026-10-31 | 88,235 | ||
| YouTube | YouTube | YouTube+ Video Ads | 54000 | 129954, 132503 | yes | yes |
2026-05-01 → 2026-10-31 2026-06-16 → 2026-10-31 |
75,000 |
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.