Order lines as stored
Every row Roto Rooter'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 | 42808 | 95679 | yes | yes | 2024-11-12 → 2026-12-01 | |||
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 51790 | 122839 | yes | yes | 2026-01-10 → 2026-07-31 | 133,333 | ||
| PPC | PPC | Pay-Per-Click Ads | 42452 | 94667 | CANCELED | yes | 2024-11-08 → 2026-12-31 |
$1,750.00 $45,500 total |
||
| Performance Max | Performance Max | Performance Max Ads | 52289 | 124431 | yes | yes | 2026-07-31 → 2026-12-31 |
$12,500 total |
||
| SEO | SEO | SEO | 37198 | 110257 | yes | yes | 2025-07-01 → 2026-12-31 |
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.