A partner can send the right visitor to your site and still lose credit at checkout. The problem is usually not the affiliate link. It is the referral cookie, the campaign rule, or a domain handoff that broke in the middle.
Rewardful partner cookies keep referral attribution available after a visitor leaves the first landing page. Set the campaign rule first, then test the full path before you give partners a live link.
SET UP REWARDFUL PARTNER COOKIES
Rewardful uses first-party cookies for referral tracking. It does not offer a separate feature called a “custom partner cookie” that lets you define an arbitrary cookie name or schema.
Your practical controls are the campaign cookie window, attribution model, cross-domain settings, and explicit referral-source tracking. Rewardful documents these controls in its customizable cookie overview.
Configure the campaign cookie window
Open the campaign you want to change and edit its Cookie window value. Rewardful’s default referral window is 60 days, but the right setting depends on your sales cycle.
A 14-day trial product may need a 30-day window. A higher-value B2B product with demos and procurement steps may need a longer period.
The visitor must convert inside that campaign window. A signup after the window expires won’t credit the original partner.
Pick the attribution rule before launch
New Rewardful campaigns use first-touch attribution by default. The first eligible affiliate referral receives credit.
You can use last-touch attribution in the campaign’s Advanced Settings when the partner who created the final visit should receive credit instead. Don’t treat this as a minor setting.
First-touch and last-touch rules can produce different payout results for the same customer journey.
Write the rule into your partner terms. Partners need to know what happens when a prospect clicks more than one referral link.
CONTROL ATTRIBUTION ON A SPECIFIC PAGE
Sometimes a partner sends traffic to an untagged page, a webinar registration page, or a landing page managed outside the normal link flow. In that case, you can place a known partner source into the Rewardful referral cookie.
Rewardful’s JavaScript API supports rewardful('source', 'partner-token'). Replace partner-token with that affiliate’s link token.
Use it only on a page that belongs to one named partner. The call writes that referral source and overwrites an existing referral stored for the visitor. It is not a neutral fallback.
Use direct page tracking with care
Direct source tracking works for a controlled co-marketing page or a partner-specific offer. It is a poor fit for a general pricing page shared by every channel.
If Partner A’s token runs on /pricing, a visitor who first arrived through Partner B can be reassigned. That creates a payout dispute you could have avoided.
Rewardful also supports the referral=<UUID> URL parameter. This loads an existing referral into the cookie. It is useful when you pass a known referral between connected properties.
Review the Rewardful JavaScript API before adding frontend tracking calls. Keep the partner token out of a generic site-wide script.
TRACK USERS ACROSS DOMAINS AND SUBDOMAINS
A referral flow often crosses more than one host. Your marketing site may sit on www.example.com, while signup runs on app.example.com or a separate product domain.
Rewardful tracks subdomains automatically when its script is installed on each subdomain involved. Missing the script on one stage of the funnel is enough to lose the referral.
Add every separate domain to data-domains
For different root domains, add the data-domains attribute to the Rewardful script and list the domains that belong to the same journey. Install the script on every listed domain.
Rewardful adds a referral=<UUID> parameter to outbound links between those approved domains. The destination site then loads that referral into its own first-party cookie.
The cross-domain tracking documentation shows this behavior and the required data-domains setup.
Do not assume a redirect provider, checkout host, or help center is covered. Test each real host that a prospect crosses before payment or signup.
Run a controlled referral test
Use an internal test partner or a low-risk test path. Start in a new private browser window so an old referral cannot affect the result.
- Open a known affiliate link with its
viaparameter. - Confirm the landing page loads the Rewardful script.
- Click through each domain and check that the destination URL receives
referral=<UUID>when separate domains are involved. - Complete a test signup or conversion using your normal production path.
- Confirm the expected partner and referral appear in Rewardful.
For browser-level debugging, inspect Rewardful.referral and Rewardful._cookie in the console. Rewardful labels _cookie as a debugging property, not a stable integration interface.
FIX COOKIE FAILURES BEFORE YOU SCALE
Most Rewardful partner cookie failures come from a short list of setup issues. Check these before changing commission rates or asking partners to send more traffic.
- Your consent platform blocks the Rewardful script until consent, but the visitor never accepts the required category.
- A cached landing-page template still lacks the Rewardful script or the current
data-domainsvalue. - The script is present on
wwwbut missing from the app, checkout, or account subdomain. - The campaign cookie window expired before the visitor converted.
- A later affiliate click replaced attribution under a last-touch setup.
- A direct
sourcecall overwrote the referral that was already stored. - Browser privacy settings, private mode, extensions, or cleared site data prevented the cookie from persisting.
First-party cookies avoid the problems created by third-party cookie phase-outs. Rewardful confirms that it does not rely on third-party cookies for referral tracking in its cookie tracking FAQ. That does not remove the need for consent-aware testing.
Keep a support record for every failed test. Save the landing URL, partner ID, campaign, link type, referral UUID, date, browser, expected result, and screenshot. Don’t overwrite the original test record when you find a correction. Add the new result beside it.
FINAL CHECKS FOR PARTNER ATTRIBUTION
Rewardful partner cookies work when the campaign rule, referral source, and conversion path agree. Set the window. Choose first-touch or last-touch deliberately. Install tracking on every domain that matters.
Test the same path a real buyer uses, not only the first click. Attribution is only reliable when the full journey is verified.
