Every tap. A better start.
Carry useful context from shared links into your app.
Make the first tap feel right.
New users need a clear welcome. Returning users know what they want. Give both a direct route into your product.
- App-aware destinations
- Consent-aware native SDKs
- Separate Apple aggregate reports
Little details.
A bigger difference.
LinkRunway combines mobile deep links with deterministic click attribution and native SDKs. Android referrers and explicit referral codes support install recovery; Apple postbacks provide a separate aggregate view.
Configure both platforms
Register app identifiers and domain associations. Add store destinations for users who have not installed your app.
Respect the user’s choice
Enable SDK tracking after the appropriate consent. Privacy-suppressed clicks do not receive attribution tokens, and anonymous activity is not treated as verified identity.
Measure the outcomes you control
Use your backend to report signups and payments. Apple privacy postbacks are verified and reported in aggregate, separately from customer-level attribution.
From a tap to the right place.
Explore an installed-app journey, step by step.
A little introduction.
Someone taps a shared link to content they want to see.
Good questions.
Clear answers.
Does the SDK navigate for us?
No. It resolves the incoming link and returns its app path and context. Your app validates that path and handles navigation.
What is included for SKAN and AdAttributionKit?
Signed postback verification, deduplication, development-mode separation, and conversion-rule configuration are included. Your released app must apply conversion updates and send real postbacks for deployment validation.
Can we measure users who decline consent?
The SDK does not track without consent. Privacy-suppressed links do not issue attribution tokens. Aggregate Apple measurement is reported separately, without joining it to customer identity.