> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt). # Data Integration Implementation Guide (New) > Send Branch data to data partners with pre-formatted webhooks, and see the setup steps for each integration. ## Overview Data partner integrations provide an easy way to automatically send Branch data to your other analytics services and marketing tools using pre-formatted webhooks. This guide walks you through how to send your Branch data to our data integration partners. For most partners, configuration just requires you to input your credentials, enable the integration, and save. You can find all data integrations in Branch under **Configuration > Integrations**, on the **Data** tab. > **Note: this guide is for new Branch** > > Please note that this guide is about integrating data partners in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on integrating data partners in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/data-integration-implementation-guide.md). ### Import vs. export Each data partner supports one or both of the following directions, shown as separate sections on the partner's configuration page: - **Export**: Branch sends your attributed event data to the data partner. Most data partners are export-only. - **Import**: Branch receives events from the partner, so downstream conversions can be attributed to Branch Link clicks. Data partners that support both import and export (for example, mParticle and Segment) show both sections on a single configuration page in Branch, each with its own toggle. ### Data limitations Please note that installs and other events attributed to Facebook Ads, Snap, Twitter Ads, or TikTok **will not be sent to data partners**. For more information, please refer to the following: - [Facebook Ads Data Limitations](https://help.branch.io/marketer-hub/meta-ads-overview.md#data-limitations) - [Exporting Snap Data](https://help.branch.io/marketer-hub/snap.md#export-snap-data) - [Twitter Ads Data Sharing](https://help.branch.io/marketer-hub/twitter-ads.md#twitter-data-sharing) - [TikTok Data Sharing](https://help.branch.io/marketer-hub/tiktok-for-business.md#data-sharing-and-access) ### iOS 14.5 data changes Apple requires users to opt into sharing their device data through Apple's [AppTrackingTransparency](https://developer.apple.com/app-store/user-privacy-and-data-use/) framework. When an install is attributed to paid ads, a second install event will fire after user opt-in. Opt-ins will affect your paid ads attributed install events as they’ll be delayed until opt-in. No data will be available for opted-out users unless another Branch-attributed channel was involved (Short Link, Banners, Email, etc.). Our recommendation is to use a different identifier (ex. IDFV) to de-dupe install events on your partner systems. For additional information on changes post iOS 14.5, visit our [FAQ pages](https://help.branch.io/marketer-hub/category/ios-14-faqs.md). ## 1. Verify data partner accepts your events The events Branch sends to data partners 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. Each data partner has a dedicated configuration guide covering the events Branch sends to (or imports from) that partner: ### Export partners - [Airship Configuration](https://help.branch.io/developer-hub/airship-configuration-new.md) - [Batch Configuration](https://help.branch.io/developer-hub/batch-configuration-new.md) - [Braze Configuration](https://help.branch.io/developer-hub/braze-configuration-new.md) - [CleverTap (Export) Configuration](https://help.branch.io/developer-hub/clevertap-data-configuration-new.md) - [Google Analytics Configuration](https://help.branch.io/developer-hub/google-analytics-configuration-new.md) - [Google Analytics 4 Configuration](https://help.branch.io/developer-hub/google-analytics-4-configuration-new.md) - [Leanplum Configuration](https://help.branch.io/developer-hub/leanplum-configuration-new.md) - [MoEngage Configuration](https://help.branch.io/developer-hub/moengage-configuration-new.md) - [Movable Ink Configuration](https://help.branch.io/developer-hub/movable-ink-configuration-new.md) - [mParticle (Export) Configuration](https://help.branch.io/developer-hub/mparticle-export-configuration-new.md) - [Segment (Export) Configuration](https://help.branch.io/developer-hub/segment-export-configuration-new.md) ### Import partners - [mParticle (Import) Configuration](https://help.branch.io/developer-hub/mparticle-import-configuration-new.md) - [Segment (Import) Configuration](https://help.branch.io/developer-hub/segment-import-configuration-new.md) ## 2. Complete data integration prerequisites Before enabling a data partner integration, you'll need to ensure the Branch SDK is implemented in your app and that you're tracking the events you want to send to your partner. Some data partners also require the partner's SDK to be installed in your app. See our [developer documentation](https://help.branch.io/developer-hub/data-integration-steps-for-developers.md) for implementation details. You'll also need Data Feeds included in your Branch plan. If your plan does not include Data Feeds, the **Data** tab will be locked. To get access, contact your Branch account manager or [Branch sales](https://branch.io/contact-sales/). ## 3. Enable the integration Before you start, retrieve any keys/credentials the integration requires from your partner's dashboard (for example, API keys or write keys per platform). If your partner has a dedicated configuration guide, the guide will explain where to find them, see [Partner-specific SDK configuration](#_4-complete-partner-specific-sdk-configuration) below. To enable a data partner integration: 1. In the left-side navigation, under **Configuration**, click **Integrations**. 2. On the **Integrations** page, select the **Data** tab. 3. Search for and click your data partner. If the **Data** tab is locked, data integrations are not included in your current plan, see [Prerequisites](#_2-complete-data-integration-prerequisites). 4. On the partner's configuration page, configure the section(s) available for that partner: - **Export**: Enter the credentials required by the partner, then set the **Export** toggle to **Enabled**. - **Import**: Select the platforms you'd like to import events from, then set the **Import** toggle to **Enabled**. 5. Select **Save** in the top-right corner of the page. Your changes do not take effect until you click **Save**. > **Note: import and export managed separately** > > If a data partner integration has both export and import capabilities, you can manage these separately. One can be enabled while the other is disabled. To find partners you've already configured, select **My partners** on the **Data** tab. To disable an integration, set the relevant toggle to **Disabled** and select **Save**. ## 4. Complete partner-specific SDK configuration Some partners require additional SDK configuration to pass specific identifiers or metadata to Branch. If your partner requires this step, your development team will need to make SDK updates. See our [developer documentation](https://help.branch.io/developer-hub/category/data-partners-new.md) for implementation details. Partners with more involved setup have dedicated configuration guides. See the [Custom Export Provider Technical Guides](https://help.branch.io/developer-hub/category/custom-export-provider-technical-guides-new.md) and [Custom Import Provider Technical Guides](https://help.branch.io/developer-hub/category/custom-import-provider-technical-guides-new.md) sections of the documentation for the full list, or the [lists above](#_1-verify-data-partner-accepts-your-events).