How to set event promo code limits and measure whether they work

You've sent a private discount code to a partner, and the tickets are moving. Then someone asks whether the code works on VIP tickets. Another buyer puts six tickets in one basket. Your partner posts the offer publicly, and suddenly the little test you approved has a much bigger audience.

This is why an event promo code strategy needs to start with limits. Decide which purchase you want to encourage, how much you're prepared to give up, and exactly what stops the offer. Then measure whether it brought your event enough additional business to justify that cost. A code being used proves that someone received a discount. It doesn't prove they needed one to buy.

We'll work through the decisions that matter before you share a code, including ticket and order limits, overlapping offers, partner distribution and the review afterwards. The calculations below use a fictional concert and illustrative figures. They're there to help you check your own offer, not suggest a standard discount for every event.

Give the code a specific job

The first thing you want to do is finish this sentence: "We're offering this code to these people because we want them to do this."

That might mean encouraging a local music community to try your new concert series. It might mean helping previous buyers commit to a quieter date. It could mean giving a partner an agreed offer for its members. Each purpose leads to different limits and a different way of judging the result.

"Sell more tickets" doesn't tell your team enough. If Saturday is already close to selling out, a code that also discounts Saturday could reduce what you earn from your strongest date. If you're trying to reach new people, a public code used mainly by existing fans isn't evidence that you've expanded your audience.

Write down what you believe is preventing the purchase. A discount can help when price is the obstacle and the reduced price still works for your business. It won't explain an unclear lineup, fix an unsuitable date or tell a buyer whether their friends are coming. You may get more from explaining the event properly before changing its price.

Our guide to testing ticket-sales email offers covers alternatives such as clearer programme information and useful included benefits. Start there if you haven't established why the audience needs a cheaper ticket. Once you choose a discount, the rest of this guide helps you keep that promise affordable and understandable.

Calculate what each discounted ticket leaves you

Suppose your concert normally leaves you $50 per ticket after taxes and selling fees. Serving each additional attendee costs another $10, leaving $40 towards venue hire, artists, other fixed costs and profit. These are fictional organizer receipts, not advertised checkout prices.

Now suppose the offer reduces what you keep by $10 per ticket, after accounting for the actual effect on fees and taxes. You retain $40 before the attendee cost, and $30 afterwards. Every genuinely additional discounted attendee therefore adds $30 towards the event's remaining bills. Every buyer who would have paid the usual price leaves you $10 worse off.

That second group is easy to overlook. Your code report can show a healthy ticket count even when the offer mostly reduces the price for people who were already planning to attend.

Imagine you sell 100 discounted tickets. If 70 buyers would have bought anyway and 30 are additional, the extra buyers contribute $900. The discount given to the other 70 costs you $700. You have $200 left before the costs of running the campaign. Spend $250 promoting it and the event is $50 worse off under those assumptions.

You won't know each buyer's alternative decision with certainty. That's why you need a comparison, which we'll cover later. For now, use the calculation to decide whether the offer has a plausible chance of helping.

Include partner commissions, extra staffing, materials and campaign spend where they apply. If a discounted booking crosses a threshold that requires another steward or an extra room, include that additional bill. Don't spread an unchanged venue bill across the tickets and mistake that accounting choice for the cost of admitting another person.

Our group ticket discount guide develops this calculation for larger baskets. The same principle applies to a code: the additional purchases need to pay for the discounts given to existing demand and the extra cost of running the offer.

Turn your discount budget into a real limit

Decide how much reduction in ticket receipts you're prepared to authorize before opening the settings. For the fictional concert, suppose you approve up to $600 in discounts, with campaign costs considered separately. At $10 per eligible ticket, that allows 60 discounted tickets.

That arithmetic only protects you if the setting controls tickets. A quota of 60 code uses could mean 60 orders. If each order can contain four discounted tickets, you've potentially authorized 240 discounted tickets and $2,400 in reductions. The word "use" needs a precise meaning.

Before you launch, establish whether the system counts a use when someone applies the code, completes payment, buys an eligible ticket or creates an order. Check what happens to a basket containing different ticket types. A code applied once can reduce several ticket lines, and the report's redemption count may not match the number of discounted admissions.

Also check when the quota is reserved. A buyer might hold tickets while paying, fail payment, retry or abandon the basket. You need to understand what happens near the limit, especially when several people check out at once. A promise of "the first 60 tickets" should agree with what checkout actually allows.

Write both limits in your campaign record: the maximum discounted ticket quantity and the maximum money you're prepared to give up. They answer different questions. A ticket limit controls how much admission inventory receives the offer; the money limit tells you the financial exposure.

For a percentage code, calculate against every eligible price. Ten percent off a premium ticket costs more than ten percent off general admission. If the system doesn't enforce a money ceiling, restrict eligible inventory or set a quantity you can afford even at the highest applicable discount.

Set the per-buyer rule separately

An overall cap doesn't tell a buyer how much they can purchase. Decide whether the offer is for one attendee, a pair of friends or a group, then make the buyer limit match that intention.

For the concert example, you might allow two discounted tickets per buyer within the 60-ticket allocation. That's different from allowing the same buyer to place two orders containing any number of tickets. Test a second purchase and a larger basket before assuming the setting enforces your rule.

Be equally clear about identity. A limit attached to an account is not necessarily a limit per human being. Someone may use another email address, and two people sharing a household may be genuinely separate buyers. Choose a control proportionate to the offer rather than asking your door team to investigate everyone's relationships.

If eligibility matters, decide how you'll establish it before payment. A members' offer needs a reliable membership check if you genuinely intend to exclude everyone else. A code that anyone can type isn't evidence of membership. Don't promise an exclusive audience based only on where you originally distributed the characters.

Avoid collecting personal information just because it might make the restriction stricter. Ask what you actually need to verify the offer and how the buyer will understand the process. A modest partner discount should not create a confusing application before someone can purchase a concert ticket.

Make the fallback decision now. If you can't reliably enforce the intended buyer restriction, simplify the offer, reduce the overall exposure or choose another way to provide the benefit. Relying on staff to catch excess purchases after payment creates an argument you could have prevented.

Decide which tickets and dates qualify

Start with the specific event, date, session and ticket type you want to support. Protect inventory that is likely to sell at the usual price unless you have a clear reason to include it.

A general admission offer shouldn't quietly include premium seats because both happen to appear in the basket. Equally, an ad saying "tickets" can mislead buyers if the code only works on a poorly identified category. Name the eligible ticket in the promotion and check it appears the same way at checkout.

Include bundles and extras in this decision. If a ticket package includes admission and merchandise, does the discount reduce the entire package or just the admission component? If the buyer adds merchandise separately, does the offer reach it? The cost can change substantially while the headline still says ten percent.

Look at other allocations too. Sponsor holds, complimentary tickets and group commitments still use capacity. A discount quota doesn't create extra room, and a seat held for another purpose shouldn't become available simply because the code has remaining uses.

If you want a cheaper initial allocation available to everyone, a separate release may communicate the offer more clearly than a public code. Our early-bird ticket pricing guide explains how to size that release. Choose the arrangement that matches the promise rather than making buyers hunt for a code everyone is meant to receive.

Write the stacking rule before buyers discover it

Stacking means using more than one price reduction on the same purchase. Your checkout might encounter a partner code, an existing group price, a cheaper release or another promotion. Decide which combinations you intend to allow, then test them.

Suppose a fictional $50 ticket already has a ten percent reduction, making it $45. Applying another ten percent to that reduced amount produces $40.50. Subtracting both percentages from the original price produces $40. Those are different outcomes, and neither should surprise the person who approved the campaign.

A fixed reduction also needs a clear order of calculation. Does a $10 code reduce each eligible ticket or the whole order? Does it apply before or after a percentage offer? Are taxes and mandatory charges treated separately? Use the actual checkout result in your cost model rather than estimating from the code's name.

For a straightforward first campaign, I'd keep combinations simple. Decide which existing offers remain eligible and make the exclusion visible. "Cannot be combined with another promo code" doesn't tell people whether it works on a group package or an early release, so name those conditions where they matter.

Test both orders of entry if the system allows multiple codes. Apply one, add the other, remove the first and change ticket quantity. Check the final payable amount and the discount recorded against the order. A correct first screen isn't enough if the result changes later in checkout.

If the platform doesn't support the combination rule you want, change the offer before announcing it. Don't publish a restriction that relies on someone manually discovering the purchase afterwards. The restriction should be clear to buyers and supported by the way you sell the tickets.

Set up the controls your platform actually provides

On Loopyah, our discount code help guide explains how to manage codes for a selected ticket type. You choose a percentage or fixed reduction and set a total quota and a per-user quota. You can also activate or deactivate the code.

Those controls let you limit an offer instead of sharing an unrestricted reduction. Use the total quota for the campaign's overall allowance and the per-user setting for the buyer rule you've decided. Check a realistic basket so you understand exactly how the quotas affect the tickets you're selling.

The guide doesn't specify every behaviour discussed here. Confirm the unit counted by each quota, interactions with other offers, treatment of cancelled orders and any deadline behaviour before relying on them. A setting's label is useful, but the purchase result is what your customer experiences.

You still own the commercial decisions. The platform cannot decide whether your partner should receive a larger allocation, whether Saturday needs a discount or how much reduction your budget can absorb. Agree those choices first, then configure the offer and verify that checkout follows them.

Keep a short record of the approved settings and the test purchase. That helps another person handle a support question without recreating your reasoning. It also gives you a useful reference when the next event comes around and someone wants to copy the previous code.

Use one approval record for the whole offer

Before anyone shares the concert code, put the decisions in one short record. Start with the audience and objective, then list the eligible ticket, discount calculation, total allocation, buyer allowance, campaign cost and closing condition. Add who owns the campaign and who answers buyer questions. This is enough to help the people doing the work agree on what you've approved.

For our fictional concert, the record would authorize 60 general admission tickets with a $10 reduction in organizer receipts per ticket. The overall reduction is limited to $600, and no buyer should receive more than two discounted tickets. Campaign spend has its own approved amount. Those figures must match the tested configuration before the partner receives the code.

Now imagine a second partner asks for the same offer. You have a decision to make. You could split the existing allowance between the partners or approve additional exposure because their audience is worth testing. Creating another code with the original quota without revisiting the budget would quietly double the authorized discount. Treat each new allocation as a budget decision, even when setup takes only a minute.

Record changes while the offer runs. If you increase the allowance, note who approved it, when it changed and what new evidence justified the decision. Preserve the earlier version so you can interpret purchases made under different conditions. Otherwise your final report can show spending beyond the original limit without explaining whether that was deliberate or a mistake.

The record should also state what counts as success. For example, you might require additional contribution after campaign costs, with no unplanned discounting of premium tickets. If the main purpose is earlier cash, record how early you need payment and what that timing is worth to your plans. Don't change the objective afterwards just because a different measure looks better.

Share each offer with the audience you approved

A private message doesn't make a reusable code private. Anyone who receives it can forward it, put it in a group chat or publish it on a deals page. Treat restricted distribution as one part of the plan, supported by limits you can afford.

Tell partners where they may share the offer and whether public posts are permitted. Include the eligible tickets, deadline, buyer allowance and the exact wording you want them to use. If they need different terms for a second audience, approve that separately rather than letting one code serve several unexplained purposes.

Separate partner allocations can make control easier when your setup supports them. One partner reaching its allowance then doesn't automatically consume the entire offer. Keep the combined allocations within the budget, though. Five codes with 60 discounted tickets each authorize 300 tickets, regardless of the name on your original campaign plan.

Use a simple naming convention that your team can recognize. The code should connect to a campaign and owner in your records without containing personal information. You don't need elaborate names that buyers struggle to type, especially if they're copying the offer from a phone screen.

If the purpose is to credit a promoter for sales, a discount isn't automatically necessary. With Loopyah's promoter links, promoters receive their own links and credited ticket sales. You can reward the distribution without teaching every buyer to expect a lower ticket price.

A promoter code and a promoter link can also answer different questions. One records a price reduction; the other records sales credited through that route. Agree commission terms and include their cost if you're combining them. Don't assume the discount replaces a separate obligation to pay the promoter.

Make the terms understandable where people see the offer

Buyers need the conditions that affect whether the offer is useful to them. Put the eligible event and ticket, reduction, quantity limit and closing condition in the promotion. Add the buyer allowance and important exclusions without hiding them behind a vague promise that terms apply.

For example, your concert offer might state that a named code takes $10 off eligible general admission tickets, up to two per buyer, within a 60-ticket allocation, ending at a specified local time or when that allocation sells out. Use this wording only after confirming the setup enforces those conditions.

Be clear about whether the deadline applies to starting checkout or completing payment. Name the time zone when people could reasonably read the offer elsewhere. Give your team a plan for buyers who are already paying at the cutoff, based on the behaviour you've tested and the terms you've published.

In the UK, CAP's guidance on significant promotional conditions explains why important restrictions belong in the advertising itself. Its closing-date guidance also addresses when dates can change. These are useful reasons to decide the rules before distribution instead of repeatedly extending an offer because sales were slower than expected.

Show prices in line with the requirements applying to your event. For covered US live-event tickets, the FTC's fees rule guidance explains upfront total-price disclosure and how restricted discounts affect displayed prices. A conditional code shouldn't make an unavailable discounted price look like the price everyone can pay.

Keep the event page, partner copy and checkout consistent. If the discount excludes a mandatory charge, the buyer should understand the actual saving and total price before committing. A headline percentage that appears to promise more than checkout delivers invites complaints even if your internal calculation was correct.

Test the awkward purchases before launch

Run through the intended purchase first. Then test the cases most likely to expose a misunderstanding: the wrong ticket, a mixed basket, an oversized order, a repeat buyer and a second offer. Check both the amount charged and the admission records created.

Use an authorized test route or a controlled purchase process for your platform. Don't create orders you cannot reconcile or accidentally consume the real allocation without accounting for it. Record whether test orders reduce the quota and whether removing them restores it.

Near the end of a test allocation, check what the next buyer sees. A clear explanation that the offer has finished is more useful than a mysterious invalid-code error. Your support response should explain the condition accurately without suggesting the buyer did something wrong.

Also review refunds. Establish whether a cancelled or refunded ticket releases another use, whether partial refunds affect the count and whether a code can then be reused. These details change how much discount the campaign may provide over its lifetime.

Send the approved offer to someone who didn't configure it and ask them to buy the intended tickets. Watch where they hesitate. If they can't tell which ticket qualifies or why the reduction differs from their expectation, fix the message or settings before a partner sends it to thousands of people.

Measure more than code redemptions

Keep an order record showing eligible ticket quantity, actual discount, receipts after relevant selling costs, refunds and any partner commission. Track total orders separately from tickets. Otherwise a change in basket size can look like a change in how many buyers your campaign attracted.

For exposure, record who was offered the code where you can do so reliably. An email campaign can have a defined recipient group; a partner's public post usually has a less certain audience. Don't calculate a precise redemption rate using follower count as if everyone received and read the offer.

Links help explain the route people took. Google documents how campaign parameters identify referring campaigns in Analytics. Use consistent campaign names if you're adding those parameters to your own measured links. A forwarded code and an original campaign link can travel separately, so expect some disagreement between the two reports.

Loopyah's ticket sales reporting shows sales by source. Use that information alongside the offer's purchases and costs to understand distribution. Source reporting tells you where credited sales came from; it doesn't establish what the same buyers would have done without the discount.

Review code sales alongside full-price sales, later purchases and refunds. A launch-day surge may include people buying earlier than planned. That can help cash collection, but it isn't the same as increasing final event revenue. Keep the immediate result and the final result in your notes.

Compare the result with a credible alternative

The hard question is how many purchases the code added. When possible, compare similar eligible groups, with one receiving the offer and one receiving your usual promotion at the same time. Decide what you'll measure and when you'll stop before seeing which version looks stronger.

The US National Institute of Standards and Technology recommends defining an experiment's objectives before choosing its design. For your event, that means stating whether you're testing additional ticket contribution, earlier purchases or access to a new audience. Those objectives can produce different decisions from the same sales report.

Keep the comparison practical and fair. If you give one group a completely different campaign and another group no communication, you're comparing those whole approaches. You can't claim that the price reduction alone caused every difference. Record other changes, including availability and competing announcements.

If people share the code between groups, acknowledge that limitation. Don't quietly remove inconvenient buyers from the comparison. For small audiences, you may get too few purchases to support a confident conclusion. Repeat a controlled offer rather than treating a handful of orders as a dependable improvement.

When a fair comparison isn't available, use scenarios. For the fictional concert, 60 discounted tickets leave $1,800 after the stated attendee costs. If all 60 buyers would have paid the usual price, the discount reduces your result by $600 before campaign costs. If all are additional, their $1,800 helps cover those costs and the event's fixed bills.

Most real outcomes will sit between those assumptions. Estimate a plausible range using your sales history and the campaign's audience, explain the uncertainty, and avoid calling every redemption an additional sale. That gives you a more useful decision than a precise return figure built on an unsupported assumption.

When you review the result, check the ordinary sales forecast too. Suppose the concert was already expected to sell out. A discounted buyer might simply take a ticket that a later full-price buyer would have purchased. The attendee is new to your database, but that does not mean the event gained another paid admission. Include the likely loss of the later purchase when you judge the offer.

The reverse can happen on a quiet date with plenty of room. A new buyer who would otherwise stay home can add useful money towards bills you've already committed to paying. The same discount can therefore be sensible on one performance and expensive on another. Keep results separated by eligible date and ticket type so the strong sales of one session don't justify discounting every session next time.

Decide what happens when the offer ends

Assign someone to watch the allocation, questions and discount total while the campaign runs. Decide who can deactivate the code and who can authorize an extension. Your team should know the answer before an unexpected public share sends purchases towards the cap.

If the code reaches people outside the intended audience, check the published terms and affected orders before deciding what to do. A forwarded code is not, by itself, proof of dishonest buying. Stop further exposure through supported controls where appropriate, and handle existing customers consistently with the promise they actually received.

Also decide how you'll answer someone who bought before the code appeared. You don't need to invent a new refund policy in the middle of a campaign. Review the terms already offered, agree who can handle an exception and prepare a clear explanation of the promotion's audience and timing. If your team gives a retrospective adjustment, record its cost with the campaign. Otherwise the report understates what the offer cost while support deals with the consequences outside your sales figures.

After the planned window, record whether you'll repeat, change or retire the offer. Compare the money retained, audience reached, operational work and later sales with your original objective. Keep the approved terms and results together so the next campaign starts with evidence. Before you copy that code, confirm that the new event has the same capacity, costs and reason to discount.