Partnerships
Editable co-branded pages with auditable session claims.
Partnership deals involve marketing teams from two companies, but app engineers end up manually creating deep links for each partner. When deals change, the engineering team has to update links, rebuild, and redeploy. There's no visibility into which sessions from a partner campaign were actually claimed.
How Forwarded solves it
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. Engineering only configures the payload schema once. Every install that comes through the link generates a session with the partner context. Claim events are delivered via webhook and inspectable in the dashboard.
- 1Create a Forwarded Link for the partner campaign. Payload includes partner_id, campaign_id, routing flags.
- 2Share the Forwarded Link's public URL. The partner marketing team can edit the landing page without touching the payload.
- 3Every landing page visit creates a session. Installs are tracked by platform. Payload is protected from client-side modification.
- 4Sessions are resolved and claimed in the app. Webhooks deliver session.claimed events to your backend for CRM attribution.
- 5Use the Forwarded dashboard to inspect session counts, platform breakdown, and claim status for each partner campaign.
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
Partners get editable landing pages. Engineering gets reliable attribution. Finance gets auditable claim data for revenue share calculations.
Next steps
See the partner campaign 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 →