Branch gives you peace of mind that your links will work in every edgecase to route users to the best destination with the industry’s highest matching accuracy, by combining every deep linking standard into a single, simple package. Easy to implement, and always up to date.
- Direct deep linking users who have the app installed already to relevant content.
- Deferred deep linking users who do not have the app installed to relevant content immediately after the first install.
- Customized/branded URLs
- Store custom data parameters in link data
- User clicks a link.
- If user has the app installed: the app opens and routes to relevant content.
- If user doesn't have the app installed:
a. Route user to App/Play store to download the app and routes to relevent content on app open.
b. Route user to mobile web relevent content
Developers knowledgeable with APIs, Web, and Mobile Development are required.
Please visit our Developers Hub to implement the Branch SDK on both iOS and Android.
Depending on how your mobile app is routing to in-app content will determine how you will create and tag your Branch Links.
Branch Link creation options:
- Quick Link
- Ideal for one-off campaigns
- Deep Linking API
- Ideal if you are looking to programmatically generate Branch Links at scale
- Mobile SDKs
- Web SDK
- Chrome Extension
When configuring your Branch Link you must make sure you are adding the correct key/value pairs to the data dictionary to ensure they make it into the app when it opens from a Branch Link click.
Additional details on configuring your Branch Link can be found here.
Click the Branch Link on your mobile device and it should go through the flow outlined in How does it Work?.
For NativeLink™ Deferred Deep Linking, please follow our guide here.
A canonical URL is a Branch referred term that represents the corresponding web URL for the in-app content. If your app can already deep link using web URLs, it is recommended to use the $canonical_url key with the web URLs value for deep linked routing for the app. This reduces the level of effort as $canonical_url is often automatically applied as Branch Link data for products like Journeys and Email; therefore, there is not an additional need to add extra data to a link.
For example, a shopping brand that has both a website and a mobile app will have equivalent experiences for the user to get to related content and it can be identified with a canonical URL. A web URL might look something like this:
For a hotel/travel brand, a canonical URL might look something like this:
The different parts of the URL can be used for deep linking the user to in-app content.
When creating your Branch Link, you can add Open Graph tags to enhance its look and feel in a social graph. Adding these tags should make your Branch Link look better in channels like SMS or on social media posts. The following tags can be used in your Branch Link:
|Open Graph Key||Description|
|The title of your object as it should appear within the graph|
|A one to two sentence description of your object.|
|An image URL which should represent your object within the graph.|
This is automatically set when setting the Social Media Tags if you are creating a Branch Quick Link or scraped when setting
$original_urlis set in the Link Template, which will automatically add the
$canonical_urlwith the same value. However,
$canonical_urlis NOT directly scraped for setting the Social Media Tags.
Please following the following guide for testing troubleshooting your deep links:
Updated 6 months ago