How to Set Up Event Discount Codes Without Losing Revenue

A discount code does two jobs: it moves someone from thinking about it to buying, and it tells you which channel moved them. Most events use it for the first and waste the second.

Give every channel its own code

Not one code for the launch — one per partner, newsletter, speaker and social campaign. The discount can be identical; the code is the measurement. At the end you know that the partner newsletter produced forty registrations and the paid post produced three, which is the only way next year's spend gets better.

Always set three limits

• An expiry date. A code without one is a permanent price cut you have forgotten about.
• A usage cap. Total uses, so a leak is a bounded loss rather than an open one.
• Which tickets it applies to. A code meant for a standard ticket should not discount the student rate.

Per-person codes for anything sensitive

Speaker, sponsor-guest and complimentary codes should be one code per person with a single use. A shared "SPEAKER26" code will be forwarded — not maliciously, just helpfully — and you will discover it when the numbers do not reconcile. Single-use codes also let you see who has claimed and chase who has not.

Percentage or fixed amount?

Fixed amounts read as larger on cheap tickets and smaller on expensive ones; percentages do the reverse. For a mixed ticket range, a percentage is more predictable for you and easier to explain. For a single ticket price, a round fixed amount lands harder: "£50 off" beats "20% off" at £250, even though they are the same.

Do not let the code become the price

If every campaign carries 20% off, your standard price is now 20% lower and you have added a step. Use codes for specific, time-bound reasons — a partner's audience, a lapsed-attendee win-back, a bulk arrangement — and let early bird do the general discounting, because it has a deadline everyone can see.

Watch for leaks

Public codes end up on deal aggregators. Two defences: a usage cap, and checking redemptions weekly against the channel you issued to. A code issued to a 400-person newsletter that has 900 redemptions has left the building. That is a five-minute check, and it is cheaper than the alternative.

Reconcile at the end

Redemptions per code, revenue after discount, and the acquisition cost per channel. Put it in the post-event report — it is one of the few sections that changes next year's plan.

Gathervo supports per-code limits, expiry, ticket restrictions and single-use codes, and reports redemptions per code. Try it free.