Level up. Article complete. Limits that protect the campaign and still feel generous.
Engagement playbooks Campaigns Fairness

Play limits that don't annoy your players

Per-player limits, in total and per day, keep a campaign fair and its budget intact. Setting them without making people feel shut out.

Every campaign needs limits. Without them, the most determined people play hundreds of times, your prize budget goes to a handful of them, and everyone else’s chance shrinks. With the wrong limits, people hit a wall on their second visit and don’t come back. The goal is somewhere in between: tight enough to keep things fair, loose enough that nobody feels turned away.

Two numbers

Limits are set per player, with two numbers:

  • In total. The most plays one person gets for the whole campaign.
  • Per day. The most plays one person gets in a single day.

Use either or both. Leave one empty and there’s no limit of that kind. A campaign built on routine suits one play a day with no total. A launch weekend might suit three plays in total, however they’re spread.

The same two limits can also be set on a channel, across every campaign that runs on it. That answers a different question. “Three goes at this game” is a campaign rule. “Ten plays on our app this month, whatever is running” is a channel rule. When both apply, whichever runs out first stops the play.

Who counts as a player

Keliplay doesn’t have its own player accounts. Your backend passes your own id for each player when it asks for a play token, and every limit counts against that id.

That makes limits exactly as strong as your idea of who someone is. Behind a login, one person is one id, and the limits are solid. On an open page, where your id might be a cookie, a determined person can clear it and look new. If the prizes are worth cheating for, put the game behind a sign-in.

What counts as a play

A play counts as soon as it starts, not when it finishes. Closing the tab halfway through a bad run doesn’t give it back. Without that rule, a limit of one would really mean one play that was allowed to go well.

Limits are checked at the moment a play starts, so two quick taps on two devices can’t slip past one another. Your backend also gets an early answer when it asks for a token, with a clear message such as the player having used all their plays for today. Handle that response in your own interface too, so the player hears it from you.

What the player sees

When someone has no plays left, the Play button says so. The default is “No plays left”, and you can change it. That alone is a dead end, though, and dead ends are what make limits feel mean.

The pre-game page can show blocks only to players who are out of plays. Use them to turn the wall into a door:

  • Tell them when they can play again. “Come back tomorrow for another spin” is a reason to return.
  • Remind them what they already won, if they won something.
  • Point them at something else worth doing on your site.

Picking the numbers

There’s no universal right number, but a few rules of thumb hold up.

Quick chance games want tighter daily limits, because each play is over in seconds. Skill games can be more generous, since practice is part of the fun and the prize rarely depends on volume. Prediction games only need one play; there is one answer to pick.

Test plays from the dashboard don’t count against any limit, so your team can try a campaign as often as it likes before launch.

There’s no cooldown between plays within a day. If you want to space plays out, the daily limit is the tool.

Keep reading