Give your app a destination.

Give the app a verified domain.

Add the domain in Settings, publish its DNS verification record, and point it at the API through your HTTPS hosting setup. Register the app in Integrations with that domain.

• iOS: inspect /.well-known/apple-app-site-association.
• Android: inspect /.well-known/assetlinks.json.
• Serve both files over HTTPS without authentication or a redirect.

Open the destination on iOS.

Add applinks:links.example.com to Associated Domains in Xcode. Handle the incoming browsing activity or SwiftUI onOpenURL, then resolve the URL and navigate using a validated app path.

let runway = LinkRunway(
  endpoint: URL(string: "https://links.example.com")!,
  publishableKey: "lr_pk_your_publishable_key"
)
// Only after your consent flow grants collection.
await runway.setConsent(true)
if let destination = try await runway.open(incomingURL) {
  // Allowlist destination.path, then navigate in your app.
}

Verify the link on Android.

Add an autoVerify intent filter for the HTTPS host. Use the SHA-256 certificate of the distributed app, then resolve incoming intents from a coroutine.

<intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="https" android:host="links.example.com" />
</intent-filter>

Test the journey after installation.

Use the Android SDK’s install helper for Play Install Referrer after consent. For explicit referral recovery, create a code before installation and claim it in the app with a stable UUID. iOS matching is not automatic.

• Installed app: confirm the intended screen opens.
• Uninstalled app: confirm the store or web fallback works.
• Consent denied: confirm no attribution token is persisted.
• Repeat open or claim: confirm retries do not create another install or claim.

Find the missing connection.