Order lines as stored
Every row Solo'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| CTV | CTV, Video | CTV + Video Ads | 49912 | 116437 | CANCELED | yes | 2026-02-01 → 2026-09-30 | 42,857 | ||
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 49912 | 116436 | CANCELED | yes | 2026-02-01 → 2026-10-31 | 1,466,666 | ||
| Social Mirror | Social Mirror | Social Mirror Ads | 49912 | 116435 | yes | yes | 2026-06-10 → 2026-10-06 | 213,333 | ||
| Video | CTV, Video | CTV + Video Ads | 49912 | 116437 | CANCELED | yes | 2026-02-01 → 2026-09-30 |
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.