Bridgly
Growth1 min read

Referral links that actually work on mobile

Most referral programs leak at the same point: the invited friend installs and lands on a generic home screen with no idea who invited them. Here is the plumbing that keeps a referral intact.

Referral programs fail in a predictable place. Not the incentive, not the share prompt — the moment the invited friend installs.

Where it leaks

The invited person taps a link. They do not have the app. The link opens a browser, they find the store, install, open the app.

They land on a generic home screen. They do not know what they were sent, and your system does not know who sent them. The invite is unrecoverable and the referrer never gets credit.

Two things through the install:

Who referred them, so the referrer is credited.

Where they were going, if the invite was to something specific — a room, a list, a shared item.

Both need to survive the store detour, which is deferred deep linking. Without it, a mobile referral program is largely decorative.

Design details that matter

Unique link per user. A shared link credits nobody.

Short and clean. Referral links get pasted into messages read aloud and retyped. Long query strings get truncated by messaging apps and look like spam.

A working web fallback. Some referrals get opened on desktop. That should land somewhere sensible, not a dead end.

Credit at the right moment. Crediting on install invites abuse. Crediting after a real action — a first session, a purchase — is more robust.

Measure the drop-off, not the total

The number that tells you whether the program works is not shares or installs in isolation. It is the step-by-step drop: shares sent, links opened, installs started, installs completed, referrals successfully credited.

The gap between the last two is the one most programs never look at, and it is usually the biggest.

Frequently asked questions

Why do mobile referrals break?
Because the invited person usually does not have the app. The link opens a browser, they install from the store, and the app launches with no memory of the invite. Both the destination and the referrer are lost.
How do you attribute a referral through an install?
With deferred deep linking. The referrer's identifier is stored against the click and restored the first time the app opens, so the app knows who sent the invite and can credit them.
Should each user get their own referral link?
Yes. A shared link cannot credit anyone. The referrer identifier has to be carried in the link, whether as a path or a parameter.
What is a realistic referral conversion rate?
It varies so widely by category and incentive that any single benchmark is misleading. The more useful comparison is your own rate before and after fixing the install handoff, since that is the step most programs lose people at.

Read more