Order lines as stored
Every row Milligan Vein'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| PPC | PPC | Pay-Per-Click Ads | 44767 | 133026 | yes | yes | 2026-07-01 → 2026-12-31 |
$1,806.00 $10,836 total |
||
| Performance Max | Performance Max | Performance Max Ads | 44767 | 133043 | yes | yes | 2026-07-01 → 2026-09-30 |
$7,500 total |
||
| SEO | SEO | SEO | 44767 | 119561 | yes | yes | 2026-01-01 → 2026-09-30 | |||
| Social Mirror | Social Mirror | Social Mirror Ads | 44767 | 133028 | yes | yes | 2026-07-01 → 2026-09-30 | 75,000 | ||
| YouTube | YouTube | YouTube+ Video Ads | 44767 | 119562, 133027 | yes | yes |
2026-01-01 → 2026-12-31 2026-07-01 → 2026-12-31 |
127,000 |
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.