Deep Linked Email allows you to automatically convert your email links into multi-platform deep links that take users directly to content in the app on mobile devices, while still maintaining the same web experience for desktop and mobile users without the app.
With a script provided by Branch, you can dynamically create Branch links in email. In any place the script is called, the web URL is converted into its corresponding Branch link. The email is then sent.
When a link is clicked by a user without the app, it will route that user to the original web URL (including on desktop). When a link is clicked by a user with your app, it will direct that user into the relevant in-app content regardless of platform or email client.
- This guide requires you to have already integrated the Branch SDK into your app.
Contact your Branch Account Manager or email@example.com at any time for assistance with the setup steps.
Choose your email service provider¶
Navigate to the Deep Linked Email section of the Branch dashboard. Select your email service provider and click Get Started.
Set up deep linking for email¶
Email link behavior¶
Branch turns the web URLs you put into your emails into Branch deep links, opening the app for users with your app installed to that same content in the app.
To do this, it must be possible to map your web URL content (e.g. a page with brown loafers at
https://shop.com/shoes/brown-loafers) into a working deep link that takes users to brown loafers in the app. The Deep Linked Email setup flow will attempt to automatically detect this mapping for you.
If you do not want to set this up yet, you can select No, just open to app homepage for now.
By default, email deep links will redirect users without your app to the same content on the web instead.
If you would like to send users to the App Store or another default you have specified in Link Settings, you can select Open to default redirects.
Checking your deep linking setup¶
If you chose not to set up deep linking to specific content within your app, then you can skip this step.
In this step, you will want to enter a web URL that corresponds to a specific screen within your app. In other words, the webpage should have content that also exists in your app. If you do not know whether your web content also exists in-app, try any URL other than your website homepage. Some examples:
- A product page, like a page with brown loafers
- An article
- A content page, like a video or image
Once you choose one and click Submit, meta tags that can be used for deep linking will be retrieved from your webpage. You will see a result indicating the mapping between your web content and your app content. For a full explanation of the tests run on this page and the possible results, check out the support section.
We couldn't determine your deep linking setup¶
If an app deep linking scheme that maps to your web content cannot be successfully detected, you can configure your settings manually, or you can reach out to your Branch account manager or support for assistance.
We will help you set up one of the following methods:
If you use unique key/value data as deep link values:
- Recommended: Hosted deep link data: You can host your deep link data on your website with a metatag that looks like this
<meta name="branch:deeplink:my_key" content="my_value" />where
my_valuewill become a key value pair in deep link data. For each web URL, Branch will look for those tags and embed the deep link data (if found) into the deep link. Note that Branch also accepts App Links tags for deep linking. For more details, please read Hosted Deep Link Data.
- As query parameters: Simply append query parameters on to your web url and Branch will take those parameters and put them in deep link data.
If you use your web URL as a deep link value:
- URL path: If you use the path of your web URL as your
$deeplink_pathvalue, or any other deep link value, then the configuration will automatically take the path of the URL and put it in deep link data.
- Full URL: If you use the full web URL as your
$deeplink_pathvalue, or any other deep link value, then the configuration will take the entire URL and put it in deep link data.
Host deep link data for more than just emails
In the meantime, you can proceed to the next step: Configure ESP.
Deep linking settings for email¶
The following are all the possible settings you can configure for deep linking with email.
|Setting||Example||Link Data Result|
|Open the app homepage||No settings configured to generate deep link data for email; email links will route to the app homepage.|
|Open to specific app content||Deep link to specific app content based on one or more of the following settings.|
|Translate query parameters on URLs into Branch link data||URL:
|Translate web URL into Branch link data:
Full URL for key ______
|Translate web URL into Branch link data:
URL path for key ______
|Retrieve hosted deep link data from website and translate into Branch link data||URL:
|Strip protocol (http:// or https://):
Note: Typically used with one of the other settings.
Other Settings: Translate web URL into Branch link data: Full URL for key
|Translate query parameters on URLs into Branch link data from parameter ______ to key ______
Note: Not configurable in the UI. Contact support to use this setting.
Link behavior for users without your app¶
|Open to specific web content||Route to the original URL specified in the email.|
|Open to default redirects||Route to defaults specified in Link Settings.|
Completing your integration requires some setup that is specific to your email service provider. Please follow the documentation for your provider:
- Amazon SES
- Braze (formerly Appboy)
- Campaign Monitor