In this article
A referral link can produce an account without producing a customer. If the reward becomes payable immediately, the business has committed its acquisition budget before learning whether the referred person is eligible or will complete the intended work.
Choose a qualifying action that represents the customer relationship the program is meant to create. Then make the reward’s state understandable: what has happened, what remains pending and why a referral might not qualify. The operating policy matters as much as the invitation itself.
Start with the behavior worth paying for
The right qualification depends on the product. A paid project completing, a new business processing a valid transaction or a person establishing meaningful product use may each be appropriate in different settings. Pick a condition the system can verify and the participant can understand.
Dropbox’s referral documentation distinguishes invitations, pending steps, completed rewards and ineligibility. Its qualification includes actions after account creation. The useful lesson is the separation between registering and completing the program’s requirements, rather than the particular action another product chooses.
Wise’s invitation guidance similarly connects qualification to specified transactions and directs participants to their invite page for the applicable amount. A program should surface the terms relevant to that participant rather than promising a universal reward rule that may not apply.
Write your own condition as an observable event with explicit exclusions. “A new eligible business completes its first paid project, and the payment remains unrefunded through the stated holding period” is easier to operate than “bring us a valuable customer.” Avoid adding hidden requirements after the participant has acted.
Store the referral separately from the reward
The referral record establishes who referred whom and under which program version. The reward record tracks what, if anything, becomes payable. Keeping them distinct lets the business preserve an invitation history even when a reward is declined, delayed or reversed.
A proposed state sequence is invitation, attributed signup, eligibility checked, qualifying action completed, reward pending, reward awarded and, where permitted by the stated policy, reward reversed. Each transition needs a timestamp and a reason. An unresolved eligibility review should remain pending rather than being silently counted as success or failure.
Record the terms in force when the participant accepted the offer. If the program changes its reward or qualifying event, the system needs to know which policy applies to existing referrals. Preserve the original decision history when a support correction changes an outcome.
Work through the reward expense
The following example is fictional. Assume 200 unique people are invited, 80 create attributed accounts, and ten are ineligible under the stated new-customer policy. Of the 70 eligible signups, 40 complete the qualifying paid project. Four projects refund during a 14-day holding period, leaving 36 qualified customers whose rewards are awarded.
Each qualified referral earns $10 for the referrer and $10 for the new customer. Assume both rewards have their full stated cost to the business. The example excludes program software, support, payment costs and other acquisition spending; it measures reward expense only.
| Measure | Calculation | Result |
|---|---|---|
| Total reward expense | 36 × ($10 + $10) | $720 |
| Expense per attributed signup | $720 / 80 | $9 |
| Expense per qualified customer | $720 / 36 | $20 |
| Expense per repeat customer | $720 / 18 | $40 |
For the final row, assume 18 of the 36 qualified customers complete another project within a fully observed 60-day window after qualification. The assumed repeat rate is 50%. The four pre-award reversals are 10% of the 40 initial qualifying actions. Neither rate is a benchmark or a claim about fraud prevalence.
Paying both rewards at signup would cost $1,600 for the same 80 signups. If all later behavior stayed identical, that would be about $44.44 per eventual qualified customer. This is a cost comparison under fixed assumptions, not proof that delaying the reward leaves behavior unchanged. A later reward may affect participation, so that tradeoff deserves its own evaluation.
Make attribution and eligibility answerable
Decide which referral receives credit when a person encounters several links, and define the attribution window. Preserve the identifier that connected the invitation to signup. Do not let every subsequent link click create another payable referral.
Check eligibility at the entity level that matters to the program. If the offer is for a new business, a new email address from an existing business may not qualify. Conversely, shared networks or devices do not by themselves prove that two legitimate customers are the same person. Use the agreed rules and retain a route to resolve mistakes.
The participant needs a useful explanation, such as an existing-account restriction or an incomplete qualifying action. Avoid exposing another person’s sensitive account activity in the referrer’s status view. “Qualification pending” can provide enough information without revealing payment details or private work.
Decide what happens after a reversal
In the example, the holding period prevents four rewards from being awarded because the underlying projects refund first. The system should record the reversal and its reason, then update the participant’s status according to the published terms.
Later reversals need a separate policy. If a reward has already been spent or paid, can the business recover it, offset a future reward or accept the cost? Do not assume a negative balance is either permitted or desirable. Make the intended behavior explicit before implementation and communicate the conditions that affect participants.
Use an adjustment entry rather than erasing the original award. That preserves the financial and customer-support history. A retry, delayed event or manual correction should not issue the same reward twice. Tie the award to a unique qualification record and make repeat processing safe.
Evaluate the customers after the reward
Follow qualified customers into the behavior the program is meant to support: repeat work, paid consumption or another relevant outcome. Keep qualification and later success separate. A reward can have been correctly earned even when the customer never returns.
Report reward expense per qualified customer with its full denominator and observation window. Show pending referrals separately, and avoid comparing a mature cohort with one whose holding period has not ended. If the business wants total acquisition cost, add the other program costs rather than relabeling reward expense as the complete answer.
Attribution also does not establish incrementality. Some referred customers might have arrived without a reward, and an existing customer’s invitation may influence people beyond the recorded link. A causal claim requires a suitable design; the ledger alone establishes who qualified and what the program spent.
For the larger mechanism, see growth loops and funnels. In the product growth model, carry qualified customers and actual reward expense forward. A signup count is useful at the invitation stage; the funding decision needs the customers and costs that remain after the program’s own rules have been applied.
Sources
Something we should clarify?
Suggest a correction


