Promo codes are the cheapest live-ops tool and the easiest one to lose money on. The difference is three settings. This page is how codes work in an Appside store, how to set the limits before you set the discount, and how to use a code as a measuring stick for a channel.
What a code is
In the Studio, a promo code has:
- A discount: a percentage or a fixed amount, applied to the packs you choose (one pack, a few, or all).
- A per-player limit: how many times one player account can redeem it.
- A total limit: how many redemptions in all, after which the code stops.
- A window: an optional start and end time in UTC.
Players redeem a code while signed in from the game (the player token is the identity), so every redemption belongs to a player account, not a browser. Codes don't stack with each other.
Set the limits before the discount
| Setting | Default to use | Why |
|---|---|---|
| Per-player limit | 1 | A code that works twice is a coupon book |
| Total limit | The audience size, with headroom (a creator with 5,000 viewers: 500) | A leaked code ends on its own |
| Window | 7 to 14 days | A code with no end is a permanent price |
| Packs | One or two, not all | The code should move a specific pack, not reprice the store |
| Discount | Enough to be worth typing, not enough to beat your best bundle | Otherwise it cannibalises the bundle |
Set the four limits, then the discount. Teams that do it the other way round discover a 25%-off code on every pack three weeks later, still active.
One code per channel, and count paid orders
A code is also the simplest attribution you'll ever have (more):
- A code for the Discord, one for the newsletter, one per creator, one the support team can hand out.
- Every paid order reaches your backend as a signed
order.paidwebhook with the player ID and the pack (reference). Your order table records which code the player used; join it to the channel. - Count paid orders per code, not redemptions: a code that gets typed and abandoned at checkout is telling you about the checkout, not the channel.
The three abuses, and the limit that stops each
- The forum leak. A creator code posted publicly. Stopped by the total limit and the window.
- The multi-account farm. One person, several accounts, one code each. Stopped by the per-player limit plus the fact that redemption needs a signed-in game account, which has a cost to create in most games. Watch for many first-time web buyers on one code in one hour.
- The stack. A code applied on top of a bonus on top of a bundle. Stopped by not stacking codes, and by designing offers so a player sees one bonus at a time (live ops).
Four codes worth having on day one
| Code | Packs | Limits | For |
|---|---|---|---|
WELCOME type (first web purchase) |
Starter bundle | 1 per player, no total, 30 days | Newsletter and Discord launch |
| Creator codes | The pack the creator shows | 1 per player, total = audience ÷ 10, 14 days | Each creator |
SORRY type (support recovery) |
Any one pack | 1 per player, total 200, 90 days | Support, after a bad first purchase |
| Event code | A bundle | 1 per player, total = event size, event dates | Events, printed on the QR |
Name them for the channel, not the discount, so the order table reads like a channel report.
Create your store free and set up the four codes in the Studio. No card needed to start; 3.9% per successful payment.