Codes as evidence, and the question they leave open
What a code can and cannot show belongs to other pages, and this guide borrows only their conclusions. A Discount CodeA code a customer enters at checkout to receive an offer, also used to identify sales from a creator, partner or channel that links cannot capture. is an offer to the customer and a label to the business: issued to one partner, it marks the orders that partner's audience placed. The creator tracking guide reads codes beside links because a code picks up some buyers who never tapped through and bought later by another route, and it warns that codes leak, so redemptions indicate rather than count. The guide to measuring offline media treats a code as a response mechanism that measures a floor, contaminated by deal sites, and the podcasts and audio guide gives each show its own code so that shows can be compared with each other rather than trusted on either count alone.
Where code sales and tracked sales sit on the ladder of proof is settled as well: the hierarchy of evidence files both under attributed figures, evidence of contact rather than of need; the coupon diagnosis applies that ranking to voucher partners; and the coupon test in the reporting and incrementality guide is the step up.
None of that is a payment rule. Those pages say what a code is worth as evidence; they leave open whether an order made with a partner's own code and no tracked click earns that partner commission, who is paid when the code belongs to one partner and the last click to another, and what a leak does to that credit. The discount code request SOP comes closest. It asks the requester, before the code exists, whether its use will be credited through commission, a fee or nothing, and it places the code beside the click credit rule rather than in its place. The rest of this guide turns that answer into a rule a partner can check. The affiliate measurement hub frames the wider questions of credit, partner quality and incrementality that the rule sits inside.
When a partner's own code should earn commission
Code-only credit is a programme rule. The business decides it, writes it into the terms and applies it in its own validation; the platform records what it is set up to record. Whether a particular network or platform can accept an order that arrived without a click is a question for the business to put to its network before the rule is promised to any partner.
Start from the code type. The SOP sorts codes into public codes any customer or partner may use, codes tied to one recipient, and single-use codes, with the service team's batches tied to no partner. Only a code tied to one partner names that partner, whether it is one shared code or a set of single-use codes issued to them, so only that kind can earn code-only credit. A public code identifies nobody, and a goodwill code from the service team's batch belongs to no partner at all; an order carrying either, with no affiliate click, earns nothing under this rule. The exclusive codes that the key partners guide ties to each partner are the natural candidates, alongside the codes issued to podcast hosts, newsletters, communities and creators paid on commission.
An order then earns code-only credit when four conditions hold:
- The code was issued to that partner and has a register line naming them, written before the code existed.
- No affiliate click falls inside the lookback windowThe time after an ad interaction in which a conversion can still be credited to it. that the terms already state for clicks. Where one does, the click rule decides, as the next section sets out, so both kinds of credit run on one clock.
- The code was live and the order met its eligibility: placed before the end time, on the products and customers the code was issued for.
- The order survives validation on the same grounds as a clicked conversion, so returns, cancellations, duplicates and test orders are excluded.
Then choose the route, because the SOP's three answers fit different partners. Commission fits a partner already in the programme whose audience buys through its code as well as its link, such as a podcast host or a newsletter paid per sale. A fee fits work paid for whatever the sales, and a nothing answer fits a code issued as a courtesy where the business never meant to pay on use. Where the route is commission, state the rate beside the outcome it pays for, as the terms tutorial asks. The Commission RateThe share of a sale's value paid to the affiliate or partner credited with it. entry reads rates by partner type, product group and customer status rather than as one figure, and a code-only order is an outcome of its own that may earn the same rate as a clicked order or a different one.
Creators on a hybrid deal sit across both routes. The comparison of influencer and affiliate marketing gives each hybrid creator a unique link and code and says the deal needs attribution rules for a buyer who also clicked an affiliate site. This rule supplies the commission half of that; the fee half belongs to the creator agreement.
When the code and the click point at different partners
When an order carries a tracked affiliate click, the click rule decides it. That is what the SOP means by placing the code beside the rule: the code does not override the click, and the programme does not run a second credit system for orders with codes. The attribution and deduplication guide lists the rules a programme can choose from, from last affiliate click to split commission and cross-channel last click, and the DeduplicationRemoving double counts when one conversion is reported by more than one source. rule that removes claims made by other channels applies to orders that carry a code and a click exactly as it does to the rest. Decide whether the channel overrides that can remove an affiliate click's credit also remove code-only credit, and write the answer down; otherwise a code could earn on an order where a click from the same partner would have been overridden.
What the code can do is say who belongs in the protected group. Under last click with protection, one of the options the attribution guide offers, the latest click keeps the order unless a partner who came earlier is in a protected group. Extend that protection to the owner of an exclusive code on any order that carries the code, apart from the leaked orders set out below. A later click from a partner outside the group then does not displace the owner: a listener who heard the host's code, later read a review and clicked through from it, still credits the host. The guide describes the protection for an earlier partner's click, so extending it to the code on the order is a choice the terms must state. The click rule has still decided the order, with an option the programme already had; the code has only told it which partner on that order is protected. Code-only credit, from the section above, applies only where no click exists for the rule to decide.
The coupon clause covers the other side of that order. The recruitment, compliance and fraud guide ties every code to its recipient and pays no commission when a partner's tracked order carries a code that went to someone else, so the review site whose click came last earns nothing on an order carrying the host's code, however the protection is set. The open question was only whether the host is paid, and the protected group answers it.
Two cases need a line of their own. The first is a click from another protected partner, with one member of the group holding the click and another holding the code. The coupon clause already leaves the clicking member nothing, and the code's protection keeps the order with its owner; say so in the terms before the first dispute arrives, because the attribution guide names defining the protected group fairly as the main risk of the rule.
The second is the leak, and it is settled here once. An order that reaches the checkout through a voucher siteAn affiliate partner that publishes discount codes and offers, often reached by shoppers who have already chosen and search for a code at checkout. or a browser extension click and carries another partner's exclusive code, with no earlier click from that partner, fits the pattern the coupon diagnosis traces to a code published on a deal page. Treat it as leaked and pay nobody. The voucher or extension partner earns nothing under the coupon clause, and the code's owner earns nothing either, because the order came through a deal page rather than from the owner's audience. The guide to running promotions through affiliates handles the same case in its seed retailer's spring sale, where orders tracked to a voucher site with a blog's exclusive code earn no commission.
What a leaked code does to code-only credit
The voucher-click case pays nobody, but a leak also reaches the orders the rule does pay on. Once an exclusive code sits on a deal page, some shoppers read it there and type it at the checkout without clicking anything. Their orders carry the owner's code and no affiliate click, which is exactly how the owner's own listeners and readers look, and code-only credit pays the owner for them. Validation has no click on these orders to tell the two groups apart, so the limits have to come from how codes are issued and withdrawn.
Goodhart's law explains why this matters more once code-only credit is paid. A measure that becomes a target attracts effort, and some of that effort moves the number without moving the outcome. Code redemptions were an indicator while nobody was paid on them. Once a partner earns on orders that carry its code and no click, the partner gains from the code travelling further than its audience, whether or not it does anything to spread it. The rule needs limits and a guardrail beside it:
- End times. A short-lived code gives a leak less time to run, and the creator tracking guide counts short-lived codes among the habits that help.
- First-order eligibility. A code limited to a first order, another habit that guide names, is refused to returning customers wherever they found it.
- Withdrawal and replacement. When an owner's code turns up on a deal page, follow the SOP's answer for a code found on a voucher site: look the code up in the register, show the owner the evidence and ask how the code spread before drawing conclusions about the partner. Then withdraw it and issue a new code if the offer has time left. Code-only credit on the old code ends with the withdrawal, because the code no longer works; orders that came through the deal site with it fall under the leak rule above.
- Single-use codes. Where a partner can hand codes out one at a time, to a club's members or a newsletter's subscribers, each code works for one order only, however far a copy travels.
The register, single-use batches and rejections at validation are the coupon diagnosis's first fix and the SOP's routine, and this guide does not repeat them. The recruitment guide's fraud table lists codes appearing where they were never issued as the signal of code hijacking, which belongs to the enforcement ladder in the terms rather than to this rule.
For the guardrail, read code-only orders against when the partner actually published. The offline media guide reads broadcast response around airings and notes that most podcasts lack the spot-level timing that method needs, so what follows is this guide's own coarser reading, not that method: code-only orders that follow a show's episodes or a newsletter's sends behave like that partner's audience, while a steady stream with no tie to anything the partner published points towards a deal page. It is an attributed reading, low on the ladder of proof. The hierarchy of evidence matches the proof to the decision, and moving one partner to single-use codes can be reversed and needs less proof than a judgement on what the partner adds, which remains the coupon test's job.
Recording code credit so validation, the platform and finance agree
Code-only credit does without the record that makes affiliate validation straightforward: the platform's click. The tracking guide has each conversion carry the order reference, with context such as the coupon code where one was used, and those two fields are what let the business find and match these orders. Code-only orders come from the order system and the register rather than from the platform's clicks, so the routine runs in four steps:
- Find them. At each validation run, list the orders that carry a code tied to a partner and either no affiliate click inside the window or another partner's later click on an order not treated as leaked, by matching the code on each order to the register as the SOP does for partner orders.
- Validate them with everything else. Exclude returns, cancellations, duplicates, test and staff orders on the same grounds and inside the same validation periodHow long the business has to review an affiliate conversion before approving its commission, long enough to cover returns and cancellations.; a code-only order is not paid sooner or on looser grounds than a clicked one.
- Pay by the agreed route. For commission through the network or platform, the re-credit step of the tutorial on tracing missing affiliate conversions adds orders lost to a tracking fault through the adjustment process the business has agreed with its network or platform, and asks for one to be agreed and put into the terms where none exists. The tutorial uses that process for orders that carry evidence of a click, so whether it also accepts orders that never had one is for the business to confirm with its network; if it does not, the route is a fee paid outside the platform or nothing, and the terms say which.
- Keep them on their own line. The month-end commission tutorial matches adjustments to the invoice when the month closes. Code-only commission enters the month-end table as a line of its own, beside clicked commission and rejected leaks, so finance can tell what share of the month's commission rests on codes rather than clicks.
| Order | Who is paid | Where the evidence sits | Reason on the record |
|---|---|---|---|
| A partner's tied code, no affiliate click inside the window | The code's owner, by the agreed route | Order system and register | Code-only credit under the terms |
| The owner's code with a later click from a partner outside the protected group, unless the next row applies | The code's owner | Platform click, order system and register | Protected code owner; clicking partner rejected under the coupon clause |
| Another partner's exclusive code arriving through a voucher or extension click, with no earlier click from its owner | Nobody | Platform click and register | Leaked code |
| A public code or a service code, no affiliate click | Nobody | Register | The code names no partner |
| A partner's own click, with its own code, the public code or no code | The clicking partner, under the click rule | Platform click | Click rule |
The reasons matter as much as the payments. A partner who sees code-only orders on a separate line can check them against their own episodes and sends, a rejected leak carries a reason the code's owner can read, and the reconciliation between the platform, the order system and the invoice has an explanation for every order that never had a click.
Writing the code rule into the terms
The tutorial on writing affiliate programme terms already gives the terms a coupon clause: the codes a partner may publish, codes belonging to the partner who received them, and what a tracked order carrying someone else's code earns. Code credit extends that clause rather than sitting apart from it, and the extended clause says:
- which codes earn code-only credit, by type, and that public and service codes earn nothing by themselves;
- that an affiliate click inside the lookback window the timing clause already states takes the order out of code-only credit and into the click rule;
- the protected group for orders carrying both a code and a click, and who keeps the order when two members meet;
- that a voucher or extension click carrying another partner's exclusive code, with no earlier click from its owner, pays nobody;
- the route and the rate for code-only orders, stated beside the outcome they pay for;
- how a leaked code is withdrawn and replaced, and from when code-only credit on it ends.
Then publish it as the tutorial publishes any version, with the platform check before publishing, the change notice, the version log and the test on past disputes, adding the agreed adjustment process to the platform check and the code disputes already on file to the test. The business's legal adviser reviews the wording and finance decides how code-only commission is booked; nothing in this guide is legal, tax or accounting advice.
A chess set maker credits its podcast partners (illustrative)
Pluskermot Chess pays its podcast hosts on their codes
Pluskermot Chess, an invented maker of wooden chess sets and boards, runs an affiliate programme of 46 partners on a network. Six hold exclusive codes: three chess podcast hosts, two chess newsletters and an online chess club. Its terms set a 30-day lookback window, last click with protection for review sites, an 8% rate and a coupon clause, but say nothing about orders carrying a code and no click.
Reading a quarter's register against the order system, the programme manager finds 1,140 orders carrying one of the six codes. Of those, 410 carried a tracked click from the code's owner, 95 a later click from a review site, 75 a voucher or extension click and 560 no affiliate click inside the window. Of the 560, 470 carried a podcast host's code. The hosts had been paid on the 140 orders their own links tracked.
The new rule goes into the terms with the 30 days' notice they promise. A partner's exclusive code earns 8% on an order with no affiliate click inside the 30-day window. Where another partner's click is present the click rule decides, with exclusive code owners in the protected group. Review sites are protected too, so the terms state that when a review site's later click meets an exclusive code, the code's owner keeps the order. An order arriving through a voucher or extension click with an exclusive code, and no earlier click from the code's owner, is treated as leaked and earns nobody: the voucher site nothing under the coupon clause, the owner nothing. The public code and the service team's codes earn nothing by themselves. New exclusive codes run for 60 days and work on a first order only. Before publishing, the manager confirms that the network can take code-only orders through the adjustment process agreed with it, and writes that process into the terms.
In the first quarter under the rule, validation finds 520 code-only orders against the register; 34 returned or cancelled orders are rejected and 486 are paid through the adjustment process, on their own line in the month-end table. In week 5 one host's code turns up on a deal site. It is withdrawn that day and replaced; the 23 orders that had arrived through the deal site with it, none after a click from the host, earn nothing, and code-only credit on the old code stops with the withdrawal.
At the end of the quarter the manager reads code-only orders against each show's air dates: 391 of the hosts' 428 code-only orders came within 7 days of an episode. The rule stays for the hosts. The club's code and then its replacement leaked during the quarter, each withdrawn the day it was found, so the club moves to single-use codes issued to members one at a time.
Common mistakes
- Leaving code-only orders to whatever the platform records. Without a written rule, a host whose listeners buy through the code is paid only on the clicks, and nobody can say whether that was intended.
- Letting the code override the click. The code works beside the click rule; where an order carries a click, the rule decides, and the code only says who is protected.
- Paying the code's owner on orders that came through a deal page. A voucher or extension click carrying an exclusive code, with no earlier click from its owner, is a leak, and it pays nobody.
- Paying on public or service codes. They name no partner, so they cannot earn code-only credit.
- Approving code-only orders outside validation. They pass the same checks, inside the same period, as every clicked conversion.
- Burying code-only commission in the clicked total. Keep it on a line of its own, so finance and partners can see what rests on codes.
- Leaving a leaked code live. Code-only credit keeps paying the owner for the deal page's shoppers until the code is withdrawn and replaced.
- Changing the rule without notice. Announce it under the change-notice rule, log the version and apply it from the date it takes effect.
- Reading code-only orders as the partner's whole effect. Redemptions are a floor that deal sites contaminate; what a partner adds is a question for a test.
