Physical acquisition
Route physical-world scans through deterministic install paths.
QR codes at events and retail locations drive app installs, but analytics are broken. A QR scan on an iPhone opens Safari, redirects to the App Store — and all event and booth context is lost. Post-install analytics can attribute to 'QR code' at best, but not to a specific event, session, or booth.
How Forwarded solves it
Each booth or session has its own Forwarded Link. The QR code points to the Forwarded Link's public URL. When the user scans, visits the link, and installs, the session carries event_id and booth_id. The app resolves the payload and can display an event-specific welcome screen, apply an activation reward, or trigger event-specific onboarding.
- 1Generate one Forwarded Link per booth or activation point. Embed event_id, booth_id, and any activation context.
- 2Print the QR code pointing to the Forwarded Link URL. Update the QR code only if the event changes — the link itself is permanent.
- 3Attendee scans the QR, visits the landing page, taps the banner or installs from Play. Session is created with scan context.
- 4On first app launch, SDK resolves the session. Display event-specific welcome content (booth name, activation offer).
- 5Webhook delivers session.claimed events for each attendee. Attribution is exact — booth, event, platform, and time.
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
Physical acquisition is now fully attributable. Event and booth analytics are exact. Activation rates per location can be compared directly.
Next steps
See the QR 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 →