END-TO-END LIFECYCLE
A commission must survive eight separate checkpoints
Affiliate reporting becomes easier to understand when every outcome is treated as a state in a controlled process. A click is not a sale, a reported sale is not an approved commission, and an approved commission is not necessarily cash in the bank yet.
- Offer and rules
The advertiser defines the eligible product, customer, country, traffic source, payable event, attribution window, exclusions and commission.
- Partner identity
The program or network assigns an account, publisher or campaign identifier that can be included in a tracking link, code or supported integration.
- Qualified promotion
The affiliate publishes a permitted recommendation or campaign for an audience whose problem and intent fit the offer.
- Click and handoff
A visitor follows the tracked link. A redirect may record identifiers before sending the visitor to the merchant’s landing page.
- Conversion event
The visitor completes the defined action — for example an eligible purchase, qualified lead, registration, install or subscription.
- Attribution decision
The platform applies the program’s rules to decide whether the event receives affiliate credit and which partner receives it.
- Validation
The advertiser reviews returns, cancellations, duplicates, fraud indicators, customer eligibility and other campaign conditions.
- Approval and payment
An accepted commission progresses through the platform’s locking, invoicing, threshold, tax and payment schedule.
Measure the last verified checkpoint. If you can prove clicks but not a merchant conversion, investigate offer fit and the merchant journey. If the conversion exists but no commission appears, investigate tracking, eligibility and attribution.
TRACKING METHODS
No single tracking method covers every program, browser and device journey
| Method | What it does | Important limitation |
|---|---|---|
| Tracking link and parameters | Carries a partner, campaign or sub-ID through a redirect so the click can be recorded. | Editing, shortening or redirecting the URL incorrectly can remove required values; the program may restrict link cloaking or redirects. |
| Browser cookie | Stores referral information for a defined period so a later conversion may be associated with the click. | Expiry, consent choices, browser controls, cleared storage, another browser or another device can interrupt the journey. |
| First-party tracking | Lets the advertiser store or read referral information in its own site context. | It still depends on correct implementation, consent requirements and the program’s attribution logic. |
| Server-to-server / postback | Sends a conversion and click identifier between systems without relying only on a browser confirmation-page tag. | Missing IDs, duplicate events or incorrect status mapping can still produce lost or inflated reporting. |
| Promo or referral code | Uses a code entered at checkout or otherwise linked to a partner. | Credit depends on program rules; leaked codes, code overlap and last-click rules may affect attribution. |
Cookie duration is a program setting, not a universal promise. Awin describes 30 days as a common industry reference while explicitly noting that programs vary. Always verify the live profile or agreement, and do not advertise a tracking window you have not confirmed.
A person may discover an offer on a phone and purchase later on a laptop. Unless the merchant’s system can connect those sessions through an approved deterministic or modeled method, the affiliate click may not receive credit.
ATTRIBUTION
Tracking records events; attribution decides who receives credit
A valid click and a valid sale can exist while a specific affiliate still receives no commission. Attribution applies rules across competing touchpoints, timing, channels and eligible actions.
Attribution window
The maximum eligible time between the referral and action. It may differ by advertiser, product, event or device context.
Last eligible click
Credit goes to the latest qualifying affiliate click before conversion. Common does not mean universal; read the specific program terms.
First click or protected referral
Some programs preserve the introducing partner or use a different priority rule for particular partner types.
Code-based attribution
An assigned code may receive credit with or without a preceding click, depending on implementation and the contract.
Channel priority
The advertiser may deduplicate affiliate events against paid search, email, direct partnerships or other marketing channels.
New-customer rules
A program may pay only for new customers, selected products, approved countries or actions above a minimum value.
Affiliate platforms and analytics tools can use different attribution models, time zones, event definitions and processing times. A difference between an affiliate dashboard and GA4 is not automatically proof that either system is broken.
COMMISSION STATES
Separate activity, earned value and cash flow
| Status | What it usually means | How to treat it |
|---|---|---|
| Click recorded | The tracking platform received a referral event. | Evidence of handoff, not evidence of a customer or commission. |
| Reported / pending | A conversion was received but remains inside validation or a return period. | Forecast separately; do not call it paid income. |
| Approved / locked | The event passed the current validation stage and its amount is confirmed under platform terminology. | Track as approved revenue while checking invoicing and payment timing. |
| Reversed / rejected | The advertiser removed all or part of the commission. | Classify the reason: refund, duplicate, invalid lead, policy, attribution or another stated cause. |
| Payable / paid | The balance met the relevant release conditions or was transferred. | Reconcile against the payment record, fees, currency and tax documents. |
Networks use different labels, so map their terminology to your own consistent ledger. Your operating report should never merge pending, approved and paid amounts into one number.
MEASUREMENT
Use rates that identify where value is being lost
Example: 2,000 qualified visits create 300 affiliate clicks, 12 reported actions and 9 approved actions worth €270. Outbound CTR is 15%, merchant conversion rate is 4%, approval rate is 75%, approved EPC is €0.90 and approved revenue per qualified visit is €0.135. This is a measurement example, not an earnings projection.
Compare like with like: use the same date basis, currency, traffic segment and commission state. For paid acquisition, subtract media, creative, tooling, refunds and labor before describing a campaign as profitable.
TROUBLESHOOTING
Find the first broken checkpoint instead of changing everything
| Observed signal | Likely investigation area | First controlled check |
|---|---|---|
| No tracked clicks | Wrong link, broken redirect, blocked placement or no real engagement. | Copy the link from the platform again, inspect the final destination and compare your own analytics with network clicks. |
| Clicks but no reported actions | Audience intent, offer mismatch, price, merchant UX, country/device eligibility or tracking. | Segment by page and country, inspect the merchant journey and verify that the exact product/action qualifies. |
| Known action but no commission | Attribution loss, expired window, another click, excluded customer/product, consent or implementation fault. | Record time, click ID/sub-ID, product and order reference, then ask support without exposing unnecessary personal data. |
| High pending, low approval | Refunds, poor lead quality, duplicates, compliance or campaign-specific validation. | Export rejection reasons and calculate approval rate by offer, source and campaign. |
| Approved but unpaid | Threshold, advertiser funding, invoice cycle, identity/tax verification, currency or payment setup. | Check the platform’s payable balance, required documents and published payment calendar. |
| Dashboard mismatch | Different attribution, time zone, event state, currency, latency or deduplication. | Align one date range and one conversion ID before comparing totals. |
CONTROLLED VERIFICATION
Test the path without violating program rules
- Read the test and self-referral rules
Do not place a personal order or create a lead through your own link unless the advertiser explicitly permits it.
- Start with the generated link
Preserve required parameters. Add only supported sub-IDs for page, placement or campaign measurement.
- Check the redirect safely
Confirm HTTPS, the expected advertiser domain, correct country page and intended product. Avoid publishing copied session-specific URLs.
- Verify click reporting
Allow for stated reporting latency, then confirm that the network records the expected click and sub-ID.
- Use an authorized conversion test
Where available, use a sandbox, advertiser test order, network test tool or a support-assisted verification process.
- Document the evidence
Keep timestamps, link version, landing page, sub-ID, consent state and support case. Never store full customer payment details.
If the link, landing page, traffic source and tracking setup all change together, the result cannot show which change solved or caused the problem.
PRIVACY & TRANSPARENCY
Tracking permission and commercial disclosure solve different obligations
A cookie or conversion integration may involve privacy, consent and data-protection requirements. An affiliate relationship also creates a commercial connection that should be disclosed clearly near the recommendation. A cookie banner does not replace an affiliate disclosure, and an affiliate disclosure does not by itself authorize tracking.
- Identify which party sets or reads each cookie and which data reaches each provider.
- Configure consent and privacy notices for the visitor’s jurisdiction and your actual technology.
- Collect the minimum identifiers needed for measurement and support.
- Use plain-language affiliate disclosure where the recommendation can influence a decision.
- Mark paid or affiliate links appropriately for search engines and follow platform-specific rules.
- Obtain qualified legal advice when your market, data flow or targeting creates uncertainty.
This guide explains operational concepts and is not legal advice. Requirements vary by country, audience, technology and role in the data flow.
OPERATING CHECKLIST
Before relying on an affiliate campaign, prove these facts
- The exact payable action and all major exclusions are recorded.
- The permitted countries, devices, channels and promotional methods match the campaign.
- The live tracking link reaches the correct secure merchant page without losing parameters.
- The attribution window and priority rule come from the current program terms.
- Clicks, reported actions, approved actions, reversals and payments are stored separately.
- Sub-IDs identify the page or campaign without exposing personal data.
- The approval rate, approved EPC and approved revenue per visit are calculated consistently.
- Disclosure and privacy controls match the actual placement and tracking setup.
- A support-ready evidence record exists for missing or disputed conversions.
- No scaling decision relies only on pending revenue or headline commission.
You are ready for Module 03 when you can trace one referral through every status, explain why tracking and attribution are different, calculate approved EPC, and identify the first checkpoint to investigate when revenue is missing.
APPLY AND REVIEW
Build a commission-status record
Assignment
Create a fictional record of several referrals. Keep recorded actions, pending amounts, approved amounts and received payments in separate fields. Explain which source supports each field and which cases remain unresolved.
Worked example
Suppose a dashboard records three actions but only one approved commission. That observation alone does not identify a tracking failure. Use the lifecycle and diagnosis sections to distinguish status, eligibility and missing evidence before deciding what to investigate.
Completion criteria
Submit the records, status definitions and one investigation note. A test click confirms a narrower outcome than a validated commission or a payment.
PRIMARY SOURCES
Documentation used for this guide
Source review: . Tracking technology, browser behavior and program terms change; verify live documentation before implementation.
Next: affiliate programs, networks, platforms and marketplaces
Module 03 compares direct advertiser programs with network and platform models, showing what each structure changes for discovery, approval, tracking, support, payments and risk.