App Routing and Deep Links

How to troubleshoot the wrong app or web fallback

Check the routed destination, provider detection, device settings, and fallback choice in the order they actually run.

Updated Jul 26, 20267 min read

The wrong app or content opens

  • Open the final web destination and confirm it points to the exact public content you expect.
  • Check country routing first; app routing uses the final routed destination.
  • Use automatic mode for a recognized provider unless you have a verified reason for a custom app URL.
  • Remove extra shorteners or redirects that hide the final provider URL.
  • If using custom mode, confirm the app URL format is valid for the intended app and device.

Only the web fallback opens

  • Confirm app routing and deep linking are enabled for the Smart Link.
  • Confirm the current device is enabled.
  • Check whether LinkStack recognizes the final provider and URL shape.
  • Confirm the destination app is installed and allowed to open links.
  • Check the Instagram or TikTok switch when testing inside those apps.
  • Desktop traffic is expected to use the web destination.

The fallback uses the wrong browser

  • Review the app-not-installed fallback for the current device.
  • Choose external browser when you want to leave a social in-app browser.
  • Choose in-app browser when you intentionally want to stay inside the social app.
  • Use the account default or save a device-specific override, then retest the public link.

Retest cleanly

  1. 1Save every routing section you changed.
  2. 2Open the public Smart Link in a new browser session.
  3. 3Test the installed-app and fallback cases separately.
  4. 4Record the device, browser, destination, and result before changing another setting.

Related articles

Still need help?

Tell us what you are trying to do and where you got stuck.

Contact support
How to troubleshoot the wrong app or web fallback | LinkStack Help | LinkStack.fyi