The post-event economy hangover and how long it lasts

An event runs, performs well, and ends. The following two weeks are quiet — purchases down, engagement softer, the store underperforming its usual baseline. The team reads this as post-event fatigue and starts planning the next event to fill the gap.

Sometimes that is what it is. Often it is something more mechanical, and treating it as fatigue leads to exactly the wrong response.

Where the quiet period comes from

Events inject currency. That is most of what they do — participation rewards, milestone payouts, completion bonuses, the contents of whatever players earned or bought. When the event ends, the activity stops but the currency does not disappear. It sits in wallets.

For a period afterward, a meaningful share of your players are wealthier than usual. They can buy the things they want without topping up, because the event already gave them the means. Purchases fall not because players lost interest but because they are spending down a balance rather than acquiring a new one.

This is a hangover in the literal sense: the effect of the event is still working through the system after the event itself is over. And it resolves on its own, at a rate determined by how much was injected and how fast players spend.

The trap is that the dip looks identical to disengagement on a revenue chart. Both show the same shape. The response to each is opposite — disengagement calls for something new, a spend-down calls for patience — so getting the diagnosis wrong is costly.

Telling the two apart

The signals separate cleanly if you look past revenue.

In a spend-down, engagement holds up while purchases fall. Players are still playing, still progressing, still acquiring things — they are simply acquiring them with currency they already had. Sessions and activity look normal or better. Only the top-up behaviour is suppressed.

In genuine post-event fatigue, engagement falls with revenue. Players are logging in less, sessions are shorter, and the drop in purchases is a consequence of them being less present rather than less needy.

The second distinguishing signal is aggregate wallet balance. If the total currency held across your player base is elevated relative to its normal level, the event injected more than players have spent yet, and the dip has a mechanical explanation. If balances are back at baseline and revenue is still down, the currency is gone and something else is happening.

That second measurement is worth having available as a standing number rather than something reconstructed after the fact. It is the difference between diagnosing this in an afternoon and arguing about it for a week.

Why running another event immediately makes it worse

The instinct when revenue dips is to schedule something. If the dip is a spend-down, this compounds the problem in a specific way.

Players who are still working through event currency do not need to top up for the new event either. They participate using the balance the last event gave them, and the new event converts poorly — not because it was badly designed but because its audience is pre-funded. Then it ends, having injected more currency of its own, and the hangover extends.

Two or three cycles of this and the game reaches a state where a substantial part of the player base is permanently ahead of the economy. Events run continuously, currency is always plentiful, and top-up purchases have largely stopped because nobody needs to. Revenue at that point depends almost entirely on the players who were going to buy regardless, and the economy has stopped doing any work.

Unwinding it is slow, because the fix is either to reduce event generosity — which reads to players as a takeaway — or to add sinks large enough to absorb the surplus, which changes the game's cost curve.

Planning for the recovery instead of against it

The productive response is to treat the recovery period as part of the event rather than as a failure following it.

If you know an event injects a certain amount and the population spends at a certain rate, the recovery window is predictable. Planning the calendar with that window included means the next event lands when players are actually in a position to engage with it, and it converts on its merits rather than against a pre-funded audience.

The second adjustment is on the event's own design. Events that pay out mostly in items rather than currency produce a much shallower hangover, because items are consumed in place rather than becoming general-purpose spending power. A player who earned a specific reward has that reward. A player who earned currency has optionality, and optionality is what suppresses future purchases.

The third is to give the surplus somewhere to go. An event that ends with a sink attached — a limited window to spend earned currency on something worthwhile — recovers the injected supply and gives players a satisfying use for what they won. That is a better outcome than the currency sitting in wallets suppressing sales for a fortnight.

See how we model what an event does to the economy →

The reporting habit that prevents the mistake

The narrow fix here is to stop reading event performance as a single number bounded by the event's start and end dates.

An event's real result includes what happened in the weeks after it. An event that produced strong revenue during its run and suppressed revenue for three weeks afterward may have shifted spending forward rather than created it. An event that produced modest revenue during its run and left the economy in good shape may have been the better one.

Measuring the window rather than the event is a small change to how results get reported and it changes which events look successful. It also makes the hangover visible as a normal, expected part of the cycle rather than as a mystery that shows up after every event and gets explained differently each time.

Talk to us about event economy planning →