筛选项

Braze

Connect Branch and Braze to unlock a more holistic picture of the customer journey for your app.

1328

概述

Braze 将数据,团队和技术结合在一起,为世界各地的客户创建杰出的品牌消息传递体验。

它是如何工作的?

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 Braze, in the exact format Braze expects.

Branch Events Sent to Braze

Branch 发送给第三方数据工具的事件会根据合作伙伴支持的事件以及您是否已实施 Branch SDK 来衡量所述事件而有所不同。

Braze 支持以下事件:

  • Installs

Metadata sent to Braze
Branch 发送给第三方数据工具的 metadata会根据合作伙伴支持的数据以及您是否已实现 Branch SDK 来测量所述数据而有所不同。

Branch机构分析标签Braze Data Placeholder Tag
Campaigncampaign
Channelsource
Adgroupadgroup
Adad

先决条件

In order to enable Braze, you need to have completed the following:

  1. Admin access to your Branch Dashboard.
  2. Enabled Data Feeds for your Branch account.
  3. Implemented the Branch SDK into your mobile app (iOS | Android)
  4. 实现 Branch SDK
  1. Admin access to your Braze account.

Enable Braze

1. Retrieve IDs from Braze

您需先从 Braze 帐户中检索凭据,然后才能在 Branch 操作后台 (Dashboard)上启用集成。

Branch 要求这些凭据不仅可以进行身份验证,还可以确保将 Branch 数据发送到正确的帐户。

Branch 要求以下凭据:

  • API Key
  • Braze REST Endpoint

要找到您的 Braze API Key:

  1. 在 Braze 操作后台 (Dashboard)上,前往 App Settings 部分,然后点击 3rd Party Integrations
  2. 从那里可以获取您的 API key(页面上列出的所有归因合作伙伴都相同)。

To find the correct Braze REST Endpoint, please refer to Braze's documentation.

2. Connect Braze in Branch

In the Branch Dashboard in Data Feeds → Data Integrations tab, find and search for Braze.

Enter the API Key and Rest Endpoint from the previous step and hit Save.

3. Pass Metadata to the Branch SDK

👍

需要开发人员

Developers on your mobile app are required for this step

Braze 要求您将正确的标识符传递给 Branch SDK。为此,请从 Braze SDK 中检索 ID,然后使用以下方法将此值传递给 Branch:

  • setRequestMetadataKey() Branch SDK 方法:

NOTE You must set the correct key before initializing the Branch session. You must also initialize the Braze SDK before setting the request metadata in the Branch SDK.

📘

February 2023 Updates

Prior to February 2023, our Branch attribution integration used the IDFV as the primary identifier to match iOS attribution data. It is not necessary for Braze customers using Objective-C to fetch the Braze device_id and sent to Branch upon install as there will be no disruption of service.

For those using the Swift SDK v5.7.0+, if you wish to continue using IDFV as the mutual identifier, you must ensure that the useUUIDAsDeviceId field is set to false so there is no disruption of the integration.

If set to true, you must implement the iOS device ID mapping for Swift in order to pass the Braze device_id to Branch upon app install in order for Braze to appropriately match iOS attributions.

You must also disable and re-enable the Braze Data Integration connection on the Branch Dashboard

Branch.getInstance().setRequestMetadata("$braze_install_id", Braze.getInstance(context).deviceId);
Branch.getInstance().setRequestMetadata("$braze_install_id", Braze.getInstance(context).deviceId)
Branch.getInstance.setRequestMetadata("$braze_install_id", braze.deviceId)
  [[Branch getInstance] setRequestMetadataKey:@"$braze_install_id" value: braze.deviceId];

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 Braze. To verify data is being sent from Branch to Braze, you can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:

FilterOperator
webhook partner keyequalsdi_braze

📘

Wait Period

Please be patient as data may take some time to flow through Branch's attribution systems and onto Braze. If data has not appeared in Braze after 30 minutes of completing a test conversion, review the above steps to see if you may have missed something.