Measurement · 7 minute read

Build a referral funnel that reflects customer value

A referral is not successful merely because somebody installed your app. The useful endpoint is the first behaviour that shows they received meaningful value.

Start with the decision

Before selecting events, name the decision the funnel must support. Are you comparing sharing prompts, acquisition channels, reward structures or the quality of referred cohorts? One funnel may inform weekly optimisation while another supports a quarterly programme review.

Separate arrival from activation

Install, account creation and activation answer different questions. For a finance app, activation might require a verified account and first transaction. For a marketplace, it may be a completed order. Document the exact event and qualifying conditions so teams do not interpret “activated” differently.

Keep both sides of the relationship

A useful model connects referrer and referred user while respecting consent and data-minimisation requirements. That connection lets analysts compare referrer cohorts, identify repeat advocates and understand whether incentives create durable behaviour.

Add time as a dimension

Report both conversion and time between stages. A strong install rate can conceal a slow activation journey, while an attribution window that is too short can undercount legitimate referrals. Use windows grounded in your product’s actual consideration cycle.

Validate before you optimise

Run test journeys across Android and iOS, new and existing users, delayed installs, and common Malaysian sharing channels. Reconcile event counts with operational reward records. Only then should funnel changes be treated as evidence of customer behaviour.

Ask about a funnel audit