Affiliate Links: How Clicks Earn Commissions
A reader finds a product review, follows its link to a retailer, and buys the product. The publisher may earn a commission, but the purchase alone does not settle the question. The link has to identify the publisher, the customer action has to be reported, and the program has to decide that the action qualifies. A reader may want to know whether the recommendation is paid; a new publisher may want to know why a click did not become earnings. Both questions start with what an affiliate link actually does.
An affiliate link identifies the publisher who referred a potential customer so a qualifying action can be considered for commission. The action might be a purchase or another result specified by the advertiser; Shopify describes affiliates as third-party promoters who use unique links and earn commissions on desired customer actions. The useful word is considered. A link creates a way to assign credit. It does not promise that every visitor, order, or sign-up will be paid.
The practical approach is to treat an affiliate link as one part of a recommendation and one part of a commercial agreement. Readers need a clear reason to follow it and a clear statement of the publisher’s financial connection. Publishers need to know which action counts, how long a referral stays eligible, who wins when several partners participate, and when a recorded action becomes an approved commission.
An affiliate link identifies a publisher, not a guaranteed payout
In a typical arrangement, the advertiser sells the product or service, the publisher recommends it, and an affiliate platform records the referral and later action. The customer sees a link in an article, product comparison, video description, or another placement. The platform’s task is to connect the qualifying action to the right publisher under the advertiser’s rules. The APMA’s guide to affiliate tracking describes platforms and networks as intermediaries for tracking, reporting, and payments, and describes tracking links in publisher content.
That makes an affiliate link different from an ordinary outbound link in purpose, even when the text on the page looks the same. A plain link takes a visitor to a destination. An affiliate link also supplies a referral identity that the program can use. The visible words “See the product” do not tell a reader which kind of link sits underneath, and the mere presence of tracking in a URL does not tell the reader what the publisher will receive. The disclosure has to explain the commercial relationship in ordinary language.
Affiliate marketing also differs from a customer referral program. A store might reward an existing customer for introducing a friend; an affiliate partnership commonly involves a publisher or creator recommending a brand to an audience. Shopify’s comparison of referral and affiliate marketing describes that distinction. The distinction matters when someone asks for an “affiliate link” but actually wants to share a personal referral code: the participant, reward, and eligibility rules may belong to a different program.
For a publisher, the first question is therefore not “Where do I paste the URL?” It is “What agreement does this URL represent?” If the program pays for an eligible purchase, a click is a lead toward possible commission. If the program defines a different qualifying action, the publisher must judge the link against that action instead. A recommendation that draws curious visitors but few qualifying actions can be useful to readers while producing little affiliate income. That is a commercial outcome, not proof that the link failed.
Follow the click through to the reported action
The normal tracking sequence has separate events. A customer clicks the publisher’s link. The tracking system records the referral identity and click time. Later, if the customer takes a qualifying action, the advertiser reports the conversion to the affiliate platform. The APMA tracking guide describes a first-party record of the publisher ID and click time, followed by a conversion reported through a browser pixel, a server-to-server call, or an API.
Consider an illustrative journey: a reader follows a publisher’s product review on Monday, compares options elsewhere, and returns to buy on Thursday. The Monday click and Thursday order are different records. To credit the publisher, the program needs enough continuity to associate the reported order with the eligible referral. If the order never reaches the affiliate platform, the earlier click cannot by itself establish a payable sale. If the order reaches the platform but fails the program’s rules, the recorded conversion still may not produce commission.
The reporting method is an implementation choice, not a different definition of an affiliate link. A browser pixel sends conversion information from the order confirmation flow; a server call or API sends it through a different route. The APMA guide lists all three approaches. An advertiser choosing among them should ask how the chosen method carries the referral identity into the conversion record. A publisher choosing a program should care whether real customer journeys are tracked reliably, even if the publisher never sees the advertiser’s integration.
This separation also explains why a report of “clicks” is not a report of “sales.” A click shows that someone used the link. A conversion report shows that a later action was recorded. An approved commission shows that the program accepted that action under its rules. Those counts answer different questions, and treating them as interchangeable makes both income forecasts and disputes less useful.
The attribution window limits the chance to earn
A referral cannot stay eligible indefinitely unless a program explicitly provides for that result. An attribution window sets the period in which a tracked referral can receive credit for a later conversion; Shopify’s explanation of an affiliate referral window says the duration varies by program. A purchase outside the applicable window can be genuine and still fall outside the commission terms.
For an illustrative example, imagine a program with a seven-day click-to-purchase window. A shopper clicks on day one and buys on day six: the timing condition is met. The same shopper buys on day nine: the timing condition is missed. The illustration says nothing about a particular advertiser’s terms. Its point is that a publisher cannot infer eligibility from the fact that the customer eventually bought.
The length that matters depends on the decision the audience is making. A publisher writing a detailed comparison for a purchase that readers may postpone should examine the window closely. A longer eligible period could make that kind of recommendation more workable, though it does not cure missing tracking or a rejected transaction. If readers normally act during the same visit, the window may be a less decisive term than which action qualifies or how competing affiliates are handled. This is a judgment about matching a program to the content, not a claim that one window is universally best.
“Cookie duration” and “attribution window” can also describe different constraints in a particular system. Trackdesk’s documentation distinguishes how long a browser cookie remains available from a server-side deadline for accepting a conversion. A publisher should therefore read the actual program rule instead of assuming that a prominently advertised cookie period settles every timing question. The date of the click, the date of the qualifying action, and any later approval or payment date can play different roles.
Two affiliates can point to one purchase
The visitor’s path rarely has to contain only one recommendation. Imagine, illustratively, that a shopper reads Publisher A’s review, later clicks Publisher B’s comparison, and then purchases. Both publishers may have helped. A program still needs a rule for assigning a commission. Trackdesk documents first-touch attribution, which credits the first affiliate click, and last-touch attribution, which credits the most recent affiliate click. Applied to the same illustrative path, the first rule favors A and the second favors B.
Neither rule is a neutral account of every contribution. First touch values introduction to the product; last touch values the final recorded affiliate step. The advertiser must decide which behavior it intends to pay for, and publishers need to know that choice before interpreting their reports. A creator who teaches readers about an unfamiliar product may see a different result from a publisher whose link is clicked shortly before checkout, even if both send useful traffic.
An attribution window and a touch rule answer separate questions. The window asks whether a referral is still eligible. The touch rule asks which eligible publisher receives credit when there are several. A sale can be inside the window for one publisher yet be assigned to another under last touch. Conversely, an earlier publisher could receive credit under first touch if the program’s timing and other conditions allow it. Seeing the distinction helps a publisher ask a precise question when an expected commission is absent.
I would avoid judging a partnership by its headline commission alone. Two programs can offer the same stated rate while crediting different partners on the same customer path. The better choice depends on where the publisher’s content appears in that path and on the program’s actual terms. The cost of preferring an attribution rule that rewards early education is that a later partner may receive less credit; preferring the final click makes the opposite trade-off. The rule should be clear before either side treats a sale as “theirs.”
A coupon code can carry the referral instead
Some affiliate relationships work without a clicked link. Rakuten Advertising describes an exclusive coupon feature that can associate a sale with a publisher when the advertiser enables it. The code can act as the publisher identifier at purchase. This is useful to understand when a recommendation is heard rather than clicked, such as a spoken code in a video or podcast. It is a specific program feature, not a universal property of discount codes.
Suppose, illustratively, a presenter says “use my code” and a viewer types that code into checkout after visiting the store directly. A click-based report would have no affiliate click from that presentation. A program configured for that exclusive code could still recognize the publisher through the code. If the customer forgets the code, or the advertiser has not enabled the feature, that route to credit is absent. The code’s presence in the presentation alone does not create a commission.
Codes introduce their own questions when a customer both clicks a link and enters a code. Which publisher gets credit can depend on the platform and advertiser’s configuration. Rakuten’s coupon guidance makes clear that linkless code tracking depends on advertiser support, and Trackdesk documents a setting that determines whether a recognized click or coupon takes priority. Before promising an audience that a code supports a particular creator, the creator should confirm the code is assigned, active, and commissionable under that advertiser’s rules.
For the buyer, a coupon and a disclosure serve different purposes. The code may offer a price benefit or simply identify the publisher, depending on its terms. The disclosure tells the buyer about the publisher’s financial incentive. A publisher should not assume that displaying a code makes the commission relationship obvious.
A tracked sale can still be declined
Even after an order is recorded, commission may remain unsettled. Awin’s auto-validation guidance explains that a tracked transaction can be approved or declined before a specified period ends, with automatic approval if it has not already been handled under the applicable setting. Its documentation gives returns or refunds as reasons an advertiser may need time to decline an incorrect transaction. The wider lesson is that “tracked” and “payable” are different states.
A publisher looking at a dashboard should distinguish clicks, tracked actions, pending commission, and approved commission. An expected order that appears as pending is a different problem from an order that never appears. The pending order may need time for the advertiser’s decision; an absent order may require examining the link, referral record, conversion reporting, or attribution rule. That difference directs the next question and avoids treating every delay as a tracking fault.
Here is an illustrative calculation, not an earnings benchmark. Assume a publisher sends 100 clicks, three purchases are recorded, and one of those purchases is declined under the program’s rules. If each of the two approved purchases would pay $10, approved commission is $20, or $0.20 per click across the original 100 clicks. Counting all three recorded purchases as paid would have shown $30 and $0.30 per click. The denominator has not changed; the status of one purchase has. A real publisher would need the actual terms and approved transactions before making that calculation.
An advertiser has a parallel obligation to make the rules intelligible. If returns, cancellations, ineligible products, or other conditions affect commission, those conditions should be discoverable before the publisher spends time producing content. The sources here establish that validation can approve or reject a transaction; the terms of any particular program have to supply the specific reasons. A generous stated rate cannot compensate a publisher for rules it cannot understand or apply.
Missing credit often starts before payment
When a publisher hears “someone bought through my link,” there are several possible gaps between the story and the platform record. The visitor may have acted outside the attribution window. Another affiliate click may have taken priority. The conversion may not have been reported or linked to the earlier click. A tracked action may still be pending or may have been declined. These are distinct explanations, drawn from the documented roles of timing, attribution, conversion reporting, and validation; they should be checked in that order only when the available records support it.
Device changes deserve particular attention. PartnerStack’s explanation of its cookie flow says that a customer who clicks on one browser or device and signs up or buys on another can become a missed referral in that flow. Picture a reader opening a review link on a phone, then completing the purchase on a laptop. A publisher can have influenced the sale while the documented cookie route fails to join those visits. That limitation belongs to the described implementation; it should not be projected onto every affiliate program without checking its tracking method.
Changing the way a conversion is reported does not, by itself, answer the identity problem. A server call or API can deliver an order record to the platform, as the APMA tracking guide explains, but the program still needs a basis for associating that order with an eligible referral. If the advertiser wants to support journeys that move between devices, it must establish what lawful, reliable matching information its own system and provider can use. The existence of an API is not a promise of cross-device credit.
For a publisher, the useful response to a missing commission is a focused question: was the click recorded, was the customer action reported, was it within the window, which publisher had priority, and what status does the transaction show? A screenshot of a buyer’s receipt might establish that a purchase occurred, but it cannot by itself establish that the purchase met every affiliate condition. The publisher should ask the advertiser or platform about the relevant record and rule rather than guarantee the buyer that a commission is owed.
For an advertiser, a sound launch includes trying the full journey represented by the promotion: click a publisher link, complete the specified action, and check the resulting partner record and its status. The APMA guide describes the click-to-conversion chain and the available reporting routes. Testing the actual route is a practical inference from that chain. If a campaign sends people into an app or invites a return visit, those paths deserve the same attention as a simple desktop checkout.
Choose the recommendation and the link together
The reader’s job is usually to decide whether a product, service, or offer fits. An affiliate link is useful when it follows an explanation that helps make that decision. A comparison should say what matters between the options; a review should say who the product suits and where it falls short; a tutorial should place the link near the step where the reader needs the item. These are editorial choices, not properties supplied by a tracking platform.
I would put a link on the specific recommendation it supports and make its destination clear in the surrounding words. Repeating the same link through an article without adding information gives the reader more exits but no better basis for choosing. A link to a product the article barely discusses asks the commission arrangement to do the work of the recommendation. The cost of a selective approach may be fewer affiliate clicks. The gain is that each click follows a decision the page has actually helped the reader make.
This approach also helps a publisher choose programs. If an audience needs time to compare, timing and attribution rules deserve close attention. If an audience is likely to remember a spoken offer rather than tap a link, a supported exclusive code may fit the placement better. If the advertiser cannot explain which actions count or how a recorded action becomes approved, the publisher cannot responsibly estimate what the relationship is worth. These judgments follow from the tracking and eligibility rules, not from a promise that one content format always performs better.
Advertisers should make the offer equally concrete. Tell a publisher which customer action qualifies and where to send the customer. Explain the attribution rule, the window, any supported code arrangement, and the route from recorded action to approved commission. A publisher can then decide whether its content genuinely matches the offer. Leaving those terms vague makes a dispute likely whenever a reader buys but a dashboard shows no approved credit.
Put commission disclosure beside the recommendation
A publisher’s financial connection is relevant to how a reader weighs a recommendation. For endorsements covered by U.S. guidance, the Federal Trade Commission says an affiliate relationship should be disclosed clearly and conspicuously, with the disclosure close to the recommendation. A plain sentence such as “If you buy through this link, I may earn a commission” tells the reader what matters. It does not require the reader to decode marketing vocabulary.
Placement matters because a disclosure can be present on the page yet absent from the reader’s decision. If a product recommendation and its link are far from a notice at the end of a long article, a reader may never connect the two. The FTC’s affiliate guidance discusses whether the disclosure and link are visible together and says proximity improves clarity. Put the explanation where the reader encounters the recommendation. If a page has several separated recommendation areas, consider whether each reader can see a clear disclosure at the point of choice.
The label “affiliate link” alone is a poor substitute for that sentence. The FTC notes that consumers may not understand that the term means the publisher gets paid for purchases through the link. The disclosure should identify the possible commission, not merely classify the URL. A code that can earn commission deserves the same plain-language treatment when the publisher is endorsing the product.
This is U.S. guidance for the endorsements it covers. A publisher serving other jurisdictions must check the rules that apply there, rather than treating a U.S. example as a global legal formula. The reader-facing principle remains useful: explain the commercial connection in words a buyer can understand before that connection could influence the click or purchase.
Mark paid outbound links for Google
There is a second, separate audience for link information: search engines. Google Search Central says paid outbound links should use rel=“sponsored” and that rel=“nofollow” remains acceptable, though sponsored is preferred. That instruction concerns the link attribute in the page’s HTML. It does not tell a human reader that the publisher may receive a commission.
For a site owner, the decision is straightforward. When publishing an affiliate recommendation, make the financial relationship plain to the reader and ensure the outgoing paid link is qualified for Google. If a publishing system supplies a setting for sponsored links, use the setting and check the resulting link. If the publisher cannot control the HTML, the publisher should ask the site operator how paid links are marked. A reader disclosure and a link attribute solve different communication problems, so neither replaces the other.
The distinction also prevents a misleading shortcut. Adding rel=“sponsored” does not make a hidden commission obvious on the page, while a disclosure sentence does not set the outbound link attribute. Both can coexist without changing the substance of the recommendation. The recommendation still has to earn the reader’s trust through accurate, useful content.
Check the program rules before counting income
Before using an affiliate link as a business tool, a publisher should read the terms as a sequence of decisions. What customer action qualifies? How long after a click can it count? If the visitor encounters two affiliates, which one receives credit? Can an exclusive code identify the publisher without a click? When does a tracked transaction become approved? The documented examples from Shopify’s referral-window explanation, Trackdesk’s attribution settings, Rakuten’s coupon feature, and Awin’s validation process show why a link and a commission rate are insufficient answers.
The same questions help an advertiser design a fair program. A rule that rewards the final affiliate click may suit one commercial aim while disappointing a publisher that introduces buyers early. A short window limits the period for credit; a longer one can increase the advertiser’s exposure to later claims. A code can recover a spoken recommendation that produces no click, but only if the feature and its priority rules are configured. These are trade-offs to decide openly, not surprises to discover when the first commission is disputed.
The most useful mental model is simple: the affiliate link opens a possible route from a recommendation to commission. Tracking records a click and a later action; attribution rules decide who can receive credit; validation decides whether the recorded action is payable. Disclosure tells the reader about the publisher’s incentive, while the sponsored link attribute tells Google how to treat the paid outbound link. Once those parts are separated, a buyer can understand the recommendation and a publisher can judge the opportunity without mistaking a click for a paycheck.