A six-night run reports as one number, and that number is usually fine. Two weekend shows sell strongly, the aggregate lands around seventy percent, and everyone moves on. Inside that seventy percent sit two weekend dates at ninety-five and a Tuesday at thirty-one. The Tuesday is where the margin went, and nobody looked at it until the final fortnight, when the only remaining instrument was a discount.

Why aggregates fail here specifically

Multi-date runs share creative, share a campaign structure, share a budget, and increasingly share an automated bidding layer that optimises across all of it. Platform optimisation will naturally push spend toward the dates that convert most easily, which are the dates that needed the least help. Left alone, the machine spends the run's budget selling out the shows that were already selling out.

This is not a flaw in the algorithms. They are optimising for the objective they were given, which is conversions, not sell-through per date. Nothing in the campaign structure tells them that the ninety-fifth percent of a Saturday is worth far less than the fortieth percent of a Tuesday.

What to do instead

• Budget per date, not per run. Each date gets its own line, its own pace target and its own read. It is more work and it is the only structure that surfaces the problem in time.
• Pace targets by day of week. A Tuesday does not sell like a Saturday and should not be judged against the same curve. Hold each date to its own comparable.
• Cap the strong dates early. Once a date's forecast clears its target with confidence, its budget should fall, not hold. The freed budget has an obvious destination.
• Separate the creative angle. Mid-week dates often need a different reason to attend rather than more impressions: availability, better seats, a shorter queue, a lower price band that still exists.

The timing that decides it

A weak date identified in week one has every instrument available: reach, creative, audience expansion, price, even a schedule change in extreme cases. The same date identified in the final fortnight has one instrument, and it is the expensive one. The entire value of per-date reporting is that it moves the discovery forward by four or five weeks.

This is also why weekly reporting cycles cost real money on live runs. A Monday report on a Tuesday problem is a week late, every week.

The structural fix

Per-date visibility requires ticket sales attributed to the specific performance, joined to spend attributed to the same performance, updated daily. Ticketing systems hold the first. Ad platforms hold the second, usually at campaign level rather than date level, which is why the join has to happen outside both.

Once it exists, the management of a run changes shape: instead of one budget conversation per week, there is a daily reallocation across dates, most of it small, none of it dramatic. The Tuesday gets found in week one, and the weekend stops absorbing money it does not need.