Order lines as stored
Every row SBS One Source Architects'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 | 54144 | 130452 | CANCELED | yes | 2026-06-17 → 2027-05-31 | |||
| Meta | Meta | Meta Display & Video Ads | 54144 | 130451 | yes | yes | 2026-06-18 → 2027-05-31 | 39,285 | ||
| Social Mirror | Social Mirror | Social Mirror Ads | 54144 | 130450, 131843 | CANCELED | yes |
2026-06-01 → 2027-05-31 2026-06-22 → 2027-06-22 |
663,156 | ||
| Video | Video | Video Ads | 54144 | 130453 | CANCELED | yes | 2026-05-11 → 2027-04-30 | 433,333 |
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.