Order lines as stored
Every row Usdan Summer Camp for the Arts'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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Display | Display | Display Ads | 50383 | 121788, 121792 | yes | yes |
2026-01-01 → 2026-07-06 2026-07-01 → 2026-10-31 |
400,000 | ||
| Meta | Meta | Meta Display & Video Ads | 50383 | 121791 | yes | yes | 2026-07-01 → 2026-10-31 | 60,000 | ||
| Mobile Conquesting | Mobile Conquesting | Mobile Conquesting Display & Video Ads | 50383 | 121787 | yes | yes | 2026-01-01 → 2026-07-06 | 180,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.