Connect Branch and Google Analytics to unlock a more holistic picture of the customer journey for your app.
Send your Branch data to your Google Analytics dashboard, helping you understand the power of Branch as an acquisition and re-engagement pathway. If you're interested in the segment of users coming into your apps through Branch and want to measure their events against your other cohorts, this guide can help.
Once the Branch SDK is integrated into an app, Branch can detect which Branch Links are leading to opens, installs, re-installs, and down funnel events. Enabling this integration and providing your Google Analytics Tracking Id will result in Branch automatically forwarding events to Google Analytics, in the exact format Google Analytics expects. This includes automatically setting various UTM tags that can be used to determine the source of new users.
Branch Events Sent to Google Analytics
Branch will send installs and opens, commerce, content, user lifecycle, as well as any custom events you track with Branch. Clicks, web session starts, and web pageviews will not be sent. Branch also sends over analytics data that is attached to the link, whether it's UTM tags or fields set on the Branch Dashboard (e.g. Campaign, Channel, Feature). This will allow you to analyze which campaigns, channels, etc. are helping you acquire and engage users. You can see the list of fields that we send to Google Analytics here.
Branch 事件将与您在 Google Analytics（分析）中其他追踪的事件一起显示。这是设置了测试信息的 Sources 屏幕的示例。
To view installs and opens, as well as any custom events you track with Branch as they are occur, navigate to Real-Time > Events. The event category for all Branch events is BranchEvent.
In order to enable Google Analytics, you need to have completed the following:
- Admin access to your Branch Dashboard.
- Enabled Data Feeds for your Branch account.
- Contact your Branch account manager or visit https://branch.io/pricing
- Implemented the Branch SDK into your mobile app (iOS | Android)
- 实现 Google Analytics（分析）SDK
- Admin access to your Google Analytics account.
Enable Google Analytics
1. Retrieve IDs from Google Analytics
Log into your Google Analytics Dashboard. Make sure that you have admin access.
For Google Analytics 4 you need to retrieve your Measurement ID:
- In Admin, make sure that you have the desired account and property selected.
- In the Property column, click Data Streams, then click your web data stream. Your
G-XXXXMeasurement ID appears in the upper right portion of the panel.
For Universal Analytics (Legacy) you need to retrieve your Tracking ID:
- Go to Admin.
- In the Property column, click Property Settings. Your
UA-XXXXTracking ID appears at the top of the Property Settings Page
2. Connect Google Analytics in Branch
In the Branch Dashboard in Data Feeds → Data Integrations tab, find and search for Google Analytics.
Enter the IDs from the previous step. Enter them into the iOS and Android fields in the Branch Dashboard, and hit Save.
3. Pass Metadata to the Branch SDK
Developers on your mobile app are required for this step
For a given app session, the unique Google Analytics identifier needs to be passed to the Branch SDK (before the Branch SDK initializes) in order for Branch to properly send events to Google Analytics.
|Version||标识符||Google Shortcode||Branch Metadata Key|
|Google Analytics 4||用户 ID|
|Universal Analytics||Client ID (for device identification)|
Specify the Branch metadata key for your Google Analytics tracking identifier
Pass User ID to Branch
Pass Client ID to Branch
Note: You just need to pass a random UUID on install and store it in local storage for later use for the Branch SDK.
// Add before initializing Branch session. let uuid = UUID().uuidString; let branch = Branch.getInstance(); branch.setRequestMetadataKey("$google_analytics_client_id", uuid)
// Need import java.util.UUID // Call after instantiating Branch in your application's onCreate before you call Branch initSession UUID uuid = UUID.randomUUID(); String client_id = uuid.toString(); Branch.getInstance().setRequestMetadata("$google_analytics_client_id",client_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 Google Analytics. To verify data is being sent from Branch to Google Analytics, you can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:
|webhook partner key||equals||di_google_analytics|
Please be patient as data may take some time to flow through Branch's attribution systems and onto Google Analytics. If data has not appeared in Google Analytics after 30 minutes of completing a test conversion, review the above steps to see if you may have missed something.
Properties Sent to Google Analytics
|Property 名称||值||Sourced From||例如||必要项|
|追踪号码||Branch 操作后台 (Dashboard)||UA-XXXXXX-Y||是|
|客户 ID||(discussed above, includes ||AEBE52E7-03EE-455A-B3C4-E57283966239||是|
|Campaign 名称||utm_campaign or Branch campaign||"Beaches and breezes"||否|
|Campaign Source||utm_source or Branch channel||"Twitter"||否|
|Campaign Medium||utm_medium or Branch feature||"480banner"||否|
|Campaign 关键字||utm_term or Branch ||["Keyword1", "keyword3"]||否|
|Campaign 内容||utm_content or Branch tags||"Some content"||否|
|Device IP Address||由 Branch SDK 收集||18.104.22.168||否|
|Cache buster||[unix time + random number]||1461878903666||否|
If for some reason Branch does not receive an advertising identifier or hardware identifier, and you do not explicitly specify
$google_analytics_client_id, then Branch will send
anonymousas the Client ID (
cid). This is a required field by Google Analytics.
当 Branch 发送安装和打开时，Google Analytics（分析）将自动启动会话。因此，您应在应用启动时删除所有创建新会话的代码。例如，在 iOS 上，您可能会触发以下事件：
[builder set:@"start" forKey:kGAISessionControl];
- Check your Measurement/Tracking ID in the Branch Dashboard matches the Measurement/Tracking ID in Google Analytics
- 确保您正在查看 Google Analytics（分析）操作后台 (Dashboard)的正确部分。数据应显示在
Acquisition > Sources > All
- 检查您的 Google Analytics（分析）视图是否没有任何筛选项。例如，如果您的视图筛选掉了英国的用户，而 Branch open 来自英国的用户，则您将不会在视图中看到 Branch 的数据。
Updated 2 months ago