With Mobile Deep Linking you can easily set-up your Custom Domain to support the industry standard deep linking methods of Apple's Universal Links and Google's Android App Links. Bitly also supports domain-level overrides as well as the legacy method of deep linking known as Custom Schemes.
- Universal Links & Android App Links - Enable all links on a Custom Domain to deep link into your app. This set and forget feature ensures you're providing the best mobile customer experience for all your links.
- Domain-level Overrides - Setting an alternate mobile path (a.k.a. mobile URI), Alternate Install Preference, or Alternate Install URL on any link already configured for Universal Links and/or Android App Links.
- Legacy Custom Schemes - Enable an individual link to be a deep link by associating it directly with your app.
- NOTE: Apple has deprecated this method with iOS 9+ by requiring the user to jump through additional steps before reaching your app.
Creating Universal Links & Android App Links
1. Configure your mobile apps through the Account Management section of Bitly Enterprise.
- NOTE: The Apple App ID and Android SHA-256 Key are required to associate the app(s) to your custom domain.
2. Associate your custom domain with one or more mobile apps. By doing so you are creating a site association file that enables support for the industry standard deep linking methods of Apple's Universal Links and Google's Android App Links.
3. Install the Bitly SDK into your iOS and/or Android apps.
- NOTE: The SDK is used to provide the original destination URL to the app in order to route the user to the expected content.
- NOTE: The SDK also enables you to measure App Opens and App Installs as well as support link deep link creation directly through your app.
4. Create a link on the custom domain you have enabled for Universal Links and/or Android App Links.
- NOTE: All links created on a custom domain before and after it is associated with an app will be deep linking enabled.
Creating Domain-level Overrides
1. Ensure you have successfully set up Universal Links and/or Android for your custom domain.
2. Create a link or edit an existing link.
3. Under Mobile Behavior you will see the Android and iOS apps already associated with the custom domain. Choose the Edit button for the app settings you would like to override.
- NOTE: Override settings can be set independently for iOS and Android apps.
- NOTE: Overrides inherit the app already associated with the custom domain. The override cannot be associated with a different app.
4. Enter the mobile path, Alternate Install Preference, and Alternate Install URL.
- Mobile Path: The deep link URI (also known as Custom Scheme) which provides the route to the content to be loaded in the app. This route, similar to web URLs, will have a unique structure based on how the app was built.
- NOTE: If you do not know the mobile path contact your mobile development team.
- Alternate Install Preference: The mobile experience shown to a user when the app is not already installed on the mobile device. This can be uniquely set for iOS and Android.
- OFF - User will be automatically taken to the content in mobile web.
- INTERSTITIAL - User will be taken to an interstitial on mobile web where they can choose to go to the Install URL to download the app or be taken to the content in mobile web.
- APP STORE - User will be automatically taken to the Install URL to download the app.
- Alternate Install URL: The URL that will be used when Interstitial or App Store is selected as the Install Preference.
- NOTE: The default settings for the Alternate Install Preference and Alternate Install URL are inherited from the configured app but can be updated for individual links.
Creating Custom Scheme Deep Links
1. The first step is to configure your mobile apps through the Account Management section of Bitly Enterprise
- NOTE: Your mobile app must contain an App Scheme.
2. Create a link or edit an existing link.
3. Click the Add Mobile Behavior link, select either iOS or Android operating system for your app, and then select the desired app:
4. Enter the mobile path, install preference, and install URL.
- Mobile Path: The deep link URI (also known as Custom Scheme) which provides the route to the content to be loaded in the app. This route, similar to web URLs, will have a unique structure based on how the app was built.
- NOTE: If you do not know the mobile path contact your mobile development team.
- Install Preference: The mobile experience shown to a user when the app is not already installed on the mobile device. This can be uniquely set for iOS and Android.
- OFF - User will be automatically taken to the content in mobile web.
- INTERSTITIAL - User will be taken to an interstitial on mobile web where they can choose to go to the Install URL to download the app or be taken to the content in mobile web.
- APP STORE - User will be automatically taken to the Install URL to download the app.
- Install URL: The URL that will be used when Interstitial or App Store is selected as the Install Preference.
- NOTE: The default settings for the Install Preference and Install URL are inherited from the configured app but can be updated for individual links.
