The "App" level of a Branch account is the third level of access and includes access (either edit or read-only) to the following functionality.
If you are an Admin, you have edit access to the Profile tab.
- Branch Key - provided by Branch; resettable.
- Branch Secret - provided by Branch; resettable.
- App Name - provided by you; editable.
- App ID - assigned by Branch; not editable.
- Time Zone - Your time zone affects your dashboard analytics and how your Branch data matches up with external data sources. Use the drop-down to select the appropriate time zone.
Resetting your Branch Key/Secret
If you need to reset your Branch Key/Secret, click Reset Key or Reset Secret respectively. Doing so automatically generates a new Branch Key/Secret.
Any user type - Admin, Team Member, Full Read, Limited Read - has the ability to edit the User tab.
- Dashboard UID - assigned by Branch; not editable.
- First and Last Names - provided by you; editable.
- Email Address - provided by you; editable.
- Change Password - provided by you; editable.
If you are an Admin, you have edit access to the Team tab.
To add a new App Team User:
- Click the Add App Team Member button.
- In the Add App Team Member modal:
- Provide the user's Email Address
- Provide the user's First and Last names
- Select the appropriate Access Level
- Admin - Edit access to all settings and export access to all data.
- Team Member - Edit access to channels and links, read-only access to app settings, and access to aggregate data.
- Full Read - Read-only access to all settings and access to aggregate data.
- Limited Read - Access to aggregate data only.
- Custom - Customize settings and data access.
- No Access - no dashboard access.
- Click Invite.
Each access level - as defined above - comes with predefined permissions which you can edit if you choose.
If you want to modify a predefined access level, click the pencil icon to (de)select the available options.
- Link-level Settings - Settings or features that can impact functionality for single links.
- Channel-level Settings - Settings or features that can impact functionality across a marketing channel.
- App-level Settings - Settings or features that can impact functionality app-wide.
- Aggregate Data - Summary data that contains no granular data.
- Sensitive Data - Data that can contain user-identifying, payment-related, or secret information.
- Fraud Settings & Data - Settings or data associated with fraud detection and prevention.
To modify an existing App Team Member:
- Find the App Team member you want to modify and click the ... button in the Actions column for that user.
- To edit the App Team member:
- Click Edit and modify any of the following:
- First and Last names
- Access Level
- Click Save.
- Click Edit and modify any of the following:
- To resend the invitation to join the account:
- Click Resend Invite.
- To delete the App Team member:
- Click Delete.
- In the Are you sure you want to delete? modal, click Yes, Delete.
If you are an Admin, you have edit access to the General tab.
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.
- Conservative mode will never use URI schemes if there is a risk of error messages.
- 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 will force URI schemes everywhere, causing users without the app to see error messages in some browsers.
- Use these settings to control the default behavior of your deep links on iOS
- Enable Universal Links
- Starting with iOS 9, Apple offers Universal Linking functionality, which will open URLs directly into an app, rather than the usual Link -> Safari -> App handoff cycle. This requires some set up, but we do this for you, we just need your Apple App Prefix and your app's Bundle identifier.
- The Apple App Prefix is found within the Apple Developer Portal for your app.
- Use these settings to control the default behavior of your deep links on Android
- Play Store is for published apps, if your app cannot be located or is a local/dev build, please use the Custom URL option
- Enabling App Links
- Starting with Android 6.0 (API level 23) and higher allow an app to designate itself as the default handler of a given type of link. App Links will open URLs directly into an app, rather than the usual Link -> Browser -> App handoff cycle. This requires some set up, but we do this for you. We need your sha256_cert_fingerprints.
- Generate a SHA256 Cert Fingerprint
- Navigate to your keystore file (used to build the debug and production version of your APK file before it gets deployed)
keytool -list -v -keystore my-release-key.keystoreto generate a fingerprint
- Example fingerprint
AA:C9:D9:A5:E9:76:3E:51:1B:FB:35:00:06:9B:56:AC:FB:A6:28:CE:F3:D6:65:38:18:E3:9C:63:94:FB:D2:C1to add to your Branch Dashboard
- Use these settings to control the default behavior of your deep links on Fire
- Use these settings to control the default behavior of your deep links on any other platform.
We now support deep linking to Desktop apps such as Spotify and Slack, via URI schemes
Our beta Mac OS Desktop SDK is available for testing, so please contact your Branch Account Manager or [email protected] for more information.
Use these settings to control the default behavior of your deep links on Desktop browsers
For Desktop apps
- Enter your Desktop URI Scheme (e.g.
$desktop_deeplink_pathkey-value pair to your link (e.g.
- If the app is not installed when the link is clicked, we will fall back to
$desktop_urlor Default URL, in that order
- This feature is still in the early stages of development; so usage without a Desktop SDK will not be able to attribute or pass data through an install.
- Enter your Desktop URI Scheme (e.g.
- Use these settings to control the default behavior of your deep links on other devices.
- Match Type
Uniquemeans 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.
Use UTM tags for analytics (for dynamically-created links)
disabled. If you enable this, Branch will automatically set channel, feature, campaign, tags and $keywords based on UTM params. This only applies to dynamically created links, not links generated through the Dashboard, API or SDKs.
| UTM parameter | Branch parameter
| --- | --- |
utm_term| Keywords (not visible on Dashboard)
Enable Link Scraping
- If you enable this, Branch will automatically add data from your website's meta tags.
- Set the default image preview for your deep links when shared on social media
- These values are typically overridden by Custom link behavior which differentiate your deep links between one another
- Choose a link domain which will be used for all your links
- The link domain is the website which hosts your deep links
- The link domain is not a deep link
Changing Link Domains
Please view our in-depth article on [changing your link domains]/using-branch/docs/advanced-settings-configuration#section-change-link-domain), including how to use certain domains as well as troubleshooting.
If you choose to delete your app, this will be a permanent change. Note the following actions that we apply once you delete your Branch app.
- We delete the dashboard user data of the original app creator associated with that particular app. They can still log in to other apps.
- Your links will show a 404.
- All requests to our API (via the SDK), will return a server error.
- Attribution and analytics information will no longer be tracked.
- All data feed systems will stop sending data (such as webhooks and data integrations).
Default Attribution Window Settings
Each attribution window has its own default measured in days. Please refer to the image below for these defaults.
Deep Linking Duration refers to the duration of time someone is eligible to receive deep link data. This includes anyone clicking a Branch link, or being automatically redirected to the app through a Branch Web SDK call. Measured in minutes.
Click to x refers to events that occur after someone clicks a Branch link. If someone clicks and installs from a link, and comes back 10 days later to purchase, we would count that as a conversion, and it would surface in our dashboard. Measured in days.
Impression to x refers to events that occur after someone views a Branch impression link. Measured in days.
Re-engagement Inactivitydefines the period between two events that a user must be inactive in order to define the later event as a re-engagement. Used in re-engagement cohort analysis but not activity analysis.
If you are an Admin, you have edit access to the Partner Management tab.
Each Universal Ad Partner has the following settings:
- Account Settings
- Partner Credentials; e.g. API Key, SDK Key, Security Token.
- Postback Config
- Partner supported postback templates per conversion type
- Link Parameters
- Parameters added to the Partner's link by default; not editable.
- Attribution Windows
- Use a custom attribution window to match AdAction Engage's attribution windows. This overrides your app level attribution windows.
Updated about a month ago