Types of deep links: standard, deferred and contextual, with examples

Someone taps your link on their phone. Where they land decides whether you make the sale. Open the product inside the Amazon or Instagram app, where they’re already logged in with a saved card, and checkout is two taps away. Drop them on a logged-out mobile web page, or inside Instagram’s in-app browser, and most of them leave.

Deep links are how you control that landing. But the phrase covers a few different mechanisms, and the differences only matter to you on the day one of them stops working. Here’s each kind you’ll actually meet, what it does, and which one your campaign needs.

Three of the kinds below are about what a deep link does. The last two are about how it gets from a tap to the app.

A standard deep link points at a screen through the app’s own address scheme, something like yourshop://products/42. Tap it with the app installed and the right screen opens. For years that was the whole story.

The catch arrives when the app is missing. A raw scheme link has no fallback. The phone sees myapp://, finds nothing registered to open it, and shows an error or simply does nothing. Your visitor is stuck on a broken tap. That’s why a bare scheme link belongs on buttons inside your own app, and why sending one to a cold audience loses you the people who haven’t installed yet.

A deferred deep link fixes the missing-app problem. The person taps, has no app, gets sent to the Play Store or App Store, installs, opens the app for the first time, and still lands on the exact screen you meant: the product, the invite, the shared playlist. The destination waits, or defers, across the install.

This is the mechanism behind app-install ads and referral programs. It’s also the hardest to build, because the tap and the first app-open happen in two separate sessions with nothing shared between them. Matching the two needs either a native SDK inside your app or a fingerprint guess, and Apple’s privacy changes have made the fingerprint route shaky. Firebase Dynamic Links handed this out for free until Google shut it down in 2025, and the free replacement is what most teams moved to.

A contextual deep link is a standard or deferred link carrying extra baggage: who referred the user, the campaign they came from, a coupon to auto-apply, a group to drop them into. It isn’t a separate technology; the link just carries extra data. When a friend shares a food-delivery referral and you open the app to a pre-filled invite with the discount already in your cart, that data came in on a contextual deep link.

People fold these into the list above, so pull them apart. The first three are about behaviour: what the link opens. Universal Links on iOS and App Links on Android are about delivery. They carry a deep link over an ordinary https address, so one link opens the app when it’s installed and a web page when it isn’t, with no error screen and no scheme guessing.

Ship your deep links as Universal Links and App Links today. The old custom-scheme approach still works for in-app buttons, but for anything public it fails in the exact spots that cost you money, starting with Instagram’s in-app browser. The full breakdown is in Universal Links vs deep links and Android App Links vs deep links.

Match the kind to the job. Sending existing app users to a screen, from an ad, a push or a bio link, wants a standard deep link shipped as a Universal Link so non-users still land somewhere useful. Running an install campaign or a referral program wants a deferred deep link, so the person who installs because of you still reaches the screen that sold them. Passing a referrer, a coupon or a campaign tag layers contextual data on top of either.

Most Indian sellers and creators need the first, and now and then the second. Almost none of them need to hand-build the plumbing. Creating a deep link that opens the app and falls back cleanly takes a few minutes with a tool that handles the scheme, the store fallback and the Universal Link setup for you.

Every kind above shares one failure mode: the in-app browser. Tap a link inside Instagram or TikTok and the app opens it in its own stripped-down webview, where your deep link often never gets the chance to fire. Getting past that on both iOS and Android is what separates a link that opens your app from one that opens a dead end.

directinapp is built for exactly this. It routes the tap into the real app, falls back to the store or the web when it has to, and then reports which link actually drove the install or the sale, so you learn which placement is worth repeating.