Order lines as stored
Every row Sonoma Backyard'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 | 53054 | 126894 | yes | yes | 2026-03-19 → 2026-09-30 | 92,592 | ||
| Performance Max | Performance Max | Performance Max Ads | 53054 | 126896 | yes | yes | 2026-03-19 → 2026-09-30 |
$17,500 total |
||
| YouTube | YouTube | YouTube+ Video Ads | 53054 | 126895 | yes | yes | 2026-03-19 → 2026-08-31 | 59,523 |
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.