Skip to content

Answers use only the pages of this documentation, and every answer links to the pages it came from. Your question is sent to our answering service to be answered, and kept so the people who write these pages can see what readers ask.

🔗 Deep Linking

Open a specific screen straight from a link, and choose the fallback.

A deep link opens one particular screen inside your app, rather than the home screen. Send someone a link to an order, an event or a profile, and if they have the app installed it opens there.

The panel holds one section: Redirection and Fallback.

The addresses themselves are not set here. Every screen already has one, and you can see it in Screens — open a screen and look at its Deep Linking section, which shows the route it answers on.

Screens that are not routes, such as an auth gate rendered by the app layout, have no address and say so.

Where to redirect users when the app is not installed?

A deep link is only useful to someone who has the app. This setting decides what happens for everyone else.

Two options:

  • Redirect to PWA — send them to the web version of your app. It is the same app, so the link usually still lands somewhere sensible.
  • Custom Redirect — send them somewhere you choose.

Choosing Custom Redirect reveals two fields:

  • Fallback URL iOS
  • Fallback URL Android

Both take a full URL, for example https://example.com. They are separate because the two stores are separate — most apps point each one at their listing on the matching store.

Save is disabled until something has actually changed and the form is valid.

Note

Deep linking is not available on older apps built before the current layout engine. Those apps see an explanation in place of this form rather than controls that would not work.