WebmasterID logoWebmasterID
Conversion & funnels

Referral funnel

The referral funnel measures how existing users bring in new ones: being prompted to invite, sharing, the invitee clicking, the invitee signing up, and the invitee activating. Each stage has its own drop-off. Referral carries pitfalls that other funnels do not — two-sided incentives that can attract gaming, attribution of who gets credit, and network interference that complicates experiments measuring it.

Partially verified

The stages and their drops

A referral has more stages than it appears: the user must be prompted at a good moment, choose to share, the invitee must receive and click, then sign up, then activate. A break at any stage stalls the whole chain — a generous reward is wasted if the invite prompt never fires at the right moment, or if invitees sign up but never reach value. Instrument each stage so you fix the actual bottleneck.

Pitfalls unique to referral

Two-sided incentives (reward both referrer and invitee) lift participation but invite gaming — self-referrals, fake accounts — so add fraud guardrails and measure activated referrals, not raw signups. Attribution is genuinely ambiguous when several channels touch an invitee; pick a rule and apply it consistently. And experiments on referral are prone to network interference, since the treatment spreads between users — a reason to consider cluster designs.

It is fed by activated users and is itself a growth loop back into signup.

How it appears in analytics and logs

Many invites but few referred signups points to a weak invitee experience or untrustworthy invite; few invites points to a weak or mistimed prompt.

Diagnostic use case

Instrument the full invite-to-activation chain so you optimise the weakest stage, and guard incentives against gaming and self-referral.

What WebmasterID can help detect

WebmasterID's first-party events let you follow each referral stage and see where the invite-to-activation chain breaks.

Common mistakes

Privacy and accuracy notes

Referral flows handle contacts and addresses; collect them with consent, avoid scraping address books, and do not over-retain invitee data.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.