Skip to content
← All features

Deferred deep linking

The link survives the install.

When someone taps a link without your app installed, they go to the store, install, and still land on the exact screen the link pointed to. No dead ends, and no IP or device fingerprinting to make it happen.

sftl.in/app/product-123
1Tap, no app installed
2Install from the storetoken minted
Opens product/123Right screen
No fingerprinting

Deep linking, extended past the install

Standard deep linking opens your app when it is already installed. Deferred deep linking covers the harder case: the app is not installed yet. SwiftURL mints a one-time token at the moment of tap, hands it to the store install, and your app redeems it on first launch to recover the exact destination and in-app path. The token is opaque, single-use, and short-lived, so an edit or delete between tap and install can never move where the user lands.

A one-time, opaque token carries the destination through the store install

Android reads the Play Install Referrer; iOS reads a user-initiated clipboard token

No IP matching and no device signals, the token itself is the only credential

How it works

1

Tap without the app

The Deep View preview offers to get the app, and mints a one-time token.

2

Install from the store

The token rides along via the Install Referrer on Android or the clipboard on iOS.

3

Redeem on first launch

Your app posts the token to /track/open and gets back the destination and path.

4

Land on the right screen

The user opens exactly where the link pointed, first session included.

Privacy-first by design

Most incumbents recover the deferred link on iOS by matching people probabilistically on their IP address, which is personal data under DPDP and GDPR and exactly the fingerprinting we refuse to do. SwiftURL uses a user-initiated clipboard token on iOS and the official Play Install Referrer on Android instead. The token stores only a snapshot of the target, never a person, and it is purged after a short expiry.

Why it matters

First session counts

New installs land on the promoted content, not a generic home screen.

Cleaner attribution

A deterministic token beats guessing which install came from which tap.

Compliant by default

No IP correlation means one less privacy liability for your app.

Frequently asked questions

What is deferred deep linking?
It preserves the exact link target across an app install, so a user who taps a link without your app installed still lands on the right screen after installing.
How is the target carried through the install?
A one-time, opaque token is minted at tap and recovered on first launch, on Android via the Play Install Referrer and on iOS via a user-initiated clipboard token.
Do you use IP or device fingerprinting?
No. SwiftURL never matches by IP, screen, or device signals. The token itself is the only credential, which keeps it aligned with DPDP and GDPR.
Does it need app-side work?
Yes. Your app redeems the token by posting it to the track/open endpoint on first launch. It is only a few lines of integration.
How long is the token valid?
The token is single-use and short-lived, expiring by default after one hour, and it stores only a snapshot of the target, never personal data.

Never lose the link to an install.

Turn on Deep View and deferred deep linking per domain, and wire the token in with a few lines in your app.

Start free Standard deep linking