BlogDeep links

Deep link fallback URLs: where a tap goes when the app isn't installed

· 8 min read · By the Strait team

Every deep link needs an answer for people without the app. How fallback URLs work on Android, iPhone and desktop, when to send people to the store or to your website, the "Item not found" trap for unpublished apps, and how to test each path.

A deep link is a promise: tap this and you'll land on that screen. For people who have your app, the operating system keeps the promise. For everyone else, the link has to decide what to do instead, and that decision is the fallback.

Fallbacks get less attention than they deserve. They are what a new user sees first, they are where a campaign's install rate is won or lost, and they are the part that changes most between platforms. This post explains how fallbacks work on Android, iPhone and desktop, the choices you have, and one trap that catches almost every team before launch.

When a tap reaches the link server (that is, the operating system didn't open your app directly), the server has to work out:

  1. What is this device? Android, iPhone, iPad, desktop, a link-preview bot, or a phone inside an in-app browser such as WhatsApp's or Instagram's.
  2. Can the app open from here? A verified App Link or Universal Link opens the app without the server ever seeing the tap. If the server does see it, the app either isn't installed or couldn't be opened from where the tap happened.
  3. Where should this person go if it can't? The store, so they install and then land on the screen (a deferred deep link), or a web page that shows the same content right now.

The fallback URL is the answer to the third question. Most services let you set one per platform. In Strait they are androidFallbackUrl, iosFallbackUrl and desktopUrl on each link (short links docs); in Firebase Dynamic Links they were afl, ifl and ofl.

On Android, a tap in a browser usually gets an intent URL back from the link server. An intent URL tells Chrome which app should open and at which link, and includes a browser_fallback_url for when that app isn't installed. Chrome tries the app first; if it isn't there, Chrome loads the fallback.

That makes the fallback a single choice per link: Google Play or your website.

  • Google Play is right when the goal is installs. If the Play URL carries a referrer parameter, Play passes it to your app after the install through the Play Install Referrer, which is how a deferred deep link reaches the first open on Android. Strait puts the link's id and the tap's id there, so the first open lands on the right screen and joins up with the tap in analytics.
  • Your website is right when the content is useful without the app (an article, a product page, an order status) or when the person is unlikely to install today.

You can see the intent URL for any link, with either fallback, in the free Android intent link builder.

The "Item not found" trap

Here is the trap. Before your app is public on Google Play (during closed testing, internal testing, or after it's been removed), its Play listing doesn't exist for ordinary users. A fallback to Play then lands on Google Play's "Item not found" page. We hit this ourselves on a real phone on 2 October 2026 with our test app: the tap, the intent and the fallback all worked, and the person ended up on a dead end anyway.

Nothing is broken in the link. The fix is to choose the fallback based on whether the listing is live. Strait has a workspace setting for this, When someone without the app taps a link, with three choices:

Setting What happens without the app
Automatic: Google Play if the app is published, otherwise the website The server checks whether your Play listing is public and picks Play or the website
Always Google Play Always Play. Use this while testing with Play internal testers, who can see the listing
Always the website Always the link's website fallback

How the automatic check works, from our engine's code: the server requests your app's public Play listing. A "not found" answer means the app isn't public, so taps go to the website, and that answer is re-checked after half an hour. A normal listing means Play, re-checked after six hours. Any error (a timeout, a block, Play being slow) counts as available, so a problem on Google's side never sends people away from the store by mistake.

There's one catch with internal testing: your testers can see the listing, but the automatic check sees what the public sees. So while you test deferred links through Play internal testing, set Always Google Play, as our production checklist says, and switch back after launch.

iPhone: no intent URL, so a page first

iOS has nothing like Android's intent URL with a built-in fallback. If a Universal Link didn't open the app, the link server can't ask Safari to "try the app, else go here". So the usual iPhone fallback is a short page:

  • Safari: Strait shows a page with a Get the app button that opens your App Store listing. The tap on that button is what our iPhone deferred match is built on, which is opt-in (off until you turn it on).
  • In-app browsers on iPhone: a browser we recognise, such as Instagram's or WhatsApp's, gets the in-app browser page described below. Other app web views can't run the Get the app page, so the tap goes directly to the App Store.
  • No App Store id configured: the tap goes to the link's iPhone fallback URL, or the destination, on the web.

The page costs one extra tap, which some teams dislike. The alternative, sending iPhone users directly to the App Store from Safari, makes it impossible for the first open after install to know which link was tapped without some other matching method.

Desktop: the web, always

A desktop computer can't install a phone app from a link, so desktop taps go to the web: the link's desktopUrl if set, otherwise the destination itself. This is also why the destination of a deep link should be a real web page whenever possible. If your deep link path doesn't exist on your website, a desktop user lands on a 404.

A practical rule: make the destination a page that works on the web, and let the app open the same path. Then every fallback has somewhere sensible to go.

In-app browsers: a fallback before the fallback

Taps inside Instagram, Facebook and similar apps often open in the app's built-in browser, which often can't launch other apps or the store reliably. Before the store-or-website choice even comes up, the link server needs to recognise that browser and offer a way out: an Open in app page with a one-tap hand-off on Android, and help opening the link in the real browser. We wrote about this in why Instagram and WhatsApp links open the browser.

A link-preview bot (WhatsApp, Slack, iMessage and others fetching a card for the chat) should never be redirected to a store or a website. Strait gives every bot a small page with the link's title, description and image, and doesn't count it as a tap. If your previews show the App Store's title instead of yours, the link server is redirecting bots. We cover previews in WhatsApp link preview not showing.

Choosing fallbacks: a short guide

Situation Android iPhone Desktop
Install campaign, app is public Google Play Get the app page → App Store Product page on your site
App in testing, not public yet Website (or Play only for testers) Website Website
Content that works on the web Website Website Website
Transactional link (order status, delivery tracking) Website Website Website

How to test every fallback

Fallbacks are the path you test least, because your own phone has the app installed. A minimum run:

  1. Uninstall the app on an Android phone and tap the link in Chrome. Check that you land on Play or the website, whichever you chose. Our Android deep link test plan shows how to script it.
  2. Tap the same link inside WhatsApp, on a phone without the app.
  3. On an iPhone without the app, tap the link in Safari and in one in-app browser.
  4. Open the link on a desktop browser.
  5. Paste the link into a chat and check the preview card.

The free Will it open? simulator shows the decision our engine makes for each of these cases, without a phone.

Sources and how we checked

  • Google, Android Intents with Chrome: intent URL syntax and S.browser_fallback_url.
  • Android Developers, Play Install Referrer: how the referrer reaches an app installed from Google Play.
  • Firebase, Dynamic Links deprecation FAQ: the shutdown that sent many teams looking for new fallback handling. Read on 5 October 2026.
  • Our engine's decision code and its unit tests: the per-platform fallbacks, the Play availability check (30-minute re-check when not found, six hours when found, errors count as available), the iPhone page and in-app browser behaviour, and previews for bots.
  • Our recorded real-phone run of 2 October 2026, in which a Play fallback for our then-unpublished test app landed on "Item not found".