An affiliate can drive the first visit and still lose the commission. With last touch attribution, the affiliate who sends the final eligible referral before conversion receives the credit.
That rule is simple on paper. It becomes harder when you add cookie windows, coupon codes, Stripe subscriptions, refund events, and users switching devices. Rewardful can track this workflow, but your campaign settings and checkout implementation must match the rule you promised affiliates.
Set the rule first. Then install tracking, test real paths, and keep a record you can audit.
HOW LAST TOUCH ATTRIBUTION WORKS IN REWARDFUL
Last touch affiliate attribution gives credit to the most recent eligible affiliate interaction before a customer converts. Under a first-touch rule, the original referrer keeps credit instead.
Rewardful supports both models. Read Rewardful’s explanation of first- and last-touch models before changing an active campaign. A switch can affect affiliate expectations and current traffic.
A referral link starts the browser-level record
An affiliate shares a Rewardful link, often with a ?via= parameter. A visitor clicks it. Rewardful stores the referral in the visitor’s browser for the campaign’s cookie window.
Now consider this sequence:
- On Monday, a prospect clicks Affiliate A’s link.
- On Thursday, the same prospect clicks Affiliate B’s link.
- On Friday, the prospect starts a paid subscription.
With a last-touch campaign, Affiliate B should receive the referral credit if both clicks qualify and the customer converts inside the attribution window.
A direct visit does not give another affiliate credit. A new eligible affiliate link can. That is why sales teams and affiliate managers need one written rule for partner links, paid retargeting, coupon use, and internal promotions.
The window decides whether a touch is eligible
A referral cookie has an expiry date. Rewardful’s default cookie window is 60 days, but you can set it for each campaign. The Rewardful cookie window documentation confirms that the setting is campaign-specific.
If a customer converts after the window ends, the original browser referral is no longer eligible. If they click a different affiliate’s link before conversion, last-touch rules can assign the credit to that later affiliate.
A 60-day cookie does not guarantee 60 days of credit. A later eligible referral can replace the earlier one in a last-touch campaign.
CONFIGURE THE CAMPAIGN BEFORE YOU SEND LINKS
Don’t start with the tracking script. Start with the campaign. The campaign controls the commercial rule that the script will enforce.
Open the campaign you plan to use. Review the options in the current Campaign Settings Overview. Rewardful can change labels and menu locations, so check the live interface before publishing terms.
Set the attribution rule and cookie window
Use this setup sequence:
- Open the correct campaign and select its edit settings.
- Find the attribution setting or advanced attribution controls.
- Choose last touch if that is the rule you want.
- Enter the cookie window in days.
- Save the campaign and record the date of the change.
Choose the window based on your actual sales cycle. A 14-day trial with fast self-serve purchases may fit a shorter period. A product with a 45-day evaluation process may need more time.
Long windows increase the chance that affiliates receive credit after an early introduction. They also increase the period during which a later affiliate can become the last touch. Neither option is automatically fair. Your published terms need to state the rule.
Define coupon treatment before affiliates ask
Coupon attribution is separate from a browser referral. A customer can enter a partner’s code at checkout without clicking that partner’s link. Rewardful describes how affiliate coupon codes and tracking links work differently.
Enable coupons only if you can state what happens when these events conflict:
- A customer clicks Affiliate A’s link, then uses Affiliate B’s coupon.
- A customer receives several partner coupons in different channels.
- Your internal sales team applies a discount code manually.
- A customer uses an expired or unapproved coupon.
Do not assume a coupon and a referral cookie will follow the same precedence rule. Test the behavior in your own campaign and write the result into your affiliate terms.
INSTALL REWARDFUL ON EVERY RELEVANT PAGE
Last touch attribution fails when the referral is captured on one page but the conversion event never reaches Rewardful. The browser script and conversion call are both required parts of the workflow.
Place the browser script in the global head
Rewardful’s JavaScript browser integration guide instructs you to add the tracking snippet in the global <head> area of your site.
Load it on marketing pages, pricing pages, signup pages, and any custom checkout pages that a referred visitor may use. The Rewardful script must load before you call its functions.
Avoid placing the snippet only on the thank-you page. By then, the visitor may have lost the referral path you needed to capture.
Test consent handling too. If your site delays marketing or analytics scripts until a visitor grants consent, confirm the Rewardful script follows your legal and product requirements. A referral click before consent and a conversion after consent can produce a different result than your team expects.
Send the conversion after the Stripe customer exists
For a custom browser checkout, Rewardful documents a conversion call such as rewardful('convert', { email: customer.email });.
Run that call on the confirmed post-checkout or success step, after Stripe has created the customer record. The email passed to Rewardful must match the Stripe customer email used for the purchase.
The order matters:
- A visitor arrives through an affiliate link.
- Rewardful records the active referral in the browser.
- Your checkout creates the Stripe customer.
- Your success flow sends the conversion with that customer’s email.
- Rewardful associates the customer and referral.
Don’t fire the conversion call when a visitor merely opens checkout. Don’t pass a guessed email value. Don’t put it on a page that runs before payment or customer creation has completed.
For advanced debugging, Rewardful’s JavaScript API documentation describes access to current referral, affiliate, and coupon data. Use that data to inspect test sessions. Keep customer data out of public logs and browser-console screenshots.
TEST WHICH AFFILIATE RECEIVES CREDIT
A successful script install does not prove that your last-touch rule works. You need controlled tests that reproduce the paths real buyers take.
Use Stripe test mode where your account setup supports it. If you must test live, use a small internal purchase, a real company email, and a documented refund plan.
Run clean browser tests
Run every test in a new private browser session. Old cookies can make a failed test look successful.
Rewardful’s installation flow uses a private-window referral test such as ?via=install. Use that check to confirm the base script is loading. Then run your own affiliate-specific cases.
| Test path | Expected result in a last-touch campaign | Evidence to save |
|---|---|---|
| Click Affiliate A, then convert | Affiliate A receives credit | Referral and conversion record |
| Click Affiliate A, then Affiliate B, then convert | Affiliate B receives credit | Both visit times and credited affiliate |
| Click Affiliate A, then use Affiliate B’s coupon | Result follows your tested coupon rule | Referral, coupon, and conversion record |
| Click on one device, convert on another | No automatic browser carryover assumed | Device details and final attribution result |
The second row is the core proof. Click A’s link, then B’s link in the same fresh browser, then complete signup and payment. Check the Rewardful conversion or referral record after processing. The credited affiliate should be B.
Validate the complete record, not one dashboard number
A credited conversion is not the only thing to inspect. Compare data across Rewardful, your application, and Stripe.
For each test, record:
- Campaign name and current cookie window.
- Affiliate IDs, referral URLs, and coupon codes used.
- Click date, conversion date, and time zone.
- Stripe customer ID and subscription or invoice ID.
- Rewardful conversion status and credited affiliate.
- Browser, device, and consent state.
Store the original result. If an adjustment appears later, add a new record instead of overwriting the first one. You need the history when an affiliate disputes a payout.
HANDLE SUBSCRIPTIONS, REFUNDS, AND PAYOUT STATUS
Affiliate attribution chooses the customer relationship. Commission rules decide what happens after the first payment.
Rewardful connects to Stripe to track recurring invoices and customer changes. The campaign can pay a commission on all invoices or limit rewards to a defined number of invoices.
Match recurring commission rules to your offer
A monthly SaaS subscription can create more than one commission event. Decide whether the affiliate earns on:
- The first paid invoice only.
- Every paid invoice while the customer remains active.
- A fixed number of invoices.
- Revenue after a trial converts to paid.
Write the rule in plain language. State whether the rate applies to collected revenue, whether discounts reduce the commission base, and when a commission becomes payable.
Upgrades, downgrades, cancellations, and refunds change the underlying Stripe billing record. Rewardful states that it keeps commissions aligned with these lifecycle events in its Stripe-based payout process.
Keep refunds separate from paid commissions
A refund can remove or reduce a commission tied to an unpaid invoice. Don’t forecast affiliate cost from a newly created commission record.
Keep at least four states in your internal report:
| Status | What it means |
|---|---|
| Created or pending | The conversion exists but may still change |
| Cleared | The commission passed your review or pending period |
| Paid | Funds were sent to the affiliate |
| Reversed or adjusted | A refund, cancellation, or correction changed the amount |
A commission already paid needs a business rule. Decide whether you offset future earnings, request repayment, or absorb the loss. Record the invoice, refund amount, original payout date, adjustment amount, and approval owner.
FIX THE LIMITS THAT TRACKING CANNOT SOLVE
Rewardful link tracking is browser and cookie dependent. Current documentation does not describe automatic identity matching across browsers or devices.
Cross-device journeys need a clear policy
A buyer may click an affiliate link on a phone, then subscribe from a work laptop. The referral cookie from the phone is not proof that the laptop session belongs to the same person.
Coupon attribution can help because it happens at checkout. It does not depend on the original browser visit. Still, it only works when the buyer enters a valid code and your campaign allows it.
Do not promise affiliates cross-device credit unless you have tested your checkout path and can support the rule. A custom login flow may create more options, but it also needs privacy review and controlled implementation.
Build a support record that someone can reproduce
When a partner says a commission is missing, don’t start with a guess. Collect the facts.
Get the campaign, affiliate ID, referral link, coupon code, customer email or Stripe ID, click time, conversion time, and screenshots of the relevant records. Restrict access to personal data.
Track approved commissions, reversals, failed tests, and time spent correcting attribution issues. Click volume is not program health. A process that creates many disputed records is not working.
If your custom checkout, subscription logic, and affiliate terms need a technical review, Book A Call before expanding partner traffic.
FINAL CHECK BEFORE YOU SCALE
Rewardful last-touch attribution works when the campaign rule, browser tracking, Stripe conversion call, and payout policy agree. The final eligible referral must be traceable from click through customer creation and commission record.
Test Affiliate A followed by Affiliate B in a clean browser. Then test coupons, refunds, and a separate-device purchase. The credited affiliate should match the written rule, not a dashboard assumption.
