Affiliate marketing: commissions, partners and reliable tracking

An affiliate programme pays a partner when an agreed action happens, such as a completed sale or an accepted lead. The partner may be a publisher, creator, comparison site or business that refers customers. A link can record the referral. It cannot decide whether the commission is affordable, the content is honest or the customer is a good fit.

This guide covers those decisions and the day-to-day work behind them. The numbers are planning examples, not Lucid Growth Media client results or suggested market rates. Platform features and rules can change. Check the linked documentation before setting up a live programme.

Decide what a useful referral means

Choose the result you want before recruiting partners. A retailer might want profitable first orders. A software company might want paid accounts that remain active. A service business might pay for leads only after checking agreed criteria. These are different offers and need different rules.

Write one clear definition of an eligible action. For a lead, specify the required market, service, contact permission and evidence of a real request. Do not reject a lead because of a condition the partner could not have known. Give the team a deadline for checking each action and a route for reviewing mistakes.

Check that the offer is ready

A partner sends people into your buying process. Test that process on mobile before buying attention. Check product availability, prices, delivery limits, form errors, payment or enquiry confirmation and support. Make sure sales staff can handle the expected response.

Give partners accurate information they can maintain: product descriptions, images, approved claims, current offers and contact details. Tell them who will announce changes. If the offer is unreliable or hard to understand, fix it before adding more partners. Otherwise you risk paying to spread the same problem.

Work out the commission you can afford

Start with the money left after the costs that change with an order. Include product cost, payment fees, fulfilment, expected returns and discounts. Then allow for commission, network fees and programme work. Revenue alone does not show whether a referral is worthwhile.

This example leaves ₹320 before fixed overheads and profit taxes. A higher discount, return rate or service cost changes the answer. Run low, expected and high-cost cases. Define the commission base clearly: tax, shipping, discounts and returned items can all affect it. Have finance review tax and invoicing treatment separately.

Match rewards to the result

A flat rate is easy to explain. Different product margins may need different rates. A higher rate for a genuine new customer may make sense, but only if the business can identify that customer reliably and the rule is clear.

Avoid rewards that encourage low-quality volume. Paying for every form submission can attract duplicates and false requests. Paying only for a sale months later can shift too much risk to a partner who cannot control sales follow-up. Choose a model that each side can understand and influence. Explain any minimum payout, validation delay or tier before the partner starts work.

Choose a platform against a written checklist

Compare the tasks you need, not just the dashboard. Can the system record the right action, deduplicate it, adjust a partial return and export a clear payment record? Can staff explain why an action was credited, held or declined? Check currencies, access controls, reports, fees, support and the effort needed to leave the platform.

Server-to-server tracking sends events directly between systems. It can help record actions, but it does not remove privacy duties or solve every attribution gap. Awin's Conversion API has specific fields and processing rules; build and test against the current specification. Do not treat a successful connection as proof that every sale is recorded correctly. [1]

Put the rules in plain language

Before a partner joins, explain the commission rate, eligible action, attribution window and payment process. The attribution window is the period after a referral in which an action may receive credit. State which event starts it and what happens if another partner later refers the same customer.

• Define allowed websites, social channels, paid ads, email and coupon use.
• Explain brand-name bidding, redirects, incentives and prohibited claims.
• State how cancellations, partial returns, duplicates and fraud checks affect commission.
• Give the validation deadline, payment schedule, currency and any fees.
• Explain rate changes, termination, outstanding earnings and dispute handling.

Keep a version of the terms each partner accepted. Give notice of changes as the agreement and law require. Do not silently apply a worse rate to work already completed under an earlier agreement.

Recruit for fit and onboard for a first useful action

Look at the partner's audience, content and methods. A small specialist publisher may answer a buyer's question better than a large unrelated account. Ask how the partner earns traffic, presents recommendations and discloses paid relationships. Avoid promises of guaranteed sales or access to unexplained customer lists.

Agree a practical first activity: a product demonstration, a useful comparison or an article answering a real buying question. Supply test access or a sample where appropriate, along with accurate product information. Confirm that the tracking link works and that the partner knows how to get help. An approved account with no clear next step is not an active partnership.

Test tracking before real earnings depend on it

Use authorised test records. Follow an affiliate link, return later, complete an eligible action and inspect the record. Test mobile, permitted coupon use, repeat clicks, cancellation and partial return. Check that one transaction does not create two payable commissions.

Document limits such as blocked tracking, different devices, missing consent or code use without a tracked click. Decide how a partner can report a missing action and what evidence is reasonable. Do not promise perfect tracking. Equally, do not use known faults as a reason to ignore a credible payment query.

Keep a transaction record that finance can follow

For each action, keep an internal identifier, date, partner, eligible value, rate, status and adjustment reason. Limit access to any personal data. A partner usually needs a transaction reference and commission explanation, not a customer's full identity or order history.

Use separate totals for recorded, approved and paid commissions. A recorded action can still be awaiting validation. An approved action may not yet have reached the payment date. impact.com's documentation distinguishes pending actions from actions that are reversed; those states should remain visible in reports and partner explanations. [2][3]

Handle returns and payment disputes fairly

Suppose an eligible ₹2,000 order earns a ₹200 commission. If a ₹500 item is returned and the agreed rate applies to retained net sales, the adjusted base is ₹1,500 and the commission is ₹150. Record the ₹50 reduction and the reason. Do not reverse the whole commission merely because one item was returned, unless a valid disclosed rule calls for that result.

Give partners enough time to query missing or reduced actions. Ask for the action reference, date and specific concern through the approved channel. Review the tracking record and the terms that applied. Explain the result and correct errors. Keep undisputed amounts separate where practical so one query does not hold up every payment.

Investigate suspicious activity without assuming guilt

Warning signs include repeated contact details, unusual conversion spikes, very high returns or traffic from prohibited sources. These patterns can also have innocent explanations. Use them to decide what to check; do not treat a score or alert as proof of fraud.

Name who can pause activity or payments, on what grounds and for how long. Preserve relevant evidence, ask focused questions and protect customer data. Give the partner a review route. Follow the contract and applicable law before withholding earnings or ending the relationship.

Help partners publish useful, honest content

A useful review explains who a product suits, what it does well, its limits and how it compares with alternatives. Where the reviewer has tested it, show original observations or evidence. Where they have not, say so. Never invent personal experience, results, customer quotations or awards.

Google's review guidance encourages useful evidence and meaningful comparisons. Its spam policies address thin affiliate pages and other abusive practices. Copying a merchant description across many pages adds little value; changing a few words with AI does not create genuine experience. [4][5]

Make paid relationships easy to see

People should understand when a recommendation may earn commission or follows a payment, gift or other relevant connection. Put a clear disclosure with the recommendation. Do not rely on a footer policy, profile biography or text hidden after an expansion control.

The FTC's guidance covers material connections and practical disclosure placement. ASCI gives separate guidance for influencer advertising in India. Apply the rules for the actual audience and format; one label is not a universal legal solution. For video, consider what viewers can both see and hear. [6][7]

Use the platform's required paid-partnership controls as well. X has its own policy for paid partnerships. Platform labels do not excuse misleading claims or replace other required disclosures. Check the finished post, including cropped versions and captions, before it goes live. [8]

Measure quality as well as attributed revenue

Review approved net sales, contribution after programme costs, return rate, new-customer share and repeat business where lawfully available. For lead programmes, review acceptance reasons and eventual sales. Separate partners by the role they play so a research publisher is not judged only by the same pattern as a last-minute coupon site.

Attribution assigns credit under a rule. It does not show how many sales would have happened anyway. To investigate added value, consider a suitable holdout, staged launch or other controlled comparison. Plan it with enough volume and care to avoid misleading results. Where a sound test is not possible, describe the uncertainty instead of calling every attributed sale additional revenue.

Give routine work an owner

Automation can flag broken links, compile reports and remind staff about validation deadlines. A person should approve material rate changes, disputed reversals, partner suspension and sensitive published claims. Stop a workflow when its records are missing or inconsistent.

Review payment queries and tracking faults frequently. Review partner quality, content accuracy and economics on a planned schedule. Keep a change log so a change in commission or product availability can be connected to later results. A short, useful review is better than a large dashboard nobody uses to make a decision.

If you are the publisher, check your own economics

Estimate the cost of testing products, producing content, maintaining pages and serving the audience. Compare that cost with approved earnings, not clicks or pending balances. Read attribution, returns and payment rules before depending on the income.

Recommend products because they fit the audience. Explain drawbacks and alternatives even when that may reduce a sale. Keep records of permissions, disclosures and terms. Avoid building the whole business around one programme whose rate or availability you cannot control.

Work through a complete retailer example

The following exercise shows how recorded sales become a business result. It uses invented numbers so you can repeat the calculation with your own costs. It is not a target commission, industry benchmark or prediction.

Imagine a retailer starts a small programme for one product range. During the month, the platform records 100 orders at ₹2,000 each, excluding tax. Ten orders are cancelled in full before completion. Ten other orders receive a ₹500 partial refund. The remaining 80 orders stay at their full value. Use the validated outcome of this same group of orders, even if the return window closes in the next month.

Step 1: establish the eligible sales value

The recorded value is ₹200,000. Full cancellations reduce it by ₹20,000. Partial refunds reduce it by another ₹5,000. Eligible net sales are therefore ₹175,000. Do not keep reporting the original ₹200,000 as final programme revenue. Keep both numbers with clear labels so people can see what changed.

The 90 non-cancelled orders include the ten partial refunds. That distinction matters when counting customers and orders. A partial refund changes value without necessarily removing the whole order. If an order includes products with different commission rates, calculate the adjustment at the relevant item level rather than applying an unexplained average.

Step 2: deduct the full cost of the programme

Suppose product and other variable costs equal 70% of eligible sales in this simplified model. That leaves ₹52,500 before affiliate costs. A 10% commission costs ₹17,500. Platform costs are ₹5,000 and the month's allocated programme work costs ₹10,000. The remaining contribution is ₹20,000.

This contribution is not the company's net profit. Fixed overheads and profit taxes are outside the example. Real returns may also create costs that do not fall in line with revenue, such as return shipping or unsellable stock. Replace the simplified percentage with actual costs where possible. State any exclusions next to the result instead of hiding them in a separate workbook.

Step 3: test what could make the result weak

These cases answer different questions. A higher rate can be affordable only if the new work it attracts is worth the extra cost. A lower product margin can leave little room even when the revenue chart looks strong. Falling sales can make the fixed platform and management costs harder to cover. Do not combine assumptions casually; model each clearly and then consider a plausible downside case with several changes together.

Step 4: decide what to do next

The business might keep the existing rate, focus on products with sufficient margin and test one new partner type. It should not immediately double rates across the whole programme because a competitor advertised a larger percentage. Nor should it assume that every existing sale was caused by the affiliate activity.

Review customer quality and partner role alongside the calculation. If most orders came through a coupon placed at the final step of an existing buying journey, the programme may be claiming more credit than it adds. If a specialist publisher introduced buyers to an unfamiliar product, some value may develop over time. Those are questions for evidence, not reasons to assign favourable numbers without support.

Design a lead programme with fair acceptance rules

A lead programme needs a written definition of an accepted enquiry. Consider a service business that wants requests from companies needing a particular service. Suitable criteria might include a relevant service need, an eligible market, a genuine business contact and a request made with permission. The criteria should relate to the offer and be practical to check.

Avoid a hidden requirement that every lead must already be ready to sign. If the programme pays for a qualified enquiry, a later sales loss is not automatically grounds to reject it. If the programme instead pays only for a completed sale, say so clearly. A partner cannot manage risk that is revealed only after the work is done.

A lead calculation

Suppose 40 enquiries arrive. Under the disclosed rules, six are duplicates and four are outside the agreed service scope. Thirty are accepted at ₹400 each, creating ₹12,000 of commission. After the normal sales period, six of those accepted enquiries become customers. Each sale contributes ₹6,000 before acquisition costs, giving ₹36,000 in total.

If checking and following up the leads costs ₹3,000 and the platform costs ₹1,000, the total acquisition cost is ₹16,000. That is about ₹2,667 per customer, and ₹20,000 remains from the ₹36,000 contribution. These are illustrative figures. Confirm that the six sales came from this group of leads and that later refunds or delivery costs are treated consistently.

The example does not justify rejecting the other 24 accepted leads. The business agreed to pay for acceptance, not eventual sale. If the economics are poor, change future criteria or terms through the proper process. Improve follow-up where needed. Do not rewrite the payment event after partners have already delivered it.

An acceptance process people can follow

Give staff a small set of reason codes and examples. “Duplicate under the agreed period” is clearer than “low quality”. Let the reviewer see the minimum evidence needed. Record the date and decision so a delayed review does not leave the partner guessing.

Agree what happens when staff cannot reach a contact. One missed call should not silently become proof that the request was false. The rule might require a reasonable, defined contact process before a final decision. Keep that process proportionate and avoid repeated unwanted calls. The person's contact preferences and applicable law still govern the outreach.

Make attribution rules understandable with scenarios

Write down how common journeys will be treated. The following scenarios use an imaginary 30-day window and a last eligible affiliate click rule. They are examples of how to explain a model, not a recommendation or a description of every platform.

Two partners refer the same buyer

A buyer reads a comparison on Partner A's site, follows its link and later clicks Partner B's eligible link before purchasing. Under the example rule, Partner B gets the recorded commission. Partner A may have helped the decision but does not receive payment under that rule. Explain this difference between contribution and credited commission before recruitment.

If the business wants to reward earlier influence, it needs a deliberate, testable model or a separate commercial arrangement. Do not promise partners that the platform will somehow recognise every influence. Check whether the selected technology can support the proposed model and whether the added complexity is worth operating.

A code is shared outside the intended channel

A creator's code may appear on another website or be passed among customers. Decide whether the code itself earns credit, whether a qualifying link is also required and whether sharing is allowed. Define how code and link claims are reconciled. A code is not conclusive proof that its original owner introduced every person who used it.

Treat accidental sharing differently from evidence of a deliberate rule violation. If an exclusive code leaks, investigate how and notify the affected partner. Changing or disabling it may be appropriate, but explain the effect on valid activity already in progress. Keep customer discounts and partner commission rules separate where they differ.

A buyer changes devices or declines tracking

A person may discover the product on a phone and buy on a laptop. Their browser may block a signal, or they may decline optional tracking. The programme may not connect the events. State that limitation and use lawful, supported methods when improving measurement.

Do not work around a person's choice by collecting hidden identifiers or unnecessary personal data. If partners can report missing actions, give them an approved process that avoids sending customer identities through ordinary email. Review evidence fairly without promising that every untracked order can be reconstructed.

The purchase happens after the window

Under the example 30-day rule, an otherwise eligible purchase outside that period does not qualify. State how the window is calculated and what resets it. For a long sales cycle, assess whether that window is commercially sensible before launching. A rule can be technically clear yet poorly matched to the way the product is bought.

Keep these scenarios with onboarding materials. They reduce repeated support questions and expose gaps before a dispute. Review them whenever the tracking model or programme terms change.

Use a practical operating record

An operating record connects the commercial promise, tracking event and payment. It does not need to expose a customer's full details. The goal is to explain an action without copying personal information into every spreadsheet or email.

Set access by role. A contractor updating creative assets does not automatically need payment records. A partner should only see their own relevant information. Decide how access is granted, reviewed and removed. Use named accounts where the platform supports them, and avoid circulating shared administrator passwords.

Define retention by purpose and legal need. Keep enough evidence for payment and disputes, while removing personal details that no longer serve a valid purpose. If a client asks the agency to handle customer records, settle the processing roles, approved tools and transfer route first. The public enquiry form is not the place to upload a transaction database.

Plan a six-week pilot that produces useful evidence

A pilot should test the operating process as well as partner response. Six weeks is an example planning period; products with a long buying or return cycle need longer before final commercial results can be judged. Do not end validation early simply to fit a presentation date.

Weeks 1 and 2: make the offer and records ready

Confirm the eligible action, commission base and payment rules with finance. Test the customer journey and the key adjustment cases. Create a short partner guide, claim record and support route. Resolve missing product details before asking partners to publish them.

Select a small mix of suitable partners. For example, a product educator and a comparison publisher may reveal different needs. Record why each was chosen and what first activity is agreed. A pilot is easier to interpret when the team knows what each relationship was intended to test.

Weeks 3 and 4: publish and inspect the process

Check live links, claims, disclosures and the correct destination. Confirm that authorised test actions and real eligible actions arrive in the expected state. Review queries quickly enough that a partner is not left publishing a broken link for a week.

Keep commercial changes limited. If the rate, offer, landing page and partner content all change at once, a later improvement will be hard to explain. Necessary repairs should still happen promptly; record them and recognise that they affect the comparison.

Weeks 5 and 6: review and choose the next step

Inspect pending, approved and paid balances separately. Check unresolved returns and the age of the actions. Review content usefulness, partner workload, customer quality and the cost model. Ask partners which information or process caused avoidable work.

Choose a concrete next step: continue with the same model, repair a specific process, test another partner role or pause recruitment. Do not call a pilot successful merely because accounts were created or links were published. The result should explain what the business learned and what remains unproven.

Give publishers a realistic content plan

A publisher needs to decide whether the audience value and potential earnings justify the work. Start with questions readers already ask. Choose products that can be assessed responsibly, and plan what evidence is needed before writing. An attractive commission is not a reason to recommend an unsuitable product.

A simple monthly budget

Suppose product access and research cost ₹3,000, production costs ₹12,000 and maintenance costs ₹3,000. The total is ₹18,000 before general overheads and taxes. Forty approved orders averaging ₹300 commission produce ₹12,000, leaving a ₹6,000 gap. Sixty such approved orders cover the stated ₹18,000 cost, but do not yet provide a margin for other costs or profit.

Use approved earnings in that calculation. Pending amounts can still change, and payment delays affect cash flow even when the work is profitable. Do not assume the highest advertised commission applies to every order. Check product exclusions, new-customer rules, caps and the rate version that governed the action.

A useful four-piece plan

The publisher could create a practical introduction, a comparison, a demonstration and a follow-up answering questions from readers. Each piece should serve a different need. Link them where useful, but do not repeat the same merchant copy across all four.

Plan maintenance at the same time. Price, availability and product specifications may change. Keep the review date and evidence record. If the publisher loses access to the product or programme, update the claim or link rather than leaving a misleading recommendation online.

Prepare for problems before they happen

A programme can face a tracking outage, expired offer, late payment or disputed content claim. Write a short response process with an owner and a backup. Preserve relevant evidence, stop affected promotion where needed and tell partners what is known. Do not speculate about the cause before checking it.

For a tracking outage, record the affected period and event types. Reconcile available records using the agreed rules and lawful evidence. Explain any adjustment and remaining uncertainty. For a payment delay, distinguish an unresolved balance from a banking delay and give a realistic update. Do not promise a date the responsible team has not confirmed.

For a misleading claim, preserve the published version, assess the risk and correct or remove it promptly where appropriate. Check other assets that copied the same wording. Fixing one post may not resolve the same claim in ads, captions or translated versions. Review the cause so future approvals catch the problem earlier.

Evaluate an agency or platform proposal

Ask what the fee covers: recruitment, onboarding, tracking setup, content review, validation, support, reporting or payment administration. Define who owns the accounts and who authorises spending. Separate work the provider will do from work that still depends on your finance, legal or sales team.

Request an example report with invented or safely anonymised data. Can you see the difference between recorded and approved value? Are adjustments explained? Does the report show costs and an action to take, or only a large revenue total? Ask how disputes and access removal are handled at the end of the engagement.

Avoid promises of guaranteed passive income, perfect attribution or unlimited qualified partners. A strong proposal makes the work, dependencies and limits clear. It should leave the business able to understand its programme and continue operating it without relying on one person's private spreadsheet.

Check the cash needed before the payment date

A profitable order can still create a cash shortage if the business pays a partner before receiving the customer's money. Map the actual dates for customer payment, returns, commission approval and partner payment. Include the platform's funding rules and the time needed for finance to approve a payment batch.

Suppose ₹50,000 of commissions is properly due on a specified date, while a large customer's payment is expected a week later. The programme needs enough available funds to meet its obligation. It should not assume that slow customer payment automatically permits late partner payment. The agreement and law govern what is due. Plan a reserve or another approved funding method before the payment date approaches.

Use a simple forecast with opening available funds, expected receipts, approved commissions and other programme payments. Keep pending commissions visible as a possible future obligation. Do not treat a reserve for likely payments as profit available for another campaign. Ask finance to review the forecast when a promotion could increase volume quickly.

Make the monthly statement understandable

A partner statement should show the opening unpaid balance, newly approved earnings, adjustments, payments made and closing balance. State the reporting period and currency. If fees or tax deductions apply, identify their basis and provide the required documentation through the proper process. Do not invent a tax rate in a marketing plan or apply a deduction without checking the actual legal position.

Keep a payment reference so the partner can match the statement to the transfer. A dashboard status of “paid” should mean the defined payment step has actually happened. If a transfer fails, update the record and explain how the issue will be resolved. Avoid asking partners to send full banking credentials in an unsecured support message.

Close a programme without losing the records

Before moving platforms or ending a programme, review valid unpaid earnings, actions still inside a validation window and unresolved queries. Give the notices required by the agreement and law. Preserve the records needed to calculate and explain those balances, and remove access only through a planned process.

Tell partners which links or assets should stop being used and when. A website migration should not silently send their visitors to an unrelated page. Document responsibility for outstanding payments and support after the main campaign team moves on. A clear closeout protects both the business and partners from months of avoidable uncertainty.

Make your partner handover easy to use

Before a new partner starts, ask someone outside the programme team to read the joining instructions. Can they find the current commission, the actions that qualify, the payment timetable and the person to contact? Can they explain what happens if a customer returns an order? If those answers are spread across old emails, bring them into one dated document.

Give partners one approved place to find product details and current offers. Separate facts they may repeat from sample wording they need to adapt. Mark withdrawn offers clearly. When you change an important rule, explain the effective date, which transactions it affects and where partners can ask questions. Keep previous versions so a later payment query can be checked against the terms that applied at the time.

Close the handover with a small authorised test: open a working link, inspect the destination, confirm the disclosure and follow a test action through the report. Record the result and who checked it. This exercise will not prove that every future referral works, but it gives the partner and your team a shared starting point before real customer traffic arrives.

A practical launch checklist

• Finance has checked the commission model against returns and discounts.
• Partners can read the action, attribution and payment rules before joining.
• Authorised test actions, duplicates and adjustments produce the expected records.
• Content rights, claims and disclosures have been reviewed.
• A named owner handles partner questions, validation and payments.
• Reports separate pending, approved, paid and reversed amounts.
• The team has a review date and a decision to make at that review.

To plan a programme with Lucid Growth Media, share what you sell, who buys it, your order or lead process and any existing partner platform. Do not send customer lists through the enquiry form. We can first define the work and the data access it needs.