Tacnode™
Pipelies2 min

The Averaged Lie: A Stale Average Sets the Order Cap Too Low

The typical basket is $82. That was nine o'clock. A campaign has since pushed it to $140. At nine, the hourly job computes the typical basket: $82. The limit engine will use that number to size its per-order cap. Twenty minutes later a campaign brings in high-value buyers, and the real average climbs to $131. The stored number is still $82. Twenty minutes after that the real average is $140, and nothing on the stored number says how old it is. Just before ten the limit engine sets the cap at three times typical. It reads $82, so the cap is $246, and the new buyers' $400 orders start getting declined. Then the same hour with the limit engine reading from Tacnode. The average is computed from the orders up to now: $140. The cap comes out at $420, and those orders go through. Orders stream into Tacnode, and you choose per number how fresh it has to be. The ones a cap depends on are computed at the moment the cap is set. The rest sit in views that refresh as often as you need. Each cap is written back as context, and your pricing and limit rules don't change.

Overview

One of the fourteen Pipelies lies: how an average computed on the hour sets a cap too low for the customers a campaign just brought in, and the same hour with the limit engine reading from Tacnode.

Topics Covered

  • •An hourly job that computes the typical basket
  • •A campaign that changes the mix of buyers
  • •A stored number with nothing to say how old it is
  • •A cap set at three times an $82 average
  • •The average computed at the moment the cap is set

Key Takeaways

  • ✓The average was right at nine and $58 low forty minutes later
  • ✓The cap came out at $246, and $400 orders were declined
  • ✓Computed from the orders up to now, the cap comes out at $420
  • ✓You choose per number how fresh it has to be

Ready to get started?

Book a demo to see how Tacnode can power your real-time data infrastructure.