Order lines as stored
Every row Buds Auto'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 | 49440 | 119416 | yes | yes | 2026-02-01 → 2027-01-31 | 128,000 | ||
| PPC | PPC | Pay-Per-Click Ads | 49440 | 114825 | yes | yes | 2026-02-01 → 2026-08-02 |
$3,185.00 $19,110 total |
||
| SEO | SEO | SEO | 49440 | 114824 | yes | yes | 2026-02-01 → 2026-07-31 | |||
| Social Mirror | Social Mirror | Social Mirror Ads | 49440 | 119417 | yes | yes | 2026-02-01 → 2027-01-31 | 100,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.