Branch

Branch.io is an industry leader in cross-platform attribution, mobile app measurement, and deep linking. Many top-ranking apps use Branch to increase their performance and revenue through better performance and engagement.

RudderStack supports Branch as a destination where you can seamlessly send your customer data.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

Before configuring Branch as a destination in RudderStack, verify if the source platform is supported by Branch by referring to the table below:

To learn more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.

Once you have confirmed that the source platform supports sending events to Branch, follow these steps:

1. From your RudderStack dashboard, add a source. Then, from the list of destinations, select Branch Metrics.
2. Assign a name to the destination and click Continue.

Connection settings

To successfully configure Branch as a destination, you will need to configure the following settings:

• Branch key: Enter your Branch key from the Settings section in the Branch dashboard.
• Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to Branch.

For more information on this setting, refer to the Client-side Events Filtering guide.

Adding device mode integration

Depending on your platform of integration, follow the below steps below to integrate Branch with your app.

pod 'Rudder-Branch', '0.1.3'

$ pod install

RudderConfigBuilder *builder = [[RudderConfigBuilder alloc] init];
[builder withDataPlaneUrl:<data_plane_url>];
[builder withFactory:[RudderBranchFactory instance]];
[builder withLoglevel:RudderLogLevelDebug];
[RudderClient getInstance:<write_key> config:[builder build]];

pod 'RudderBranch', '~> 1.0.0'

import RudderBranch

@import RudderBranch;

let config: RSConfig = RSConfig(writeKey: WRITE_KEY)
            .dataPlaneURL(DATA_PLANE_URL)

RSClient.sharedInstance().configure(with: config)
RSClient.sharedInstance().addDestination(RudderBranchDestination())

RSConfig *config = [[RSConfig alloc] initWithWriteKey:WRITE_KEY];
[config dataPlaneURL:DATA_PLANE_URL];

[[RSClient sharedInstance] configureWith:config];
[[RSClient sharedInstance] addDestination:[[RudderBranchDestination alloc] init]];

repositories {
    mavenCentral()
}

implementation 'com.rudderstack.android.sdk:core:1.0.1'
implementation 'com.rudderstack.android.integration:branch:0.1.3'

// branch SDK requirements
implementation 'io.branch.sdk.android:library:4.3.2'
implementation'com.android.installreferrer:installreferrer:1.1.2'
implementation 'com.google.firebase:firebase-appindexing:19.1.0'
implementation 'com.google.android.gms:play-services-ads:16+'

val rudderClient: RudderClient = RudderClient.getInstance(
    this,
    <write_key>,
    RudderConfig.Builder()
        .withDataPlaneUrl(<data_plane_url>)
        .withLogLevel(RudderLogger.RudderLogLevel.DEBUG)
        .withFactory(BranchIntegrationFactory.FACTORY)
        .build()
)

Identify

The identify call associates a user to their actions and also captures the traits associated with that user.

A sample identify call captured from the RudderStack iOS SDK is as shown:

[[RudderClient sharedInstance] identify:@"developer_user_id"
                                 traits:@{@"foo": @"bar", @"foo1": @"bar1"}];

You can call identify when the user registers to the app for the first time, logs into the app, or updates their information.

Track

The track call lets you record the customer events along with any properties associated with them.

A sample track call is shown below:

[[RudderClient sharedInstance] track:@"test_event"
                          properties:@{@"key":@"value", @"foo": @"bar"}]

All the events tracked by RudderStack are divided into three major Branch event categories:

• Commerce events
• Content events
• Lifecycle events

Commerce event mapping

The following table lists the mapping between the RudderStack ecommerce events and the Branch events:

RudderStack also maps the Spend Credits event to Branch’s SPEND_CREDITS, although it is not directly a part of the ecommerce events.

Content event mapping

The following table lists the mapping between the RudderStack events and the Branch Content events:

The above mentioned events are a part of the RudderStack ecommerce events but are mapped to Branch’s Content events.

Lifecycle event mapping

RudderStack supports mapping the following Branch lifecycle events:

Property mappings

The following table lists the mapping of the accepted RudderStack properties common to all events:

FAQ

Where can I find the Branch key?

To retrieve your Branch key, follow these steps:

1. Log into your Branch dashboard.
2. Go to Account Settings > Profile.
3. You can find the Branch Key under Branch Key and Secret section:

Questions? Contact us by email or on Slack