Back to blog
Seasons3 min read

How to read National Day week before it ends

National Day is a four-day season. The call you make on the 21st isn't the call you'd make on the 24th. Here's what to check each evening, and what to leave for the readout.
National Day is a four-day season. The call you make on the 21st isn't the call you'd make on the 24th. Here's what to check each evening, and what to leave for the readout.

National Day week moves fast. Spend rises, creators post, discount codes go around. Then the week ends, you open the reports, and you ask who brought what.

The question isn't hard. The hard part is that you're asking it after the window to act on it has closed.

What changes in a four-day season

An ordinary month tolerates a weekly rhythm. You see Monday's number, adjust on Wednesday, and lose very little. Four days don't give you that room, for three reasons:

  • Creator posts land in bursts. A post at 9pm produces most of its orders the same night. If you don't know where those orders came from that evening, tomorrow's budget is a guess.
  • Stock moves faster than reporting. A product that sells out on day two takes its channel's return down with it. The channel looks like it weakened, and the cause was a stock decision.
  • Ad platforms are still learning. The window is too short for the learning phase to finish, so platform-reported conversions are at their least reliable exactly when you lean on them most.

Three numbers to check every evening

An evening check is enough for most stores, as long as it covers these three:

  1. Revenue by source, for today. Not blended, and not yesterday's export.
  2. Spend against revenue per channel. A channel sitting below break-even during a season costs more per hour than in any ordinary week.
  3. Whether tracking is still receiving events. A break on day one of a four-day season eats the whole season, and it makes no sound.

Everything else can wait for the readout. Order-level source and channel performance update in Flowfy as orders arrive, so the check happens on one screen instead of across three dashboards.

The check on its own isn't enough. Decide before the season what you do when a number moves: if a channel sits below break-even two nights running, do you cut its budget by an agreed percentage or pause it? If tracking stops, who calls whom? Those calls take a minute when they're written down in advance and a full day when the discussion starts mid-season.

Why the blended return isn't a decision

7.4× across the week is a fine headline. As an instruction it says nothing, because it's an average over channels that behaved nothing alike.

In most strong seasonal weeks there's one channel carrying the result and one spending with nothing to show. The blended figure is high enough that neither gets opened until the week is done. What you need is the split: what each channel spent and what it returned, day by day.

Seasons widen the spread between channels sharply. Creator posts spike and stop, retargeting pools saturate faster because frequency is higher, and prospecting costs rise because everyone is bidding on the same days. A channel that held steady all month can move twice in four days.

Discount codes give you a partial picture

Every seasonal campaign leans on codes, and a code counts the people who remembered to type it. That gap widens during a season, because shoppers compare stores quickly and type fewer codes than usual.

If you settle with creators on codes, you'll underpay the creator who actually moved buyers and overpay the one whose audience is diligent about typing. The alternative is a tagged link per creator, with the source stored on the order itself. Flowfy captures the source from a tagged link and holds it on the order; a per-creator link manager is on the roadmap and hasn't shipped, so today you build the links yourself.

The comparison worth running after the week

Compare against last year's National Day, not against last week. A previous-period comparison only tells you a season happened.

Bring three numbers from last year for the same days: revenue by source, order count, and the share of new customers. If revenue grew and orders held flat, you sold at higher prices rather than to more people. If orders grew and the new-customer share fell, the season was a discount to buyers you already had.

Season shading and saved period comparisons are on the roadmap and haven't shipped. Until they do, you pick both ranges yourself and compare them manually.

So once the week ends, read the result against last year's National Day, and start with new-customer cost before blended return. More on that in new customer acquisition cost. The evening check on three numbers belongs a week earlier, with one person named to run it.