> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).

# Batch Configuration (New)

> Send Branch event data to Batch.com for push notification campaigns and mobile analytics.

![](https://help.branch.io/img/c9482d2-Batch__branch.png "Batch + branch.png")

## Overview

Batch.com is an SDK and marketing automation dashboard focused on marketing and transactional push notifications. It also includes mobile analytics which are useful to monitor and improve its users' customer retention as well as engagement.

## How does it work?

Once the Branch SDK is integrated into an app, Branch can detect which Branch Links are leading to installs, re-opens, and users' actions. Enabling this integration and providing your relevant IDs will result in Branch automatically forwarding referred events to Batch, in the exact format Batch expects.

### Branch events sent to Batch

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.

Batch supports the following events:

- Commerce Events
- Custom Events

## Before you begin

To set up the Batch integration, you first need to:

1. Admin access to your [Branch](https://dashboard.branch.io/) account.
2. Have data export functionality enabled on your Branch account. Availability varies by Branch plan. See [Branch pricing](https://www.branch.io/pricing/) or contact your Branch representative.
3. Implemented the Branch SDK into your mobile app ([iOS](https://help.branch.io/developer-hub/ios-sdk-overview.md) | [Android](https://help.branch.io/developer-hub/android-sdk-overview.md)).

   - [Track events](https://help.branch.io/developer-hub/track-branch-events.md)
4. [Implement the Batch SDK](https://doc.batch.com/developer).
5. Admin access to your Batch account.

## Enable Batch

Complete the following steps to enable Batch:

## 1. Retrieve IDs from Batch

Before you can enable the integration in Branch, you need to retrieve your credentials from your Batch account.

Branch requires these credentials to not only authenticate, but to ensure your Branch data is being sent to the correct account.

Branch requires the following credentials:

- REST API Key
- iOS API Key
- Android API Key

Refer to [Batch's documentation](https://doc.batch.com/dashboard/settings/app-settings#api-keys) on how to retrieve these keys.

## 2. Connect Batch in Branch

In Branch, go to **Configuration > Integrations** and select the **Data** tab. Search for **Batch** and select it to open its data partner page.

In the **Export** section, enter the following, then toggle **Export** to **Enabled** and select **Save**:

- **REST API key** (required).
- **iOS API key** (required).
- **Android API key** (required).

## 3. Pass metadata to the Branch SDK

> **Developer Required**
>
> Developers on your mobile app are required for this step.

Batch requires you to pass through the correct identifiers to the Branch SDKs. To do so, retrieve the ID from the Batch SDK and pass this value to Branch using the following method:

- `setRequestMetadataKey()` method of the Branch SDKs: [iOS](https://help.branch.io/developer-hub/ios-advanced-features.md#set-initialization-metadata) | [Android](https://help.branch.io/developer-hub/android-advanced-features.md#set-initialization-metadata)

> **IMPORTANT**
>
> To be able to match events with your users - you must send a Batch User ID using **batch_user_id** metadata key via .setRequestMetaData.
>
> You can find more about Custom user ID here: [https://doc.batch.com/ios/custom-data/customid#setting-up-a-custom-user-id](https://doc.batch.com/developer/sdk/ios/profile-data/custom-user-id)

## 4. Verify data sent

Once the above steps are complete, you are now ready to start launching campaigns. Branch-attributed conversions will be sent to Batch. To verify data is being sent from Branch to Batch, you can look at Branch's [Liveview Webhook Records](https://dashboard.branch.io/liveview/webhooks) and apply the following filter:

| Filter | Operator | Value |
| --- | --- | --- |
| webhook partner key | equals | di_batch |

> **Wait Period**
>
> Data may take some time to flow through Branch's attribution systems and onto Batch. If data has not appeared in Batch after 30 minutes of completing a test conversion, review the above steps to see if you may have missed something.