Lessons 75.1 and 75.2 established the recommendation and the selected offer. Now someone clicks. What happens between that click and your payout is attribution — the shared, imperfect trail that decides who gets credit. Misunderstand it and you will argue with dashboards, misprice your work, or promise results the numbers cannot support.

Three views of the same click

The same journey looks different to each party. Keep all three in mind:

• Creator view: clicks, code uses, signups or sales reported in the affiliate dashboard. This view is fast but partial — it sees only what the tracking captured and credited to you, under the program's rules.
• Merchant view: orders, refunds, chargebacks, attribution window, and reconciliation. The merchant records what actually completed and kept — after cancellations, returns, duplicate codes, and window expirations. Payout follows this view, not yours.
• Customer view: the experienced path — read the tutorial, clicked the link, got distracted, returned via search three days later, bought on mobile. The customer does not think in links; they think in remembered intent. Any model that credits exactly one click is a simplification of this messier reality.

Key terms in plain language: a tracked link or referral code carries your identifier; a cookie or attribution window is the program's memory ("credit purchases within 30 days of the click"); a click is an arrival, not a vote; a qualified action meets the program's definition (paid plan, not free signup); conversion is the verified action; reconciliation is the merchant's month-end correction for refunds and rule violations.

Numbers here are tools for learning, not replacements for product judgment. If your tutorial genuinely helps analysts and the merchant confirms steady conversions with low refunds, the partnership is healthy even when weekly dashboard counts wobble. If clicks surge but qualified actions stay flat, the lesson is fit or destination — not a tracking conspiracy.

UTM labels: the envelope, not the letter

Affiliate links prove who should be paid. UTM parameters label where traffic came from for your own analytics. Think of the affiliate code as the letter and UTM tags as the envelope notes. Standard fields:

• utm_source — where: newsletter, youtube, blog.
• utm_medium — how: affiliate, email, social, video-description.
• utm_campaign — which effort: research-tool-review-2026-09.
• utm_content — which variant: walkthrough-cta versus comparison-table.

Example destination:

https://example-merchant.com/sample-brief?aff_id=pub812
&utm_source=newsletter&utm_medium=affiliate
&utm_campaign=research-tool-review-2026-09&utm_content=walkthrough-cta

Rules that prevent months of confusion: one naming convention, lowercase, hyphens instead of spaces, no personal data in parameters, and every link built from the convention — never hand-typed improvisations. Keep a link registry: each URL, where it was placed, date placed, and what it should do. When a merchant updates pages or a platform rewrites URLs, the registry is how you find every copy that needs fixing. UTM fields change rarely but tool menus do — confirm the current field definitions in your analytics platform's official docs at drafting time (e.g. Google Analytics custom-campaign/UTM help, support.google.com/analytics/answer/1033867, checked September 2026; interfaces are a refreshable tool layer, the durable mechanic is source/medium/campaign/content labeling), and re-verify windows, code behavior, and payout schedules quarterly — these change without ceremony.

Expect imperfection. Ad blockers, private browsing, cross-device journeys, and customer-side detours all create gaps. Reconcile weekly against the merchant report rather than defending your dashboard as gospel. A stable gap (you see 10% more clicks than credited sessions) is normal plumbing; a sudden gap is a broken link, expired code, or changed page worth investigating that day.

Exercise: build the tracking plan

Create AFFILIATE-TRACKING.md with these sections:

• Naming convention: exact utm_source / medium / campaign / content vocabulary plus affiliate ID format. Example: source ∈ {newsletter, youtube, blog}; medium=affiliate; campaign={slug-date}; content={placement-variant}.
• Link registry: table with columns — placement, full URL, code, landing page, date placed, owner.

• One code: the single referral code for offline or verbal mentions, its terms, and where it appears.
• Weekly reporting fields: clicks, arrivals, qualified actions, conversions, refund/cancellation flags, payout due — with source for each (your analytics versus merchant dashboard).
• Reconciliation routine: "Every Monday, compare merchant conversions against registry; flag gaps over 15%; verify destination loads on mobile; confirm code still active."
• Privacy and honesty notes: no misleading countdowns, no cookie-stuffing, clear relationship note placement (expanded in Lesson 75.4).

Finish line: an AFFILIATE-TRACKING.md where a stranger can follow any click from placement to payout source without guessing which link or rule applied.

Verify quickly: pick one row in the registry, click it on mobile, and confirm it lands on the promised page with the identifier intact. Then find that arrival in both dashboards. If either step fails, fix tracking before publishing more content.

Common failure mode: five casually named links, two dead codes, and a dashboard argument with the merchant. Conventions and a registry prevent nearly all of it.

Check your understanding

1. How do creator, merchant, and customer views of the same purchase differ? 2. What does each UTM field record, and why keep a link registry? 3. Why reconcile against the merchant report instead of treating your dashboard as final?

Next

The trail is trustworthy. Lesson 75.4 closes the class by making the content itself worth following — useful walkthroughs, comparisons, and honest reviews with a clear relationship note.