In the General tab of App Settings page of the Branch Dashboard, you can change your advanced link settings.
URI scheme Deep Link mode
This selector allows you to control how and when Branch uses URI schemes to open your app when Universal Links and Android App Links fail. See browser specifics in the docs here.
Deep Link Mode | Description |
|---|---|
Conservative | Conservative mode will never use URI schemes if there is a risk of error messages. |
Intelligent | Intelligent mode is recommended and uses Branch data to safely use URI schemes everywhere, with the slight risk of error messages in certain browsers if the app is uninstalled. |
Aggressive | Aggressive will force URI schemes everywhere, causing users without the app to see error messages in some browsers. |
Redirect allowlist
With Branch, you have the ability to set a specific allowlist of domains that you can allow your Branch Links to redirect to (set to disabled by default). With the Redirect Allowlist, you can limit Branch Link redirection to specific web domains or URI schemes across your Branch platform. List each of the domains you want to limit redirection to. We also support a “*” for wildcard subdomains.
For example, if your allowlist includes branch.io, *.branch.io, and myapp://, your deep links can only redirect to domains like branch.io, dashboard.branch.io, or myapp://.
It is recommended that you include the app store domains that are relevant to the way users download your app. For example: play.google.com and apps.apple.com .
Match type
Setting Match Type determines the matching methodology Branch uses for your Links and App. Selecting Unique means that Branch will only make a deep link through install match if there is a single, unique outstanding footprint. For example, if you and your twin both have iPhone 5s with the same OS/version, etc, and click different links for the same app, then open the app up at the same time, we won’t deep link when Unique is selected. You probably don’t want this as it’s mostly for very special circumstances.
Local currency
Set the local currency of your Branch Dashboard if it is not USD. By setting your local currency, you can analyze marketing spend (cost) and revenue in your local currency. This also allows direct cost data comparison with ad partners who report their spending in a currency other than USD.
A field called Local Currency will be available on the Dashboard showing the currency configured in your Ads Analytics and Unified Analytics.
Note: The currency can only be set once through the Branch Dashboard to avoid some potential issues:
Historical data does not switch to the new local currency but would be labeled as such. As a result, the data prior to the currency change may show as inaccurate.
When changing the currency type, your cost data for the previous 7 days will be updated and may cause inaccuracies.
Other settings
Setting | Default | Description |
|---|---|---|
Use UTM tags for analytics (for Long Links) | Disabled | If you enable this, Branch will automatically set channel, feature, campaign, tags, and keywords based on UTM parameters. This only applies to Long Links, not links generated through the Dashboard, API, or SDKs. |
Analytics mapping with UTM | Enabled | When redirecting to a web URL, Branch automatically passes through any values from the following Branch link analytics tags as UTM parameters [~campaign -> utm_campaign, ~channel -> utm_source, ~feature -> utm_medium]. If these UTM parameters are already detected on the URLs being redirected to, Branch will not overwrite them. |
Enable Link Scraping | Disabled | Please note that this setting does not apply to Branch Links made using the Dashboard or API-generated links. |
Enable retrieving Last Attributed Touch Data via SDKs | Disabled | Allow retrieving last attributed touch data from the client. |
Enable China Features | Disabled | China Features include the ability to collect IMEI on non-Google Android devices. |
Best practices
For changing the Link Domain for both of your LIVE and TEST Branch apps, the best practice is to change your LIVE app first and then add test somewhere in the new domain name for the TEST app.
Notice, the LIVE and TEST apps cannot use the same customized Link Domain. For example, the LIVE app of Branch Monster Factory uses branchster.app.link for its LIVE app and branchster.test-app.link for its TEST app.