Referral eligibility · Documentation-based guide with original exercise

Expired affiliate cookie: checks before counting a commission

Content updated:

Scope: Documentation-based guide reviewed on 8 October 2026. Examples are fictional and protocols proposed; they are not product tests performed by CallsIQ.

Short answer

Cookie duration alone does not define how long commissions are paid. Check the event establishing attribution, window resets and later payments. Programme terms take precedence over assumptions based only on the first click date.

Key verification: The worksheet must separate click, qualifying event, accepted attribution and paid period.

Sources and limitations

A referral may register while a cookie exists and pay after it expires. Another may visit early but register too late. Counting days until any payment cannot resolve these cases: you need the programme’s qualifying event and accepted relationship. This guide prepares a terms worksheet, without inventing commission entitlement or repairing a particular rejection.

Four separate worksheet questions

Record window start, duration, user-attribution event and how long later revenue is remunerated. Add existing-customer, affiliate-switch and device rules. Mark missing terms for confirmation. Deleted cookies, storage restrictions or another browser can limit evidence; do not promise recovery of every referral.

Three fictional fixed-window scenarios

Expired affiliate cookies: check commission eligibility: table 1
ScenarioRegistrationFirst paymentDeciding question
Click on day 0; 30-day windowDay 20Day 40Is the relationship established at registration?
Click on day 0; no new visitDay 40Day 41Is there another attribution rule outside the window?
Already-attributed customer and renewalEarlierDay 90Does the commission term include that renewal?

The table neither grants nor denies commission: it identifies the term needed to decide. A fixed thirty-day window is an exercise assumption. In a programme resetting expiry after a qualifying visit, expiry changes. Record full timestamps and time zone where boundaries matter; a date alone does not resolve an exact-cut-off case.

Reditus and programme-specific terms

Reditus’s installation help describes configurable cookie duration and payment-data integration. Evaluate it if you manage these rules for a SaaS, and inspect the actual collaboration terms. This reference establishes neither universal duration nor your specific attribution.

Accept the worksheet by having another person apply identical rules to all three cases and retain programme evidence. Use examples or an authorised test environment, rather than manufacturing affiliate clicks or registrations. CallsIQ has not tested these cases in Reditus. A small publication can start with documentary records before purchasing another tool.

Sources and limitations

Documentary review: . Content type: Documentation-based guide with original exercise.

Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.

How to report a correction

Check current terms

Consider these options if they solve the problem described. Confirm features, limits and availability in your country.

ReditusAffiliate link

The labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.

How this guide was prepared

Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.