A referral program can pay the wrong partner even when your checkout works perfectly. The problem is usually the attribution rule, not the commission rate.
Rewardful attribution decides who owns the customer when more than one affiliate sends that person to your site. Last-touch attribution gives credit to the most recent eligible affiliate link before the customer converts.
Set the rule at campaign level, confirm your checkout carries the referral data, then run a controlled two-affiliate test.
Decide When Last-Touch Attribution Fits Your Program
Last touch is a commercial rule. It rewards the affiliate that drove the final qualifying visit before signup or purchase.
This often fits SaaS programs with comparison sites, partner reviews, newsletters, and retargeting content. The affiliate that gets the customer back to your pricing page receives credit.
First touch and last touch pay different partners
Rewardful uses first-touch attribution by default for new campaigns. Under first touch, the first affiliate link a visitor clicks keeps credit.
Under last touch, the newest affiliate link wins if the visitor has not converted yet. Rewardful documents both options in its campaign settings overview.
Neither model is automatically fair. You need a policy that matches how you want partners to promote your product.
Use first touch when you want to reward the partner that introduced a new buyer. Use last touch when the final referral has more value in your partner model.
Conversion ends the referral competition
Last touch only matters before the customer converts. Rewardful permanently associates the customer with the affiliate after conversion.
A later affiliate click should not move an existing customer to another partner. Do not test last-touch behavior with a customer who already has a completed subscription or purchase.
Last touch selects the most recent eligible referrer before conversion. It is not a rule for moving credit between affiliates after a customer exists.
Write this rule into your affiliate terms. Include the cookie window, the point when conversion occurs, and how you handle manual corrections.
Configure Rewardful attribution for Last Touch
Rewardful attribution is configured per campaign. If you run separate campaigns for partners, creators, or customer referrals, review each one.
Do not assume a new campaign copied the rule from an older one.
Change the campaign attribution type
Use this dashboard process:
- Open your Rewardful dashboard and select Campaigns.
- Open the campaign that should use last-touch credit.
- Select Edit Campaign.
- Open Advanced Settings and find Affiliate Attribution.
- Select Last Touch Attribution.
- Save the campaign, then record the change date in your operating notes.
The setting controls which affiliate receives credit when a prospect visits through multiple affiliate links. There is no need to change your commission rate to enable this rule.
Do not switch active campaigns without telling affiliates. A partner may have built content and paid traffic around a first-touch agreement.
Set a cookie window that matches the buying cycle
The cookie window is the number of days a referral click remains eligible for credit. Rewardful’s default cookie duration is 60 days, but the value is configurable per campaign.
A 14-day trial with a self-serve card checkout may work with a shorter window. Annual contracts with demos, legal review, and procurement may need a longer period.
Use a window your team can explain and enforce. Rewardful’s cookie validity guidance confirms that clicks outside the configured period do not receive attribution.
Changing the window does not fix a missing checkout handoff. It only defines how long a valid referral can receive credit.
Check the Checkout Handoff Before You Test
Last-touch rules depend on a full path. The visitor must click an affiliate link, reach your site, create a customer, and complete the tracked payment flow.
A working landing-page redirect is not enough.
Confirm the Stripe connection and customer flow
Rewardful monitors activity in your connected Stripe account to identify referred customers and generate commissions. Check that the right Stripe account is connected before testing.
Use Rewardful’s guide to connect your Stripe account if the account, live mode, or business entity changed.
Then trace the real customer path:
- The affiliate link opens the same domain where your referral tracking runs.
- Your signup flow does not drop the visitor into an unrelated domain without carrying the referral state.
- Your billing process creates the Stripe customer and subscription in the Stripe account connected to Rewardful.
- The payment reaches the same campaign and product rules your live referrals use.
A free trial can still be part of the path, but the result depends on when your billing setup creates the Stripe customer and when Rewardful records the conversion.
Treat custom checkout flows as an integration task
Hosted and standard integrations need less work than custom billing flows. A custom React, Rails, API, or embedded checkout may create the Stripe customer after several redirects or server-side calls.
In that case, inspect where the referral value is stored before customer creation. Do not overwrite it with a hard-coded affiliate token.
Rewardful documents manual customer attribution through Stripe customer metadata. The metadata key is referral, and the value must be a valid affiliate token or referral ID. Use this method to repair a verified exception, not to mask a broken normal flow. See the official manual attribution instructions.
For Rails forms that create Stripe customers, Rewardful’s Rails integration method requires the data-rewardful attribute. Other frameworks need their own implementation review.
If your flow uses a billing portal, multi-domain signup, or server-side Stripe creation, Book A Call before changing customer metadata in production.
Test That the Last Referral Receives Credit
Do not test by clicking links in a normal employee browser and then checking a dashboard later. Existing cookies, old customers, extensions, and cached sessions can invalidate the result.
Run one clean test and keep an evidence record.
Build a controlled two-affiliate test
Create or select two active internal test affiliates. Call them Affiliate A and Affiliate B. Use a test email address that has never created a customer in your production Stripe account.
Run the sequence in one fresh browser profile or a private session with extensions disabled:
- Record the campaign name, attribution type, cookie window, test email, and start time.
- Open Affiliate A’s referral link and confirm that it lands on the correct page.
- Wait a few minutes, then open Affiliate B’s referral link in the same browser session.
- Complete the normal signup and checkout flow using the unused test email.
- Wait for the normal Rewardful and Stripe processing window, then review the conversion and commission records.
Use a Stripe test environment when your Rewardful setup supports the same path there. If you must test live billing, use an approved low-risk internal purchase and get finance approval first.
Do not manually set the referral metadata during this test. That changes the result you are trying to validate.
Verify the result in Rewardful and Stripe
Open the new referral or conversion record in Rewardful. Affiliate B should receive credit because B generated the last eligible click before conversion.
Check these fields:
- The customer email and Stripe customer ID match your test purchase.
- The campaign matches the campaign you edited.
- The credited affiliate is Affiliate B.
- The commission follows the campaign’s rate and product rules.
- The click and conversion timestamps fit inside the cookie window.
If Affiliate A receives credit, first confirm that B’s link was clicked after A’s link in the same browser profile. Then check whether B used the same campaign and whether B’s traffic source was eligible.
Keep a screenshot of the result, the two referral URLs, timestamps, and the Stripe customer ID. This becomes your last trusted test record.
Troubleshoot Wrong or Missing Referral Credit
A missing commission and wrong affiliate credit are different failures. Do not fix both by editing Stripe metadata.
First identify where the handoff broke.
Separate click failures from customer failures
If Rewardful shows no referral at all, start with the affiliate link. Confirm the link token is valid, the landing page loads, and the visitor did not block cookies or use a different browser for checkout.
If Rewardful shows a referral but no conversion, inspect the customer and payment path. Confirm the Stripe customer was created in the connected account and that the checkout did not lose referral data during a redirect.
If the customer appears under the wrong affiliate, check the click order, campaign setting, cookie window, and any existing customer record. Last-touch Rewardful attribution cannot replace the affiliate on a customer that converted earlier.
Check the exceptions that change attribution
Several conditions can produce a result that looks wrong:
- A test ran after the campaign cookie window expired.
- The visitor clicked a second affiliate link in another browser or device.
- A promotion code or manual metadata update assigned a referral outside the normal link flow.
- The affiliate used traffic sources your program blocks.
- The customer had converted before the test began.
Promotion codes can give affiliates a trackable checkout route when link tracking is not available. Rewardful explains how to use promotion codes for referral tracking. Test codes separately from referral links. Do not assume they follow every cookie-based scenario.
For paid search and restricted traffic, review Rewardful’s Traffic Source Control rules. A blocked referral is a policy outcome, not a tracking defect.
Run Attribution as a RevOps Control
Rewardful attribution needs an owner. Assign campaign settings to growth or partnerships. Assign Stripe customer flow to engineering. Assign commission corrections to RevOps or finance.
Keep a simple change log. Record the campaign, attribution type, cookie window, change date, owner, approval, and test result. Never overwrite an earlier test record.
Measure accepted outcomes, not dashboard activity
Clicks show interest. They do not prove revenue or correct attribution.
Track a monthly sample of referred customers and review the records your team accepts without correction.
| Metric | What it tells you |
|---|---|
| Correctly attributed test conversions | Whether the configured rule works |
| Manual attribution corrections | Whether checkout handoffs are failing |
| Reversed or refunded commissions | Whether credited revenue held up |
| Time spent on disputes | Whether the policy is creating support work |
A program that creates many commission records but needs repeated correction is not operating well. Fix the campaign rule and billing handoff before expanding affiliate recruitment.
Final Thoughts
Last-touch attribution works when the campaign setting, referral cookie, checkout flow, and Stripe customer record all point to the same result.
Configure Rewardful attribution per campaign, test Affiliate A against Affiliate B in a clean session, and retain the evidence. The last eligible referral should receive credit once, before conversion, with no manual override hiding the result.
