This documentation explains how to send mParticle events to your Branch dashboard. If you'd like to send Branch installs to your mParticle dashboard, please review the Branch/mParticle Data Integration.
These instructions apply to the mParticle SDK version 7+ integration
mParticle introduced a new attribution & deep linking API in v7 of their SDK (http://docs.mparticle.com/developers/sdk/ios/getting-started/#upgrade-to-version-7-of-the-sdk), so please contact your Branch or mParticle Account Managers for more details, if you have mParticle SDK < v7 installed in your app.
Inconsistent Universal links behavior on iOS 11.2
After updating a device to iOS 11.2, we found that the app's AASA file is no longer downloaded reliably onto your user’s device after an app install. As a result, clicking on Universal links will no longer open the app consistenly. You can set forced uri redirect mode on your Branch links to open the app with URI schemes. View details of the issue on the Apple Bug report.
- Make sure Bundle Id matches your Branch Dashboard
- From your Apple Developer Account
Add your link domains from your Branch Dashboard
-alternateis needed for Universal Linking with the Web SDK inside your Website
test-is needed if you need use a test key
- If you use a custom link domain, you will need to include your old link domain, your
-alternatelink domain, and your new link domain
- Confirm entitlements are within target
Add Branch Dashboard values
branch_app_domainwith your live key domain
- Add your URI scheme as
- Do NOT add your API keys to the file (mParticle handles this via the dashboard)
Before you can enable Branch in your mParticle dashboard, you must retrieve your Branch Key on the Link Settings page of your Branch dashboard.
Please follow mParticle's documentation on how to Connect an Event Output; i.e. enable the Branch integration.
If you have enabled Apple Search Ads for your Branch implementation, you must also check
Enable Apple Search Adsin the Connection Settings.
Once you have added the kit and configured your branch API key in the mParticle dashboard, the mParticle SDKs will take care of initializing the Branch SDK and forwarding the appropriate application lifecycle events to handle deep links.
Option 1: CocoaPods
platform :ios, '8.0' target 'APP_NAME' do # if swift use_frameworks! ‘pod 'mParticle-BranchMetrics', '~> 7' end
Option 2: Carthage
The mParticle iOS SDK (version 5.4.1 and later) will automatically call the following methods of the Branch Kit:
This means mParticle will automatically handle initializing Branch sessions. However, please ensure
.onAttributionComplete is enabled in the
mParticle appDelegate proxy not enabled
If the mParticle appDelegate proxy is not enabled, you must add mParticle's URI & Domain relays to the appDelegate.
At this point you should start seeing your Branch session data - including installs, re-opens, and any custom events - in your Branch dashboard.
Our integration with mParticle supports the creation and attribution of deep links to install and open an app. A deep link will typically contain some additional information to be used when the user ultimately opens your application, so that you can properly route the user to the appropriate content, or otherwise customize their experience.
Please ensure you've followed mParticle's documentation to ensure your deep link data is being retrieved.
mParticle in React Native
If you integrate mParticle in React Native, you will still integrate the Branch kit as a Native module and follow the setup steps above. However, instead of retrieving deep link data in the the native layer, you'll retrieve deep link data via mParticle's React Native function found here.
Please refer to the Branch iOS SDK troubleshooting section.
Updated about a month ago