What deferred deep linking is
Deferred deep linking is a mobile-linking method that takes a user to a specific screen inside an app even when the app is not yet installed. If the app is already installed, the link opens it directly to that screen. If it is not installed, the link saves the intended destination, sends the user to the App Store or Google Play, and routes them to that destination the first time they open the app.
The deferred part means the deep-link action is postponed until after installation. A standard deep link assumes the app is already there. A deferred deep link survives the install step, which is exactly what a referral or affiliate flow needs, because the person clicking usually does not have the app yet.
Deferred vs other link types
The difference that matters for attribution is whether context survives the install.
| Link type | Works without the app | Carries context through install |
|---|---|---|
| Custom scheme (myapp://) | No | No |
| Universal Link (iOS) / App Link (Android) | Opens if installed, else needs a fallback | No |
| Deferred deep link | Yes | Yes |
| Contextual deep link | Yes | Yes, plus personalized parameters |
How it works, step by step
A linking service and an in-app SDK cooperate across the install boundary.
- A user taps a deferred link in an ad, email, SMS, QR code, or affiliate share.
- The linking service checks whether the app is installed.
- If installed, the app opens straight to the destination, the same as a standard deep link.
- If not installed, the service stores the destination and any context, such as the campaign or affiliate id, then redirects to the App Store or Google Play.
- The user installs and opens the app for the first time.
- On first open, the app retrieves the stored destination and context and routes the user to the exact screen, with attribution intact.
A concrete example
A creator shares a link to a specific product. A new follower taps it, does not have the app, and lands in the App Store. They install, open the app, and arrive directly on that product page rather than a generic home screen. Because the affiliate identifier was preserved across the install, the eventual purchase is credited to the creator who drove it. Without deferred linking, that new user would open to a blank home screen and the referral would be lost.
Why it matters for attribution
Most acquisition happens before the app exists on the device. If the link cannot carry who referred the user through the install, the install and any purchase that follows are unattributed. Deferred deep linking is what lets an install-based referral or affiliate program credit the right source, and it improves the new-user experience by dropping people exactly where they intended to go.
iOS specifics: Universal Links, ATT, and no fingerprinting
On iOS, deferred deep linking builds on Universal Links, Apple's standard for opening app content from a web URL. Universal Links require an apple-app-site-association file hosted over HTTPS on the linked domain, plus the matching app configuration.
Since iOS 14.5 and App Tracking Transparency, probabilistic device fingerprinting is not a permitted way to attribute an install. A deferred link that carries a deterministic token in its payload is the privacy-safe alternative: the app reads the token on first open and pairs it with the purchase, with no fingerprinting involved.
Android specifics
On Android, deferred deep linking builds on App Links, which require an assetlinks.json file on the domain, HTTPS, and Digital Asset Links verification. The mechanism is the same: store context before install, restore it on first open.
Your implementation options
You can use a managed linking SDK, such as Branch, AppsFlyer, Adjust, or Kochava, or build the components yourself. A build-your-own setup needs a backend to store link parameters, a redirect and install-state service, client-side logic to fetch the parameters on first launch, and in-app routing. Google's Firebase Dynamic Links was shut down in 2025, which pushed many teams to migrate to one of these paths.
How Attribloom uses deferred deep linking
Attribloom issues each affiliate a deferred deep link that carries a per-affiliate appAccountToken. A new user installs through the App Store, and on first open the app reads the token. Purchases are then captured through StoreKit 2 and App Store Server Notifications, which credit the conversion to that affiliate and reverse it automatically on refund.
Because attribution rides the deterministic token rather than fingerprinting, it is compliant with App Tracking Transparency on iOS. The same idea applies on the web through Shopify order and checkout webhooks, so one model spans app installs and web sales.