Data Integration Implementation Guide
Overview
Data Integrations provide an easy way to automatically send Branch data to your other analytics services and marketing tools using pre-formatted webhooks.
This guide will walk you through how to send your Branch data to our Data Integration partners. For most integrations, configuration just requires you to input your credentials and hit “Enable”.
Paid Product
Data Integrations are included in Branch’s Data Feeds offering, which can be purchased according to Branch’s pricing schedule, and is available at no additional charge to customers who are on Launch and Startup plans for Journeys, Universal Email, or Universal Ads.
Without Data Feeds, you can still export Branch data in CSV form directly from the Branch dashboard.
Data Limitations
Please note that installs and other events attributed to Facebook Ads, Snap, Twitter Ads, or TikTok will not be sent to third parties via Data Integrations.
For more information, please refer to the following:
Data Changes Post iOS 14.5
Apple requires users to opt into sharing their device data through Apple's AppTrackingTransparency framework. When an install is attributed to paid ads, a 2nd install event will fire post user opt-in
Opt-ins will affect your paid ads attributed install events as they will be delayed until opt-in. No data will be available for opted-out users unless another Branch-attributed channel was encountered (Quick Link, Journeys, Email, etc.). Our recommendation is to use a different identifier (ex. IDFV) to de-dupe install events on your partner systems.
For data integration partner-specific impacts, visit Impact of iOS 14 on Branch Data Integrations
For additional information on changes post iOS 14.5, visit our FAQ Pages
1. Verify the Data Partner Accepts the Events You Want
The events Branch sends to third party data tools varies based on the events the partner supports as well as whether or not you've implemented the Branch SDK to measure said events.
All non-attributed events will be excluded. Branch also sends all the data that is attached to the link that drove the referred event. This will allow you to analyze which campaigns, channels, etc. are helping you acquire and engage users.
| Data Integration Partner | Branch Events Sent to Partner |
|---|---|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
⚠ AppsFlyer may not properly attribute installs to Journeys and other Branch Link clicks due to lack of IDFA on click ⚠ There may be a delay in clicks arriving at AppsFlyer via Webhook and the install event being sent to AppsFlyer by the AppsFlyer SDK |
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
|
 |
|
 |
|
 |
|
 |
|
 |
|
2. Complete Data Integration Prerequisites
Developer Required
- Implement the Branch SDK
- Ensure App Events are Measured
- You also need to be a customer to the third party and have their respective SDK installed in your app.
3. Retrieve Keys/Credentials From Your Partner
Find your Partner's Keys/Credentials. Later, you'll enter them into the Branch Dashboard.
| Data Integration Partner | Partner Keys/Credentials |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4. Enable the Integration
To enable the integration:
- In the left-hand navigation, under the Exports section, click Data Feeds.
- On the Data Feeds Manager page, click the Data Integrations tab at the top.
- Search for and click on your data partner.
- Provide the necessary credentials on the data partner's Export page.
- Click Enable.
5. Pass ID/Metadata to Branch (Partner Specific)
For some partners, you'll need to make sure to pass through the correct identifiers to the Branch SDKs. In order to do so, retrieve the ID from the partner SDK and pass this value to Branch using the following method:
setRequestMetadataKey() method of the Branch SDKs: iOS | Android
| Data Integration Partner | Partner Key & Method to pass to Branch SDK |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Updated 4 months ago