Adobe Analytics (Data Connector)

🚧

Data Connector Update

On August 1, 2021, Adobe will no longer support the Data Connectors. To support these changes, Branch has built out a new integration called Adobe Analytics (Processing Rules).

If you are currently using this integration and are satisfied with the data being sent from Branch to Adobe Analytics, then no action is needed; however, if you would like to configure the data manually, you may migrate to the new Processing Rules Integration.

概述

只需按一下键,便可以将 Branch 数据发送到 Adobe Analytics 操作后台 (Dashboard),以帮助您了解 Branch 作为获客途径的功能。

它是如何工作的?

将Branch SDK集成到应用后,Branch可以检测到哪些链接导致安装,重新打开和用户'操作。启用此集成并提供您的Adobe Analytics信息将导致Branch通过服务器到服务器集成自动将引用的事件转发到Adobe Analytics。

Branch 发送什么事件?

Branch will send referred installs and opens, reinstalls, as well as any custom and commerce events you track with Branch. Non-referred events, clicks, web session starts, and pageviews will be excluded. Branch also sends all the analytics tags that are 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.

它是什么样子的?

Branch events will appear on the Adobe Analytics dashboard through Reports > Custom Conversion > Branch eVar. Note, this will automatically appear once the Branch Data Connector is enabled through the Adobe Analytics dashboard.

您'会灵活地分析需要在Adobe分析平台,为数据发送Branch在Adobe Analytics(分析)映射到一个顶级EVAR数据。此eVar包含广告系列,渠道,目标,事件名称和操作属性,它们是您的分析标记。

11721172 14981498

Branch事件与Adobe Analytics事件类似,因为它们可用于构建自定义报告并在各个页面和仪表板上进行跟踪。但是,与正常事件不同,Branch事件首先包含有关用户如何最终进入您的应用的有价值的信息。

1. 完整的数据集成先决条件

🚧

先决条件

BRANCH

Adobe Analytics

2.在 Adobe 中激活 Branch 数据连接器

  1. 在Adobe Analytics仪表板的Admin 选项卡下,找到Data Connectors
14321432
  1. 点击+Add New ,搜索" Branch, " ,然后点击Activate
13121312

3.配置 Branch 数据连接器

整合设定

当您激活数据连接器时,这些将自动配置。

变量映射

Map your Branch events to your chosen eVar. In the example below, it will be mapped to Custom eVar 1, renamed to the SiteCatalyst metric Branch

24242424

数据设定

Branch 已为要提取的 Branch 数据提供了默认分类规则集。如下将 Branch 分析数据映射到 Adobe 分类。您可以根据需要更改此分类规则集,但不需要进行编辑。我们还包括 Branch 标签,因此您可以创建一个新规则,以进一步细分您的分析数据以实现高级可见性。

Adobe 分类Branch机构分析标签
SourceChannel
CampaignCampaign
MediumFeature
ActionBranch Event Name
Action PropertyBranch Tags
24102410

评测总结

最后,查看集成,滚动到屏幕底部,然后点击 Activate Now 以启用集成。

738738

3.配置 Branch 仪表板

检索您的 Adobe Analytics 信息

前往 Branch 之前,请在 Adobe Analytics 操作后台 (Dashboard)中前往 Mobile Marketing UI 并找到您的应用。

Manage App Setting -> SDK Analytics Options ,找到以下数据:

Branch 字段Adobe 字段值
ProtocolUse HTTPS Check Box (if checked, select HTTPS)
Analytics Server DomainTracking Server
Omniture iOS/Android Server KeyReport Suite ID for that app
TimestampOffline Tracking

For Analytics Server Domain, please do not include http or https. If your value for this is http://test.com, simply put in test.com. This means no extra slashes and no protocol.

输入 Adobe Analytics 信息

  1. 在 Branch 操作后台 (Dashboard)(dashboard.branch.io)上,前往 Data Integrations page
  2. 找到 Adobe Analytics 并选择 Enable
  • 如果您尚未输入帐单信息,请立即输入。
  1. 输入您的 Adobe Analytics 信息,然后点击 Save

4.将 Adobe ID 传递到 Branch

🚧

Adobe IDs

This step is not required if the Branch SDK is implemented using Adobe Launch
If this step is not completed, events Branch sends to your Adobe Report Suite will not reliably appear, and will not connect to other data already tracked by Adobe Analytics

You'll need to pass through all user IDs configured with Adobe, to the Branch SDKs (There are three possible Adobe IDs this integration can track). First, figure out which ID you use by asking your Adobe Consultant, and then pass that value to Branch by calling setRequestMetadataKey (iOS) or .setRequestMetadata (Android) on the Branch SDK, BEFORE calling initializing session on the Branch SDK.

例如,如果您的 Adobe 集成使用 Marketing Cloud 访客 ID 或 Experience Cloud ID,请从 Adobe SDK 中检索 ID,然后使用名为 $marketing_cloud_visitor_id 的 Key 将其传递给Branch SDK。以下所有 ID 类型的示例代码片段:

Marketing Cloud 访问者 ID /体验 Cloud ID

Value sent to Branch using $marketing_cloud_visitor_id key. Value sent to Adobe as mid. Check to see if a cloud id is present, if not, initialize branch within callback to utilize the returned cloud id, else initialize branch outside of the Adobe callback. The best practice is to store the cloud id and then reuse for subsequent app launches

  • iOS-Objective C
//Inside *didFinishLaunchingWithOptions*
Branch *branch = [Branch getInstance];
            if (experienceCloudId == nil) {
                [ACPIdentity getExperienceCloudId:^(NSString * _Nullable retrievedCloudId) {    
                    [branch setRequestMetadataKey:@"$marketing_cloud_visitor_id" value:[retrievedCloudId]];
                    ...
                    [branch initSessionWithLaunchOptions...];  
                }];
            } else {
                [branch setRequestMetadataKey:@"$marketing_cloud_visitor_id" value:[experienceCloudId]];
                ...
                [branch initSessionWithLaunchOptions...];  
                        }
  • iOS-Swift
//Inside *didFinishLaunchingWithOptions*
            if let branch = Branch.getInstance() {
                if experienceCloudId == nil { 
                    ACPIdentity.getExperienceCloudId { (retrievedCloudId) in 
                        branch.setRequestMetadataKey("$marketing_cloud_visitor_id", value:retrievedCloudId)
                        ...
                        branch.initSession(...)
                    }  
                } else {
                    branch.setRequestMetadataKey("$marketing_cloud_visitor_id", value:experienceCloudId)
                    ...
                    branch.initSession(...)
                }
            }
  • Android
//Before you initialize the session.
            if experienceCloudId == null {
                Identity.getExperienceCloudId(new AdobeCallback<String>() {    
                    @Override    
                    public void call(String id) {  
                        Branch branch = Branch.getInstance();      
                        branch.setRequestMetadata("$marketing_cloud_visitor_id", id);
                        ...  
                        branch.sessionBuilder(this)…init();
                    }
                });
            } else {
                Branch branch = Branch.getInstance();      
                branch.setRequestMetadata("$marketing_cloud_visitor_id", experienceCloudId);
                ...  
                branch.sessionBuilder(this)…init();
            }

如果您'担心额外的延迟,则可以在启动时有条件地调用对ExpectDelayedSessionInitialization的调用。


            LauncherActivity.onStart() {
                    ...
                    Branch.expectDelayedSessionInitialization()
            }

                        asyncOperationCallback() {
                            Branch.sessionBuilder(activity).withCallback(callback)...init();
                        }

Analytics(分析)自定义访问者 ID

Value sent to Branch using the $analytics_visitor_id key. Value sent to Adobe as vid. This is a custom user ID that can be set using the Adobe SDK.

  • iOS-Objective C
//Inside *didFinishLaunchingWithOptions*
//Setting the Identifier with Adobe
[ADBMobile setUserIdentifier:@"Whipple"];
//Passing the Identifier to Branch
Branch *branch = [Branch getInstance];
[branch setRequestMetadataKey:@"$analytics_visitor_id" value:[ADBMobile userIdentifier]]
...
[branch initSessionWithLaunchOptions...]
  • iOS-Swift
//Inside *didFinishLaunchingWithOptions*
//Setting the Identifier with Adobe
ADBMobile.setUserIdentifier("Whipple")
//Passing the Identifier to Branch
if let branch = Branch.getInstance() {
    branch.setRequestMetadataKey("$analytics_visitor_id", value:ADBMobile.userIdentifier())
    ...
    branch.initSession(...);
}
  • Android
//Before you initialize the session.
//Setting the Identifier with Adobe
Config.setUserIdentifier(""Whipple"");
//Passing the Identifier to Branch
Branch branch = Branch.getInstance();
Branch.getInstance().setRequestMetadata(""$analytics_visitor_id"", Config.getUserIdentifier());
...
Branch.sessionBuilder(this)...init();

Analytics(分析)访问者 ID

Value sent to Branch using the $adobe_visitor_id key. Value sent to Adobe as aid

  • iOS-Objective C
//Inside *didFinishLaunchingWithOptions*
Branch *branch = [Branch getInstance];
[branch setRequestMetadataKey:@"$adobe_visitor_id" value:[ADBMobile trackingIdentifier]];
...
[branch initSessionWithLaunchOptions...]
  • iOS-Swift
//Inside *didFinishLaunchingWithOptions*
if let branch = Branch.getInstance() {
    branch.setRequestMetadataKey("$adobe_visitor_id", value:ADBMobile.trackingIdentifier());
    ...
    branch.initSession(...);
}
  • Android
//Before you initialize the session.
Branch branch = Branch.getInstance();
branch.setRequestMetadata(""$adobe_visitor_id"", Analytics.getTrackingIdentifier());
...
Branch.sessionBuilder(this)...init();

高级

Branch 发送到 Adobe Analytics 的内容

Branch 从 Adobe 上下文数据中的 Branch Link 数据发送以下值:

Adobe 分类Branch机构分析标签例如
SourceChannel我们的网站
CampaignCampaignJourneys 测试 Campaign
MediumFeatureJourneys(网站向App引流解决方案)
ActionBranch Event NameInstall
Action PropertyBranch Tagstag=bar&tag2=1234
CustomBranch Custom Datakey=value

如果创建 Quick Link(快速链接)并指定分析,则这些分析将显示在 Adobe Analytics 报告套件中。

支持中心

问题排查时可以采取一些常见的策略。

模拟事件后未显示数据

使用 Adobe Analytics 操作后台 (Dashboard),最多可能需要2个小时才能显示数据。我们建议您模拟一个测试环节10-15事件,并验证它们显示了两个小时后,使反馈是透明的和明显的。

If you're not seeing an Adobe ID appended to the Branch events in Adobe's dashboard, you can call setDebug on the Branch SDK and inspect the requests to v1/open in-app to confirm the ID is being sent. The key you want to find in this request payload is either $adobe_visitor_id$marketing_cloud_visitor_id, or $analytics_visitor_id

什么是上下文数据,Branch 在哪里将其提供给 Adobe?

When sending server to server calls to Adobe, Context Data is the part in-between &c. and &.c in the server call. This call cannot be seen via the client (for example, it is not available via Charles Proxy). To see the detailed Branch server calls, please reach out to your Branch Account Manager. In general, values sent in Context Data can be visualized in the Adobe dashboard, and values outside of Context Data cannot. Values like the user identity (e.g.vidmid or aid) are sent to Adobe, but not in Context Data, so they can’t be visualized in the Adobe Report Suite. However, they are appropriately formatted for Adobe to log events for that user in Adobe.