Quick answer
A deep link is a link that opens a specific screen inside a mobile app, such as a product page or an order, instead of only launching the app's home screen. It makes the destination of an ad, email or push message match what it promised.
What is a deep link?
A deep link is a link that opens a specific place inside an app, such as a product page, an order or a settings screen, instead of just launching the app's home screen. The same idea exists on the web, where any URL to an inner page is a "deep" link compared with the home page. In mobile work, the term almost always means app deep links, and it covers several different technical mechanisms that behave differently.
The reason it matters is the landing. An ad, an email or a push message promises something specific. If the tap drops the user on a generic home screen, the user has to find the thing again, and many do not. A deep link makes the destination match the promise.
Types of links: what each one does
| Type | Looks like | If the app is installed | If it is not | Main weakness |
|---|---|---|---|---|
| Ordinary web link | https://shop.example/p/42 | Opens in the browser | Opens in the browser | Never opens the app by itself |
| Custom URI scheme | shopapp://p/42 | Opens the app at that screen | Fails or shows an error | Not tied to a domain, so any app can register the same scheme |
| iOS Universal Link | https://shop.example/p/42 | Opens the app at that screen | Opens the web page in Safari | Needs an association file on your site and an entitlement in the app |
| Android App Link | https://shop.example/p/42 | Opens the app directly, no chooser | Opens the web page | Needs domain verification; Android 6 or later |
| Android deep link (unverified) | scheme or https | Opens the app, but the system may show a chooser if several apps match | Opens the browser or fails | The disambiguation dialog |
Android's own documentation draws the line clearly: plain deep links are subject to the system disambiguation dialog, while verified App Links open straight into your app without asking. Apple's Universal Links work on the same principle with a website-to-app association. The practical rule: for links to your own website, prefer the verified HTTPS kind, because it degrades gracefully to a web page when the app is missing.
Deferred deep links
A normal deep link assumes the app is already installed. When it is not, the user goes to the store, installs, opens the app, and the original destination is lost. A deferred deep link remembers the destination across the install and, on first launch, takes the user to it. Platforms do not do this for you; it needs code or a link-management service that stores the intended destination and hands it to the app after installation.
Three cases cover most real traffic:
- App installed: the link opens the app at the screen.
- App not installed, link is plain: the user installs and lands on the home screen. The destination is lost.
- App not installed, link is deferred: the user installs and lands on the screen.
A worked example: one campaign link, three paths
Sample data: a campaign sends 1,000 taps from people who already have the app, and 500 taps from people who do not.
Installed users, 1,000 taps.
| Step | Link to home screen | Deep link to product |
|---|---|---|
| Reached the product screen | 300 (30.0%: users searched for it themselves) | 940 (94.0%; 60 taps fell back to a web page) |
| Purchased | 60 (6.0% of taps) | 132 (14.0% of arrivals, 13.2% of taps) |
The deep link produces 132 purchases against 60, a 2.2 times difference, mostly because 94% of users reach the right screen instead of 30%.
Users without the app, 500 taps. Of the 500, all go to the store; 150 install (30.0%); 120 open the app (80.0% of installs); with a deferred deep link, 110 of those 120 land on the product screen (91.7%), which is 22.0% of the original taps. With a plain link, the 120 land on the home screen and only the ones who search for the product reach it, for example 30.0% of 120, which is 36.
The point of the numbers: deep linking changes the last step of the path, not the first. It does not create demand; it stops losing the demand you already paid for.
Common mistakes
- Using a custom scheme for web-reachable content. If the app is missing, the link just fails. Use an HTTPS link that falls back to a web page.
- Not testing the "app not installed" case. Most testing happens on a phone that has the app. Test with the app removed.
- Linking to the home screen and calling it a deep link. If the destination screen is the home screen, you have an app link, not a deep link in the useful sense.
- Forgetting the web fallback. A deep link that opens nothing on a desktop is a dead end. Give every link a web destination.
- Losing the source on the way in. If the tracking parameters (campaign, source, click ID) are dropped at the redirect, you cannot say which campaign produced the purchase. Check that UTM values survive into the app.
- Counting the tap as the result. A deep-link launch only means the app opened; success is the action that follows.
How deep links are attributed
A deep link is a route; attribution is the record of where a user came from. The two work together: the link carries a campaign and a click ID, the app reads them on opening, and an attribution provider (see mobile measurement partner) matches the click to the install or the open and reports which campaign deserves credit.
Measuring deep links in TapCub
TapCub does not create or host deep links, and it does not match ad clicks to installs, so it is not an attribution provider. It measures what happens after the link opens and can receive the results of the provider you use. Using the example above:
- Count launches. TapCub's preset app events include
$deeplink_launch(a deep link opened the app). Whether your SDK sends it automatically depends on the platform; check the SDK page, and if not, send it yourself under that name. - Follow the route. In All-platform analytics › Behavior › Behavior analysis, build a funnel from
$deeplink_launchto your product-view event to your purchase event. That gives the "reached the product screen" and "purchased" rows of the table. - Split by channel. If you write
$channelon events, App analytics › Users › Channels shows new users per day, next-day retention and active share by channel. - Bring in the provider's attribution. In App analytics › Configuration › Business settings you get a receiving address for your provider's postbacks. They are written as
$app_installevents, and App analytics › Quality & attribution › Attribution reads the media source, campaign and match type, and splits installs into organic, promoted and unattributed. - Check cost. The same install events feed All-platform analytics › Business › Channel ROI, where you can import spend by day and channel and see cost per click and per acquisition.
For a plain-language view of apps, see native app.
See also: Deferred Deep Linking: How It Works and How to Track It.
Sources
- Android Developers, Handling Android App Links.
- Apple Developer Documentation, Allowing apps and websites to link to your content.
- Unity, The what, how, and why of deep linking.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.