Contents
Deep links take users not just into your app, but straight to the right place within it – the product, booking or message they just tapped on. Without deep links, users land on the home screen or in the browser and have to look for the content again, which many will not do. This article explains the different link types, the technical setup on iOS and Android and how to design web-to-app journeys that actually work.
What deep links are and why they affect revenue
A deep link is a link that opens a specific piece of content in an app. Typical sources are e-mails, newsletters, push notifications, text messages, QR codes, social media posts, ads and your own website. Every break along the way costs users: anyone who taps “View order” and then has to find the app, log in and navigate through menus is more likely to give up.
Deep links therefore improve several metrics at once: campaign conversion, reactivation of inactive users, referrals and the measurability of marketing channels. They are a core element of any app marketing strategy.
Link types at a glance
| Link type | How it works | Advantage | Limitation |
|---|---|---|---|
| Custom URL scheme | Your own scheme such as myapp://product/123 | Easy to implement | Fails without the app installed; not uniquely tied to one app |
| Universal Links (iOS) | Regular HTTPS links on your domain open the app if installed | Secure, with web fallback | Requires a verification file on the domain |
| Android App Links | Verified HTTPS links open the app directly | No chooser dialog, with web fallback | Requires a verification file and correct configuration |
| Deferred deep links | The destination is preserved even if the app has to be installed first | Seamless start for new users | Needs a service or custom logic; privacy-sensitive |
For new projects, Universal Links and Android App Links are the standard. Custom URL schemes are at most a supplement, for instance for internal purposes.
Technical setup: domain, app and fallback
Universal Links and App Links rely on mutual confirmation: the app declares which domains it wants to open, and the domain confirms which app is authorised to do so.
- Publish verification files:
apple-app-site-associationfor iOS andassetlinks.jsonfor Android, both in the/.well-known/directory of your domain, served over HTTPS without redirects. - Configure the app: Associated Domains on iOS, intent filters with automatic verification for the relevant paths on Android.
- Routing in the app: the app must parse incoming URLs and route to the right screen – even if the user is not logged in. In that case, redirect to the original destination after login.
- Web fallback: every link should show meaningful content in the browser, so users without the app do not end up on an error page.
- Align the path structure: ideally, web and app content correspond, so that
/products/123shows the same product on the web and in the app.
One important note: Firebase Dynamic Links, long a popular solution for cross-platform links, has been discontinued by Google. If older apps still rely on it, they should have been migrated to Universal Links and App Links or an alternative service.
Deferred deep links and attribution
The biggest gap affects new users: they tap a link, land in the store, install the app – and then see the home screen instead of the promoted offer. Deferred deep links close that gap by remembering the destination across the install.
There are two approaches:
- Attribution and linking services: providers such as Branch, AppsFlyer or Adjust offer deferred deep linking together with campaign measurement. Review privacy, data processing agreements and server location carefully.
- Your own data-minimal solution: on Android, the install referrer from the Play Store installation can be evaluated. Alternatively, a code – such as an invitation or voucher code – can be entered after install or taken from the clipboard after explicit confirmation.
Methods that recognise devices via technical characteristics (fingerprinting) are problematic under data protection law and hardly compatible with Apple’s App Tracking Transparency rules on iOS. Clarify upfront which data you process for what purpose and whether consent is required. This is not legal advice.
Web-to-app: guiding website visitors into the app
For many companies, the website is the most important gateway to the app. Good transitions are helpful but not pushy:
- Smart App Banner on iOS: a meta tag in the HTML displays a subtle banner in Safari that opens the app or leads to the download.
- Your own banners: small, dismissible hints at the edge of the page or after a completed action. Avoid full-screen overlays that hide the content – they annoy users and, according to Google’s guidance on intrusive interstitials, can hurt search visibility.
- Contextual offers: “Track your order in the app” after a purchase is more convincing than a generic download prompt.
- QR codes: on packaging, posters or in store – with a Universal Link as the target so users with the app land in the right place directly.
Whether the app is the better revenue channel for your business model in the first place is discussed in app vs. website: which generates more revenue?
Testing: the cases that fail in practice
Deep links often work flawlessly during development and then fail in the real world. Test systematically:
- App installed and logged in, installed but logged out, not installed.
- An older app version that does not yet know a new path.
- Links from e-mail clients, messengers and the in-app browsers of social networks, some of which open links themselves instead of handing them to the system.
- Redirects through newsletter tools’ tracking domains, which can break Universal Links.
- Links from push notifications with the app closed and open; see our article on push notifications.
- Invalid or deleted content, handled with a friendly notice page instead of a crash.
Conclusion
Deep links are small technology with a big impact: they shorten the path from link to content and make campaigns, notifications and website visits more effective. Rely on Universal Links and Android App Links with a clean web fallback, design deferred deep links with data minimisation in mind and test the edge cases thoroughly. For new apps, we build the linking concept into our fixed-price offer from the start.
Frequently Asked Questions
What is the difference between a deep link and a Universal Link?
Deep link is the umbrella term for any link that opens specific content in an app. Universal Links are Apple’s implementation using regular HTTPS links that open the app if installed and the website otherwise.
Why does my Universal Link open the website instead of the app?
Common causes are a faulty or unreachable verification file, redirects through third-party tracking domains or in-app browsers that open the link themselves. An incorrect Associated Domains configuration in the app is another possibility.
Do I need an external service for deep links?
Not for simple deep links – Universal Links and App Links can be implemented with your own domain. External services are mainly worthwhile for deferred deep links and campaign measurement across many channels.
Can deferred deep links be GDPR-compliant?
Yes, if the solution is data-minimal, for example using the Play install referrer or a confirmed code. Methods that recognise devices by technical characteristics should be reviewed legally with particular care.