An affiliate can introduce a customer months before that customer opens Stripe Checkout. If a later touch overwrites that referral, you pay the wrong partner and lose trust with the one who created demand.
First touch attribution gives credit to the affiliate who generated the first tracked visit. Rewardful supports this model natively, but your campaign settings, scripts, checkout path, and recovery process must agree.
Set the rules before you invite affiliates or start reviewing missing commissions.
DEFINE THE ATTRIBUTION POLICY FIRST
Rewardful can run campaigns with first-touch or last-touch rules. New campaigns default to first touch, but check every campaign before launch. A copied campaign may use different settings.
Under first touch, the first eligible affiliate click gets credit. A later affiliate link does not replace that initial referral. Under last touch, the most recent eligible affiliate gets credit instead.
Read Rewardful’s campaign settings overview before changing a live campaign. Attribution settings affect partner expectations and historical reporting.
Use first touch when partners create demand
First touch works well when affiliates publish tutorials, reviews, comparison pages, newsletters, or long-form content. These partners often start a buying journey but don’t control the final visit.
It also reduces commission disputes. The rule is simple: the first eligible referral owns the customer relationship for that campaign.
Use this policy when your goal is to reward discovery, not the final coupon click.
Put the operating rules in writing
Your affiliate terms should state:
- The campaign uses first-touch attribution.
- The cookie window length and when it starts.
- Whether commissions apply to one payment or recurring paid invoices.
- How refunds, cancellations, and chargebacks affect unpaid commissions.
- How direct signups and attribution disputes are reviewed.
Don’t tell affiliates that every click earns a commission. A click is a tracking event. A paid Stripe invoice is the commercial event that can create a commission.
A campaign setting is not a complete attribution policy. Your terms must cover the cases a cookie cannot capture.
CONFIGURE FIRST TOUCH ATTRIBUTION IN REWARDFUL
Start in Rewardful, not in custom code. Native configuration is easier to test and gives affiliates one consistent source of truth.
Go to Campaigns, select the campaign, then choose Edit Campaign. Open Advanced Settings, find Affiliate Attribution, and select First Touch Attribution.
Rewardful documents this setting in its guide to first or last touch attribution. Confirm the setting on every active campaign, including private or invite-only programs.
Set a cookie window that fits the sales cycle
Rewardful uses first-party referral cookies. The default cookie window is 60 days. You can change it in the campaign settings.
A 14-day trial product may work with 30 to 60 days. A high-ticket annual plan with demos and procurement may need a longer window. Don’t set 365 days because it sounds generous. Set a period you can explain and support.
The cookie window is not a revenue guarantee. It only controls how long the referral remains eligible before signup.
Install the script before traffic arrives
Place the Rewardful script on every page where a visitor can land, browse, sign up, or start payment. That includes pricing pages, comparison pages, signup pages, login redirects, and account creation screens.
Check the live page source after deployment. Confirm the correct Rewardful API key is present once, not twice. Duplicate scripts can create confusing tracking behavior.
Keep campaign links clean. Add UTM parameters for channel reporting, but don’t remove the affiliate token or replace the landing URL with an untracked redirect.
KEEP THE REFERRAL THROUGH DOMAINS AND CHECKOUT
Many SaaS teams lose attribution between www.example.com, app.example.com, and a separate billing or documentation domain. The prospect clicked the link. The system simply lost the context.
Rewardful tracks subdomains when its script is installed on each relevant subdomain. Separate root domains need cross-domain configuration.
Configure cross-domain tracking correctly
For two different domains, add the documented data-domains attribute to the Rewardful script and list each domain that must pass referral context.
Rewardful adds a referral=<UUID> parameter to links between the configured domains. Existing parameters remain in place. Its cross-domain tracking guide also states that this feature is available on Growth and Enterprise plans.
Review these paths in your product:
- Marketing site to application signup.
- Application signup to Stripe Payment Link or Stripe Checkout.
- Trial conversion page to account billing page.
- Regional domains, such as
.comand.io. - SSO, magic-link, and password-reset redirects.
Know where native tracking ends
Rewardful can track the referral click and apply the campaign rule. It cannot repair a checkout path that removes parameters, creates a new browser context, or sends users through an untracked domain.
Custom application logic is needed when you run a bespoke signup flow, server-side account provisioning, or a multi-product system with separate Stripe accounts. In those cases, store the captured referral ID with the pending signup record before the visitor reaches payment.
Do not build a second attribution engine unless you need one. Two systems deciding who owns a customer produce disputes.
CONNECT ATTRIBUTION TO THE STRIPE CUSTOMER
Rewardful uses Stripe data and webhooks to identify customer events, paid invoices, and refunds. It does not process the payment itself. Your Stripe Customer is the record that ties a buyer to referral and commission data.
The normal flow is native: affiliate click, Rewardful referral capture, account signup, Stripe Customer creation, then Stripe billing activity. Keep that path intact.
Let Rewardful handle the normal purchase path
For standard integrations, avoid writing referral metadata yourself on every signup. Rewardful already manages attribution when its script, campaign, and Stripe connection are configured correctly.
Stripe sends event notifications after changes occur. Review Stripe’s webhook documentation and keep your Stripe integration connected. A failed webhook connection can delay or prevent downstream commission records.
Commission timing should match collected revenue. Rewardful can create commissions when Stripe reports paid invoice activity, then adjust unpaid commissions for refunds.
Use metadata for recovery, not as a shortcut
A direct signup can bypass the normal cookie flow. The customer may register from a bookmarked page, use a different device, or complete payment after a sales-assisted handoff.
Rewardful’s documented fallback is manual attribution. Add the affiliate’s token as a referral value in the Stripe Customer metadata, then generate the commission in Rewardful. Follow Rewardful’s manual attribution process.
Stripe metadata is a key-value store. It can exist on Customers, Subscriptions, PaymentIntents, and other objects, but don’t assume metadata on one object automatically becomes metadata on another. Check Stripe’s metadata rules before building a custom flow.
Use this custom logic only when the referral record is missing:
- Look up the Stripe Customer and the Rewardful referral record.
- Confirm the affiliate token against your click or partner evidence.
- Check that no earlier eligible referral already owns the customer.
- Add
referral: affiliate_tokento the Stripe Customer metadata. - Create or approve the commission in Rewardful.
- Save the reviewer, reason, source evidence, and date.
Never delete existing Stripe metadata when adding the referral value. Preserve the original data.
VERIFY THE WHOLE FIRST-TOUCH FLOW
A green status in Rewardful does not prove your production funnel works. Test the complete path before affiliates send real traffic.
Use a test affiliate. Use a new browser profile. Use a unique email address. Then check each record after the payment event finishes.
Run a controlled smoke test
Complete this sequence:
- Open a real affiliate referral link in a clean browser.
- Visit the marketing page, signup page, and billing page.
- Create an account and complete a test purchase or test subscription.
- Find the Stripe Customer and confirm the expected customer details.
- Confirm the referral and commission in Rewardful.
- Refund the test payment and check the resulting commission adjustment.
Repeat the test across each domain and subdomain. Then repeat it with UTMs, an existing query string, and a mobile browser.
Test first touch properly. Click Affiliate A’s link, then Affiliate B’s link, then sign up. Affiliate A should receive the credit when the campaign uses first touch.
Keep an attribution audit record
Do not overwrite a disputed record with a corrected value and move on. Keep the original result, the revised result, the affiliate token, Stripe Customer ID, invoice ID, and review reason.
Track these fields in a spreadsheet or database:
| Field | What it proves |
|---|---|
| Affiliate token | Which partner claimed the referral |
| Stripe Customer ID | Which buyer record received attribution |
| First click date | Whether the cookie window was active |
| Signup date | When the customer entered the product |
| Paid invoice ID | Which revenue event created the commission |
| Review decision | Why a manual correction occurred |
Measure accepted commissions, not total commission records. A process that creates many records but needs hours of cleanup has failed.
FIX COMMON ATTRIBUTION FAILURES
Most affiliate tracking problems are not software bugs. They are broken paths, unclear rules, or missing evidence.
Start with the customer record, then work backward through the referral click, signup, payment, and commission.
Cookie loss and cross-device signups
Cookies can disappear when the visitor changes browsers, clears site data, uses privacy tools, or signs up later on another device. First-party cookies improve reliability, but they do not identify the same person across every browser.
Ask affiliates for the original referral URL when a claim arrives. Compare it with click data, signup time, email address, CRM notes, and Stripe Customer details.
Do not automatically credit a partner because a prospect says they saw a post. Require a reproducible record.
Direct signups and conflicting referral sources
A direct signup has no usable referral cookie. Use manual attribution only when you have evidence that fits your written policy.
Conflicting referrals need one rule. With first touch attribution, do not replace the initial eligible affiliate because a second partner sent a later link. Check campaign settings before changing any record.
Promotion codes can create another conflict. If you use them, decide whether a code is a discount only, a referral source, or both. Don’t allow a checkout code to overwrite a valid earlier referral without a documented policy.
Failed redirects and missing parameters
A redirect can strip referral or UTM parameters before Rewardful receives them. Common causes include link shorteners, login middleware, consent tools, and custom routing.
Test redirects with the full affiliate URL. Check the address bar after every handoff. If a parameter disappears, fix the redirect before you expand the campaign.
For a complex funnel with multiple apps, Stripe accounts, or sales-assisted attribution, Book A Call to map the record flow and exception rules.
FINAL THOUGHTS
Rewardful gives you native first-touch campaign settings, referral cookies, Stripe-based commission tracking, and a manual recovery path. The system works when those pieces follow one documented policy.
Test the exact routes customers use. Keep a record of exceptions. Pay commissions based on accepted attribution, not assumptions made after the fact.
