Advanced Compliance
Advanced Compliance
Access to Advanced Compliance requires premium product access. Please reach out to your account manager or contact sales.
Overview
Branch Advanced Compliance helps healthcare companies to benefit from Branch linking, web-to-app Journeys, and owned/earned/organic attribution. Privacy in the mobile marketing ecosystem is ever changing, and Branch strives to support all of your mobile linking and measurement needs.
Features include:
- Advanced Security Gateway - A separate data architecture, including an isolated network with custom traffic routing, strong authentication, and multiple levels of encryption.
- Protected Endpoint - Data will flow through a protected and isolated environment in which sensitive data is locked and subsequently available only where strictly necessary for specific business needs.
Branch Use Case & Feature Support
| Use Cases | Events |
|---|---|
| Deep Linking | Clicks |
| Organic Attribution | Opens |
| Journeys | Installs |
| Web Sessions | |
| Page Views | |
| Dismisses | |
| Content/Commerce/Custom/User-Lifecycle Events |
Compatible ESPs
The following is a list of compatible email service providers:
- Iterable v1
- Iterable v2
- SparkPost
- Braze & Mailjet
- Braze & Sendgrid
- Braze & Sparkpost
Prerequisites
In order to enable Advanced Compliance, you need to have completed the following:
- Created a Branch Dashboard.
- Implemented the Branch SDK into your mobile app (iOS | Android | Web)
- Developer implements SDK methods into your mobile/web app.
- IT & Identity Provider ready for setting up SSO.
- Your company meets the minimum security configuration requirements:
- 2FA enabled for login access
- Antivirus software enabled on company machines
- Intrusion detection system enabled on company machines
- Strong complex use of password configuration
- Frequent rotation of passwords
Enable Advanced Compliance
1. Configure your Branch SDK
Implement the setAPIUrl(...) method from the Branch SDK and set it to use the following protected endpoint:
https://protected-api.branch.io
SDK Version Requirement
| Platform | Version |
|---|---|
| Android | v5.9.0 |
| iOS | v3.2.0 |
| Web | v.2.82.0 |
| React Native | v6.2.0 |
2. Configure your Branch Link Domain
You may use the app.link subdomain that you already have set for your Branch app or you can set up a custom root domain for Advanced Compliance:
Custom Subdomain
Using a Custom Subdomain for Advanced Compliance is not support. Only
app.linkor custom root domains are supported.
3. Configure SSO
This step is not required, but it is highly recommended as single sign-on (SSO) is beneficial for increased security:
FAQ
Are there certain features that are currently not compatible with Advanced Compliance?
All features not included in this list are currently not supported. Branch is currently working on supporting other products/use cases like:
- Universal Ads
- Universal Email
- SEO App Attribution
Does the product work with all of your SDKs?
Usage of the protected endpoint is available through these SDK versions. Branch is currently working on supporting the other SDKs and Wrappers/Plugins.
What happens to my users using an older version of my app?
For the users who have not updated their app version to include the use of the protected endpoint, all data sent to Branch will be excluded from Advanced Compliance.
If I use a custom root domain, what happens to my app.link URLs?
The >app.link domain will continue to work, but newer links will be created using the custom root domain by default.
Updated 4 days ago