API Documentation
Support

Mobile deep linking

Mobile deep linking lets a Rebrandly short link open a specific screen or piece of content inside a native iOS or Android app, instead of (or in addition to) redirecting to a web page.

How it works

A Rebrandly link always has a default destination URL. When mobile deep linking is configured, the link carries additional routing instructions that determine where to send the visitor based on their device and app state:

  • If the device is iOS and the app is installed, the link opens the configured in-app location.
  • If the device is Android and the app is installed, the link opens the configured in-app location.
  • If the app is not installed, you choose one of three fallback behaviors (see Fallback options below).
  • If the device is neither iOS nor Android, the link falls back to the default destination URL.

This ensures the link always resolves to a valid destination regardless of device or app state.

Fallback options

When a visitor is on the target OS but does not have the app installed, you can configure one of the following:

  • App Store / Google Play Store only. The visitor is redirected to the relevant store to install the app.
  • Landing page. A page with information about the app, a link to the relevant store, and a link to the fallback URL you provide. Requires a fallback URL.
  • Mobile page only. A simple redirect to a web page you provide. Requires a fallback URL.

Requirements

  • A Rebrandly account with the Deep links feature enabled. This is a paid feature — see the pricing page for plan availability.
  • A mobile app with a public listing on the App Store (iOS) or Google Play Store (Android).
  • Workspace-level app configuration in the Rebrandly dashboard before deep link rules can be created on links — via the dashboard or the API.

Limitations

  • Mobile deep linking is not supported on links created via the high-volume API. See High-volume API link limitations.
  • One deep link rule per platform (iOS or Android) per link.