
App Onboarding
Mobile referral programmes
Plan a mobile referral programme around a useful invitation, a clear qualifying action, controlled rewards and the later experience of referred users.
undefined
A mobile referral programme lets existing users recommend an app and rewards a defined outcome. Referral software can use a unique code or link to track who refers, who accepts and conversions; multistep rewards can follow a referee’s purchase, completed step or brand milestone (Salesforce). Attribution platforms can collect data on clicks, installs and in-app actions, tying deferred deep links to the original campaign (AppsFlyer).
Australian consumer research supports the investment: 58% of consumers name someone they know personally as their most trusted source of information when purchasing, against 3% who rely on ads (impact.com). The same report found 81% say recommendations and referrals matter in their buying decisions, while 41% participate in referral programmes (impact.com).
Start with a reason to recommend the app
Ask what a user can honestly say the app helps someone do. Prompt for referrals only after the user has experienced that benefit. If the useful result remains hard to reach, an incentive may generate invitations without helping those invited.
State who can invite, who can accept, what each person receives and when. Put material account, location and product conditions beside the offer. If a service is available only in selected Australian areas, check eligibility before promising a benefit the invited person cannot use.
Settle four decisions before launch: the useful task the invitation describes, the completed action that qualifies, who receives each reward and when, and any reward limits. Then review whether invited users complete the task and return when another need arises.
Salesforce sets out a launch sequence: build the programme around a product or service customers already value, research the rewards they want, then choose a tool that manages invitations, generates unique codes or links and tracks conversions (Salesforce). Check afterwards how many referrals customers make and how many referees act on them (Salesforce).
Choose a referral link or code
Give each referrer a unique code or referral link. Referral programme software uses that identifier to track who refers, who accepts the referral and the incentive offered, plus referrer and referee activity and conversions (Salesforce). Referral Factory frames programme design around three questions: who can actually refer you, how often you can reach them and what one referral is worth (Referral Factory).
Deferred deep links carry the referral click through installation, so a new user lands on the invited content at first open instead of the home screen, and can be routed into an onboarding flow matched to the channel they came from (AppsFlyer). A deferred deep link is also a measurement event, because it preserves the context of the original click (AppsFlyer).
Keep the message and landing page consistent. If a benefit depends on a completed task or expires, explain that condition before sharing and when the recipient arrives. For email invitations, promotional campaigns or encouragement to message contacts, keep processes aligned with email marketing laws, including the Spam Act rules around consent, identification and unsubscribe (Sprintlaw).
On Android, the system Sharesheet is the simplest way to pass an invitation on. It can suggest targets a custom share solution cannot, applies a consistent ranking, and can tell you when a user completes a share and where it went (Android Developers).
Test every referral link with the app installed and not installed on both platforms; this checks both paths to the referral destination (AppsFlyer). Platform handling differs: Android passes referral data through installation using the Google Play Install Referrer API, while iOS treats the install as a privacy boundary and relies on probabilistic matching (Detour).
Set and track the qualifying outcome
Choose a qualifying outcome that represents a useful completed result, such as a sign-up, purchase or completed in-app step, rather than treating a link click or install as qualification by itself (Salesforce; Sprintlaw). Tell referrers and recipients the rule before they act. Track clicks, installs and in-app actions separately, then make the stated qualifying event trigger the reward (AppsFlyer).
Set rewards and review for misuse
Set eligibility rules and review limits in advance, and check eligibility before awarding a reward. A shared device or repeated account detail may warrant investigation, but one signal alone does not prove abuse. Programme terms can prohibit scraping, abuse and impersonation (Sprintlaw).
State the reward’s value, recipient, timing, expiry, caps and any non-transferability rule, and set a clear window for claims, for example within 30 days (Sprintlaw). If the offer makes a public price claim such as “$50 off” or “$200 credit”, advertised price laws apply, so marketing must match what customers actually receive (Sprintlaw). Australian consumers say higher reward values and simpler programmes would encourage more of them to take part (impact.com).
Choose who can refer and how often to ask
Decide which groups can take part rather than assuming the programme is only for existing customers. Depending on the programme, eligible referrers might include customers, employees or partners, and each group may need different invitation wording and rules.
Referral Factory notes that a business starting out, one that is growing and an established one each need a different referral programme (Referral Factory). Review who can refer and how they are asked as you move between those stages.
Set an asking rhythm that matches how often the business can reach those people. Make that choice explicit so invitations do not become an indiscriminate prompt.
Only a small share of any customer base ever refers, so how often you ask should reflect what one referral is worth to the business (Referral Factory). Revisit that rhythm as the programme grows.
Collect only what the programme needs
The OAIC says an agency may solicit and collect personal information only where it is reasonably necessary for, or directly related to, one or more of its functions or activities; an organisation may do so only where it is reasonably necessary for one or more of its functions or activities (OAIC). The OAIC says proportionality and data minimisation are implicit in those requirements, so identify what the programme needs before collecting referral information (OAIC).
The OAIC says an APP entity may solicit and collect sensitive information only if the individual consents, unless an exception applies (OAIC). This is an additional requirement to the APP 3 rules for personal information (OAIC).
Measure the invited user’s experience
In reporting, compare referral activity and conversions with the qualifying rule, and review whether invited users reach that outcome. Referral software can track referrers, recipients and conversions; attribution platforms can collect click, install and in-app action data and tie deferred deep links to their originating campaigns (Salesforce; AppsFlyer). AppsFlyer names its Measurement Suite as one platform option (AppsFlyer).
Use the findings to make a specific decision. Clarify an invitation, repair a task people cannot finish, revise a reward rule or stop an offer whose cost and user experience do not justify it.
In this guide
- Choosing an app action that can support a referralChoose a referral qualifying action that reflects a useful completed task, with clear eligibility, timing and reversal rules.
- Designing referral sharing without exposing private contactsDesign a referral share flow that lets users choose where to share without importing contacts, while keeping links and conditions clear.
- Preventing repeated referral rewardsDefine one referral entitlement, make credit retries safe, resolve competing claims and reconcile issued rewards.
- Measuring referred users by activation and retentionDefine a referred-user cohort, calculate activation and useful return rates, and compare outcomes without confusing installs or causation.



