Monetization
Deliver partner offers into your paywall logic.
App stores and web stores have different purchase flows. When a partner drives installs with a special offer — discount, extended trial, bundled content — apps have no reliable way to receive the offer code through the install funnel. Most teams either skip the native offer screen or build fragile clipboard-check hacks.
How Forwarded solves it
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. Your paywall logic reads the identifiers and presents the correct offer screen — before the user logs in.
- 1Create a Forwarded Link with the partner offer payload (campaign_id, offer_id, paywall_id).
- 2The partner embeds the link in their campaign page or email. Forwarded serves a branded landing page.
- 3The user taps the Smart App Banner (iOS) or installs from Play with the referrer (Android). The session is marked OPENED.
- 4On first app launch, the SDK resolves the pending session and returns the payload. Show the correct paywall immediately.
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
Partner offers are presented on the first app screen the user sees — before account creation. Conversion rates are higher because the user arrives with context they asked for.
Next steps
See the subscription offer 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 →