Use cases

One primitive. Every acquisition flow.

Forwarded Sessions carry developer-defined JSON payloads through install and app-open. Every flow — growth, partnerships, product — shares one signing, one API, one SDK. Add a new use case by attaching different JSON to a new link.

Monetization

Subscription offers

Attach the partner offer identifiers (campaign_id, offer_id, paywall_id) to a Forwarded Link. When the user installs the app via the Smart App Banner or Install Referrer, the SDK resolves the session and returns the payload.

Growth

Referrals

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.

Collaboration

Invites

Route the invitation link through Forwarded. The link carries team_id, invite_id, and role.

Partnerships

Partner campaigns

Create one Forwarded Link per partner campaign. Give the partner's marketing team access to edit the landing page (copy, logo, CTA) through the Forwarded dashboard.

Physical acquisition

QR campaigns

Each booth or session has its own Forwarded Link. The QR code points to the Forwarded Link's public URL.

Need a custom payload? Forwarded payloads are plain JSON objects — attach any JSON up to 8 KB. No schema required beyond what your app reads.

Payload concepts →