App Routing and Deep Links

How app-first deep links and fallbacks work

Let supported mobile traffic try the intended app while keeping the final web destination ready for everyone else.

Updated Jul 26, 20266 min read

The app-first flow

  • LinkStack starts with the final routed destination after country, affiliate, campaign, path, query, and fragment handling.
  • For a recognized provider and supported mobile device, LinkStack builds the managed app handoff from that destination.
  • A custom app destination can override automatic detection when you use a verified deep-link format.
  • Desktop visitors continue to the normal web destination.

When the app does not open

The visitor continues to the web destination when the app is unavailable, the URL shape is not supported, app routing is off, the device is disabled, or the operating system or social browser blocks the handoff.

Fallback choices

  • External browser fallback helps traffic leave a social in-app browser and continue in Safari or Chrome.
  • In-app browser fallback keeps the visitor inside Instagram, Facebook, or TikTok.
  • Fallback defaults can come from account settings or be overridden by device on a Smart Link.
  • Instagram and TikTok each have a separate switch controlling whether their in-app traffic may try the app-first path.

Configure app routing

  1. 1Open the Smart Link and choose Routing.
  2. 2Confirm the final web destination works first.
  3. 3Open App routing and use automatic detection when the provider is recognized.
  4. 4Enable the mobile devices you need.
  5. 5Review the app-not-installed fallback for iPhone, iPad, and Android.
  6. 6Save, then test the public Smart Link on real devices.

Related articles

Still need help?

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

Contact support
How app-first deep links and fallbacks work | LinkStack Help | LinkStack.fyi