How to stop two promoters claiming commission on the same ticket sale

Two promoters send you the same buyer's name. One says they introduced the event. The other says the buyer used their link. Both expect commission, and your team is trying to settle the argument while the next event is already on sale.

The way to prevent this is to agree which recorded sale earns commission, use one payment record for each eligible ticket, and define how genuine errors are investigated before anyone starts promoting. A discount code, a social message and a ticket order can all tell you something useful. They shouldn't each create another commission payment for the same admission.

Start with the attribution your ticketing platform actually supports. Attribution means assigning credit for a purchase. If the platform already records promoter sales and pays commission, use that record for routine payments. Keep a small exception process for faults and disputed claims, rather than asking staff to reconstruct every buyer's journey after the show.

This guide is for event businesses paying referral commission on paid tickets. We'll cover overlapping links, codes, group purchases, missing records and corrections, including a fictional reconciliation you can follow ticket by ticket. Someone sharing production costs or taking a share of the show's profit needs a broader commercial arrangement.

Decide what the payment is rewarding

Before choosing a tracking rule, explain the job you are buying. Are you paying for tickets purchased through a promoter's assigned route? Or have you also promised a fee for introducing a business, producing content or hosting a community? Those can all be valuable contributions, but they create different payment obligations.

Say Maya posts a video about your event. Jordan later shares a ticket link in a group chat. A buyer watches the video, opens the link and purchases. Maya helped the buyer discover the event. Jordan supplied the recorded purchase route. If you promised both people the full sales commission whenever either could show involvement, you've created the overlap yourself.

For a referral programme, my preference is a single commission assignment you can check per eligible ticket, following the agreed platform mechanism. You can still pay Maya a separately agreed video fee. The video then has its own brief, delivery standard and cost, so you can see what the whole campaign costs without pretending every payment represents another ticket sale.

You may deliberately choose to divide one commission between partners in a system that supports it. If so, agree the split and total payment beforehand. Two people sharing a $5 commission is different from each receiving $5. Don't offer a split arrangement unless the payment process can implement it and both partners understand the amount available.

Be particularly careful with the word "introduction". It might mean the first time a buyer heard about the event, the first recorded visit, or a personal introduction to someone booking a group. Those aren't interchangeable. You cannot reliably reward an unobservable first encounter using a report that records only completed orders through assigned links.

Work out the affordable payment separately. Our guide to setting event promoter commission explains how to test the rate against ticket prices, discounts and attendee costs. Here, the question is who receives the agreed amount when claims overlap. A clear attribution rule won't make an unaffordable rate sustainable.

Choose one record that controls routine commission

Write down where your accounts team should look when a promoter asks what they earned. That should be the platform's promoter sales and earnings record where the platform handles those jobs. A collection of messages, screenshots and self-reported totals shouldn't compete with it as another routine payment list.

This doesn't mean the system can never be wrong. It means everyone starts with the same recorded transactions and has a defined way to question them. If a promoter believes a sale is missing, they raise a case about that sale. They don't submit a replacement total which finance adds to the recorded balance.

Identify the unit being paid. A commission per ticket needs eligible ticket quantities, even when several admissions share an order. A commission per order needs order counts. A percentage needs the agreed eligible value. People can disagree about attribution when the real problem is that one is counting purchasers and another is counting admissions.

Use stable transaction references. The event identifier and order reference establish which purchase you're discussing. If an order contains several products, include the relevant ticket or order-line reference where available. A buyer's first name is too ambiguous to establish whether two claims concern the same transaction, particularly on a busy recurring event.

Then distinguish the original assignment from its current payment status. A ticket might be credited to Maya but later refunded. It remains part of the history of Maya's sales, while its payable commission changes according to the accepted refund terms. Creating another promoter assignment because the ticket changed status would confuse two separate decisions.

Name who owns exceptions and who can approve a financial correction. Your customer service team can gather the order reference and reported fault. A designated manager can assess the evidence and check the supported remedy. Finance then sees the approved outcome rather than interpreting several versions of the story.

Keep marketing credit separate from money owed

A marketing report can reasonably describe several contributions to one purchase. Your announcement introduced the event, a promoter answered a question, and an email reminded the buyer of the deadline. That is useful when deciding what to repeat. It doesn't create several independent ticket revenues.

A commission agreement answers a narrower question: which recorded transaction qualifies for this person's agreed payment? Keep that decision distinct from a later attempt to understand all the activity that helped the buyer. Otherwise every campaign review can reopen settled commissions whenever someone finds a more flattering attribution view.

Google's explanation of attribution in Analytics describes models that allocate conversion credit to interactions in a customer's journey. That is a reporting function. A channel receiving credit in an analytics report isn't, by itself, evidence that your promoter agreement promises a payment to the person associated with it.

You might use a marketing view that credits an early announcement while your referral arrangement pays the person recorded against the completed purchase. Neither result has to be dishonest. They answer different questions. Your comparison of first-click and last-click ticket attribution can help the marketing team interpret those differences without rewriting the payment terms.

Keep buyer feedback separate too. "How did you hear about us?" can reveal that a local community matters more than your click reports suggest. A buyer naming Maya in that answer doesn't automatically prove that Jordan's recorded commission is incorrect. The buyer may remember the introduction accurately and still have completed the purchase through Jordan's agreed route.

Don't respond by dismissing introductions as worthless. If useful discovery work consistently goes unpaid under your offer, change how you commission that work for the next event. You could buy a specific content deliverable or choose different partners. Honour this event's accepted sales terms while learning whether the arrangement rewards the work you actually need.

The same applies to additional sales. A recorded referral doesn't establish that the buyer would otherwise have stayed home. You can investigate that when choosing future partners and budgets. You shouldn't add a new requirement to prove the sale was genuinely additional after someone has already earned commission under the agreed rule.

Expect buyers to hear about the event in several places

It is entirely plausible that two promoters both influenced a purchase. The mistake is trying to turn that possibility into two full claims on the same commission without an agreed basis. Buyers move between conversations, social posts, search results and ticket pages while deciding what to attend.

In Loopyah's US event attendee survey, fielded through Pollfish on 11 November 2025 with 500 respondents, people could select up to three ways they usually find upcoming events. Social posts or ads were selected by 65%, word of mouth or friends by 56.4%, search engines by 37.6%, and influencers or creators by 15%.

Source: Loopyah Event Attendee Survey, Q6, US sample of 500, November 2025. These are four selected answer options, measured as shares of respondents. People could select up to three, so the bars aren't parts of one whole. The survey doesn't measure promoter overlap, ticket attribution or sales caused by each source.

That last limitation matters. You cannot calculate your likely duplicate commission claims from this chart. What it does show is that people report using several kinds of discovery source. A payment policy built around the assumption that every buyer encountered exactly one promoter is asking more of the evidence than it can deliver.

Think about what your policy encourages. If you pay whoever submits the most convincing story after the event, you reward time spent chasing buyer confirmations. If you pay whoever posts a code publicly just before checkout, you may encourage code distribution to people already planning to buy. If your system credits an assigned purchase route, explain that route clearly and help promoters use it correctly.

No rule makes every contribution observable. Choose a supported mechanism that is understandable, affordable and suited to the work you're commissioning. Then review whether it attracts the right partners. You need a workable commercial arrangement, rather than a promise to discover every conversation which helped every person decide.

There is a human benefit here too. A promoter who knows exactly how sales are credited can decide whether the offer suits them before doing the work. They shouldn't have to discover at settlement that a buyer's recollection, another partner's code or a private arrangement with your sales manager takes priority.

Settle the relationship between discount codes and promoter links

A discount code changes an offer. A promoter link identifies an assigned referral route. A platform may connect those functions, keep them separate, or support only one of them for commission. Verify the actual behaviour before writing terms which assume a code automatically establishes who should be paid.

Imagine Jordan's purchase route and a code associated with Maya appear on the same order. The code could be a widely shared price offer rather than proof that Maya referred this buyer. Conversely, an exclusive code programme on another system might deliberately use the applied code as its payment evidence. The right answer depends on the agreed mechanism and what the system recorded.

Don't decide which evidence takes priority by intuition after the sale. If the platform's promoter mechanism controls commission, explain that a separate discount doesn't independently create another promoter payment. If you operate a supported code-based arrangement elsewhere, document what happens when a code and a tracked referral disagree. Have the provider confirm what is technically possible before offering it.

The same caution applies to first-click and last-click promises. Before saying "the last promoter always gets the sale", verify that this is how the actual promoter system handles successive links, returning visits and checkout. A generic marketing attribution tutorial isn't documentation of your ticketing platform's commission logic.

Google's campaign URL guidance explains that campaign parameters identify referral traffic in Analytics. Adding a promoter's name to a campaign tag can help describe a visit. It doesn't, on its own, create a commission entitlement or replace the platform's assigned promoter link. Keep the original supported referral route intact unless the provider confirms the change is safe.

When distributing links, identify the promoter and event clearly in your own records. Provide the exact approved destination and ask them to use it consistently. If they need a short link or a profile-page button, test the finished published route, rather than assuming that a correct destination copied into a message guarantees a correct redirect later.

Also separate discounts from what you can afford to pay. A code may reduce the ticket amount while commission still follows the assigned sale. Run the resulting buyer price and organizer proceeds through your budget before approving the offer. Resolving the duplicate claim won't repair a promotion that gives away too much ticket income.

Use Loopyah's promoter records for the work Loopyah handles

On Loopyah's promoter tools, you set one commission rate for the event and invite promoters to accept it. The rate can be a fixed amount per ticket or a percentage. Once the first promoter accepts, the event's terms lock. Check the economics and explain the offer before that acceptance happens.

Each promoter shares their own link or invites their connections. Loopyah records the credited sales and shows promoter sales and earnings in the event dashboard. Commission comes from the organizer's share and is paid to the promoter as their own payout. Routine settlement shouldn't require your team to count screenshots and then transfer the same commission again.

The useful operational step is to make that supported record the starting point for payment questions. Give promoters the correct event link and explain where they can see their sales and earnings. Use the guide to hiring promoters for the setup, rather than maintaining a second set of instructions based on a guessed tracking mechanism.

The public product guidance doesn't specify every case involving several promoters' links, a returning buyer, another device and a separately applied discount. It also doesn't establish that an organizer can reassign a completed sale or reverse an already paid commission. Confirm those cases with Loopyah before promising a custom rule or correction.

That's an implementation question worth settling early. Ask about one concrete journey, including the event, links and order reference, instead of asking whether tracking is "accurate" in general. You want to know which record the system creates, what each side can inspect and what supported remedy exists if a fault is confirmed.

For refunds before payout, Loopyah describes reducing the organizer's and promoter's shares proportionately. Keep that separate from correcting who received credit. A refund changes the money retained on the sale. A referral correction changes its assignment. Don't promise that one automatically performs the other, or that the documented pre-payout handling applies to every later situation.

If you have separately commissioned creative work, keep its invoice and payment outside the automated ticket commission calculation. That avoids asking the promoter dashboard to explain a fee for a video it was never intended to calculate. You can still combine those costs in your internal event budget when assessing the partnership's total value.

Handle group orders at the unit the agreement pays

Group bookings make duplicate claims harder because several attendees can share one purchaser and order. Maya may have spoken to one friend, Jordan to another, and a third person pays for everyone. An attendee list can then make several people appear to have sold the same group.

Start with what the transaction actually records. If the platform assigns the order's eligible tickets to one promoter, use that supported assignment for routine commission. Don't divide the group according to who knows each attendee unless you've agreed such a method beforehand and have a supported way to apply it.

Here is a fictional USD example, separate from Loopyah's fees or product calculations. An order contains four eligible admissions at $50 each. The agreed referral payment is $5 per eligible ticket, and the recorded assignment is Maya. The order therefore carries $20 commission. It doesn't carry $5 because there is only one purchaser, or $40 because Jordan also knows the group.

If one admission is fully refunded, our example's accepted terms remove its $5 commission. Three eligible admissions remain, carrying $15. Keep the original order and the specific refunded admission connected so the same change doesn't get applied once against Maya's list and again against a separate group-booking sheet.

Now distinguish a refund from a ticket transfer. A buyer giving an admission to another friend doesn't automatically create a new paid sale. The new attendee's relationship with Jordan isn't grounds to pay another referral commission on the same purchase. Follow your platform's actual transfer and sales records rather than counting every new name as new revenue.

Repeat purchases need their own treatment. If the same buyer later purchases additional eligible tickets, that is a separate transaction which may carry its own recorded assignment. Don't merge it with the earlier order just because the email address matches. Equally, check for a replacement or exchange before treating an apparent second order as genuinely additional paid admissions.

Your ticket allocation arrangements with sales partners may involve a different selling model, including separate inventory or remittance responsibilities. Keep those arrangements distinct from referrals through one official checkout. A partner returning an allocation report shouldn't also receive referral commission on those tickets unless the commercial terms deliberately provide for both.

Make the selling window and missing-record process explicit

A link may still be circulating after a promoter's agreed campaign ends. Someone who saw the event during launch might return much later, and a group organiser might delay buying until everyone confirms. Decide how your accepted terms and supported setup handle those purchases before announcing a commission cutoff.

Write an actual date, time and time zone wherever a selling or claim deadline matters. Explain whether the date refers to the purchase, the qualifying referral activity or the submission of an error report. Those are different events. "Until Friday" won't answer a disagreement involving a buyer in another country and a purchase just after midnight.

Check technical enforcement separately. If the platform continues recording and paying promoter sales after your intended deadline, a sentence in your brief won't change its behaviour. Ask what supported control exists and how accepted terms apply. Don't instruct staff to remove credit manually when neither the tool nor your agreement supports doing so.

For a sale with no recorded promoter, avoid defaulting to whichever person asks first. Missing attribution might reflect an untracked purchase, a broken route or a customer who bought directly. Record what is known, investigate the reported fault and keep the sale unassigned unless your agreed process establishes an approved correction or separate payment.

A buyer's memory can help the investigation, but don't turn the buyer into your settlement referee. Ask only a relevant, optional question if you need it and can handle the answer appropriately. The buyer shouldn't have to choose which promoter gets paid before receiving their ticket, refund or other service.

Where a technical fault is suspected, capture when it was reported and which published link was affected. Distinguish a verified fault from a possible one. If you fix a redirect today, that establishes the current route works. It doesn't prove how every earlier visitor travelled or which historical orders should be reassigned.

Give promoters a reasonable opportunity to report errors under the terms you've agreed. An operational claim deadline isn't automatically a legal limit on their rights. For the wider drafting decisions, the Australian government's guide to preparing a contract covers payment, variations and disputes. Have the arrangement reviewed for your jurisdiction, particularly where deductions or recovery of paid money may be involved.

Resolve a competing claim without paying it twice

When two claims concern the same sale, open one case for that transaction. Ask each promoter for the order reference or enough information for an authorised staff member to locate it. Then identify the affected eligible tickets and amount. You can't assess whether a correction is proportionate if the claim is just "a few of my people bought".

Preserve the original assignment, sale status and accepted terms before investigating. Gather the relevant link or code, the reported purchase time and evidence of a fault. Keep statements attributed to their source. "Maya says the buyer used her link" is a report to investigate; it isn't the same record as the platform showing that assignment.

Check whether the apparent overlap is really a duplicate. Two promoters may have the same buyer name but different orders. A group might have made an additional purchase. One screenshot might show a pending checkout and another a completed sale. Identify the actual transactions before deciding that anyone is mistaken or behaving badly.

Explain the result in language tied to the agreed rule. For example: the completed order records Maya as the promoter; Jordan's message shows an earlier conversation, which doesn't qualify for a second sales commission under these terms. That acknowledges Jordan's evidence without pretending it proves something the offer didn't promise to pay for.

If you confirm a technical error, check the supported correction with the provider. A staff member editing a local worksheet hasn't changed the platform's payment record. You need to know whether a correction is possible, who can authorise it, and whether money has already been paid. Record the approved action and verify its effect afterwards.

If reassignment is unavailable but you agree a separate payment, label it accurately and budget it as an additional cost. Don't describe the original commission as removed unless it has actually been reversed through an authorised process. The accounts record should show what each person received and why, even when the commercial resolution costs more than your preferred attribution outcome.

Keep the rest of the promoter's account moving under the agreed payment terms. A disagreement over one admission shouldn't turn every other completed sale into an unresolved case. Your manager should know the specific amount affected, the next action and the person responsible for resolving it.

Share enough evidence to explain the decision

A promoter needs a useful explanation, but that doesn't require sending them another partner's customer list. Where possible, use the order reference, relevant ticket quantity, assigned promoter, status and commission calculation. Redact unrelated personal messages and payment details before sharing evidence through an approved channel.

For UK personal-data handling, the ICO's data-minimisation guidance says information should be adequate, relevant and limited to the purpose. The page is under review following UK legislative changes. Apply the requirements relevant to your business; don't treat a commission argument as permission to distribute all the attendee information you hold.

Access matters as much as content. A shared file which every promoter can open creates a different exposure from an authorised manager checking a single order. Use the permissions your platform already supplies. Where you need an exception record, restrict it to the people doing the investigation and set retention according to your legal and business obligations.

Reconcile unique tickets before authorising extra payments

Here is a complete fictional example to show where duplicate counting enters the accounts. All money is USD, the payment arrangement is invented, and the figures aren't Loopyah rates or customer results. Assume a separately administered programme which pays $5 for each eligible ticket and permits reviewed adjustments before its scheduled payment.

The original platform assignment records 40 paid tickets for Maya and 30 for Jordan. Another 30 paid tickets have no promoter assignment. That is 100 unique paid tickets in total. Maya's initial commission is $200 and Jordan's is $150, making $350 together. Unassigned tickets don't create promoter commission in this example.

Jordan then submits ten claims already included in Maya's 40. Those claims concern existing tickets, so they don't increase the event total to 110. If finance simply adds $50 to Jordan's statement, the same ten admissions receive two full commissions and total commission becomes $400 instead of $350. That is a payment error under our fictional single-assignment terms.

After investigation, eight claims remain with Maya because the agreed record is correct. Two are confirmed assignment errors. Assume, only for this separately administered example, that the provider supports the correction, it is properly authorised, and no commission has yet been paid. Moving those two assignments leaves Maya with 38 and Jordan with 32. Total assigned tickets remain 70, and commission remains $350: $190 plus $160.

Next, three of Maya's 38 and two of Jordan's 32 tickets are fully refunded. Under our fictional terms, those five tickets no longer earn commission. Maya has 35 eligible tickets and $175 commission. Jordan has 30 and $150. The final eligible promoter total is 65 tickets and $325. The 30 unassigned tickets are unchanged, so 95 paid tickets remain across the event after those five refunds.

The checks are simple enough to state aloud. Seventy assigned tickets before refunds plus 30 unassigned equals 100. Two corrected assignments move between promoters without adding tickets. Five refunded admissions reduce the remaining paid total to 95 and promoter commission by $25. Each unique eligible admission has one assignment and one $5 payment obligation.

If money had already gone out, the correction would need a further payment and recovery analysis. You couldn't simply relabel $190 as unpaid after Maya had received it. Our worked example deliberately assumes correction before payment so you can check every calculation. Confirm the actual provider process and contractual position before attempting any later adjustment.

Prevent claims that your brief accidentally encourages

Promoters need a brief that tells them how to earn, which link to share and how to raise a problem. Include a plain explanation that the recorded eligible sale controls routine commission and that a discount or buyer introduction doesn't independently create another payment unless the accepted terms explicitly provide for it.

Show a mixed case before launch. Ask what happens if Maya introduces someone who later buys through Jordan's route, or a buyer uses a shared discount while following another promoter's link. Confirm the supported answer, then explain it consistently. If you can't answer those ordinary cases, the offer isn't ready to distribute.

Set limits on promotional claims as well. Don't let someone imply that their link creates a special discount, priority entry or refund right when it doesn't. A buyer who thinks they must name a promoter to receive their ticket can become caught in a payment dispute they never agreed to participate in.

For US-facing endorsements, the FTC's guidance on endorsements and affiliate relationships explains that relevant financial connections may need clear disclosure. Include appropriate disclosure in the promotional brief. The fact that commission is tracked automatically doesn't remove the need for buyers to understand a paid recommendation where disclosure is required.

Watch for patterns without treating every overlap as misconduct. Repeated broken routes might reveal a setup problem. Several unrelated buyers applying a publicly posted code might reveal that the code is measuring discount use rather than the promoter's personal introductions. A late burst of manual claims might show that your original explanation wasn't clear enough.

Investigate the conduct before deciding what to change. If a promoter is breaching the agreement, follow the agreed and lawful process for addressing that behaviour. If the arrangement itself invites confusion, improve the next brief and setup. Neither situation justifies silently removing valid earnings from unrelated tickets.

For the next event, evaluate the partner on the work you wanted: relevant paid sales, accurate promotion, manageable costs and a useful audience relationship. Keep disputed claims in that review, but don't reduce the whole assessment to which person argued most forcefully over the final statement.

Give promoters a payment explanation they can actually use

The accepted terms need a short companion explanation which someone can understand while preparing a post or checking their balance. It should reflect the real agreement and platform, without quietly adding restrictions which the promoter never accepted. Ask your manager to compare the two before distributing the brief.

For a programme using supported promoter attribution, the explanation could say that commission is calculated from the eligible ticket sales assigned to the promoter in the platform. It should identify the event, the agreed payment unit and rate, where earnings appear, and how to report a suspected missing sale. Put the actual details in those sentences rather than sending people a generic policy with empty fields.

Then explain the overlap case directly. A buyer may hear about the event from more than one person. That alone doesn't create another commission on the same ticket. If a promoter believes the recorded assignment is wrong, they should send the order reference and relevant evidence to the named contact, who will investigate under the accepted terms and confirm what correction the system supports.

Don't promise an outcome you can't guarantee. Saying you will investigate an error is different from promising you can transfer any completed sale to another promoter. If there is a separate compensation decision, explain it as such. This helps the promoter understand why a confirmed technical problem might need a different resolution from a simple correction in their sales record.

A useful response to a rejected duplicate claim names the transaction and reason. For example, you can explain that an order's admissions already have an assignment under the agreed record, that the supplied message establishes an introduction rather than a qualifying payment record, and that no additional commission has been approved. Include the route for challenging a factual mistake. Avoid an unexplained screenshot with the instruction to accept it.

For an upheld claim, explain what changed and how the money will be handled. The promoter needs to know whether a supported assignment correction has completed, whether a separate payment was approved, or whether a provider investigation is still open. An encouraging message that says everything is sorted can create another argument when the dashboard still shows the original amount.

Keep those communications with the case. If the accounts team receives an invoice next week, they should be able to tell whether it relates to an approved extra payment or a commission already handled through the platform. That check is particularly useful when different people manage partner relationships and pay invoices.

Stop a resolved claim returning as a new invoice

Before paying an exception, search the existing case records for its event and transaction references. Check whether the original platform commission has been paid, adjusted or left unchanged. Then record the additional payment's own reference and approval. This is a narrow check on unusual payments, rather than a second manual ledger for every routine promoter sale.

Make the distinction visible in the event budget too. If you paid a goodwill amount without changing the original attribution, total acquisition cost has increased. That may be a reasonable relationship decision, but hiding it inside another promoter's sales count makes the next event's commission offer harder to price honestly.

When the case closes, send the outcome to the relevant promoter and the staff who authorised payment. Record any unresolved provider action separately. A case can be commercially settled while a technical investigation continues; keeping those statuses clear prevents someone treating a still-open support ticket as permission to pay the same amount again.

Test the ordinary purchase and the awkward ones

Before promoters start, check the journey the buyer will actually take. Open the link from its published location, verify the correct event and inspect the resulting supported attribution after an authorised test purchase. Follow your platform's procedure for test orders and refunds so you don't leave unintended admissions or payments behind.

The test should include ordinary single-ticket sales and the cases your brief promises to handle. If discounts are part of the campaign, check the combined purchase route and offer. If group bookings matter, inspect a multi-ticket order. Record what the tool actually does and confirm unresolved cases with the provider before making claims about them.

Don't perform live commission experiments casually. A real purchase may create a real payment, notification or tax record. Arrange a provider-approved testing method and know how its cleanup works. The purpose is to verify your offer, not create a second set of unexplained transactions while trying to prevent the first.

Keep a short record of the approved setup, accepted rule and test outcome with the event. Give the person handling promoter questions access to that record, so they can answer consistently when the campaign gets busy. A new staff member should be able to explain the payment without finding the colleague who negotiated it.

At settlement, start with the recorded sales and earnings. Check open exceptions for the same transaction references before authorising any additional payment. If a claim concerns an already credited ticket, resolve the assignment or separately agreed compensation explicitly. The next action is to inspect that sale, establish the supported remedy and record what was actually paid.