Order lines as stored
Every row Hot Tubs Etc'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 44826 | 106499 | yes | yes | 2025-06-01 → 2026-08-19 | 57,333 | ||
| PPC | PPC | Pay-Per-Click Ads | 44826 | 101834 | yes | yes | 2025-03-01 → 2026-08-19 |
$910.00 $16,380 total |
||
| Performance Max | Performance Max | Performance Max Ads | 53761 | 129258 | CANCELED | yes | 2026-05-01 → 2026-12-31 |
$16,000 total |
||
| SEO | SEO | SEO | 44826 | 101836 | yes | yes | 2025-03-05 → 2026-08-19 |
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.