Growth
Carry referrer identity through install.
Referral programs break at the install boundary. A user shares a referral link; their friend opens it in mobile Safari, taps 'Get the app,' and installs — but the referral code never reaches the app. The app has no way to credit the referrer or activate the referred user's welcome bonus without asking the user to re-enter a code.
How Forwarded solves it
Embed the referral metadata (referrer_id, referral_code, reward_type) in a Forwarded Session. The link visitor triggers session creation; the install resolves it; the SDK returns the payload before the user completes signup. Your onboarding flow reads the referral context and credits the referrer at claim time.
- 1User A shares their unique Forwarded Link. The link contains their referrer_id and a referral_code.
- 2User B visits the link on mobile web. A session is created with the referral payload.
- 3User B installs via Smart App Banner or Play. The session is marked OPENED with the platform recorded.
- 4On first launch, the SDK resolves the session. Your onboarding reads referrer_id and referral_code. After User B signs up, claim the session with User B's user ID to permanently bind the referral.
Payload schema
This is the JSON you attach to the Forwarded Link. Your app reads it from the resolved session object. Fields shown here are illustrative — use the keys your own backend and mobile SDK expect.
Outcome
Referral attribution is deterministic at install time. No code re-entry. Credit is applied automatically on first session claim.
Next steps
See the referral example
Full worked example in the docs — payload definition, SDK integration, and session claim.
Create a Forwarded Link
Configure your payload, set the landing page, and get a shareable URL in the dashboard.
New to Forwarded? Read the quickstart →