在自定义子域设置后,Branch.io链接不跟踪点击次数

时间:2017-08-30 16:58:43

标签: branch.io

背景

  • 我有一个使用默认分支域设置的应用程序(例如:my.app.link)。
  • 使用my.app.link创建链接。其中许多链接需要镜像我在生产中使用的现有链接(我们正在迁移的另一个链接服务)使用Branch.io中不支持的格式,所以我不得不使用' - '来解决这个问题。代替'。'在链接的路径中。这是Branch推荐的解决方案,保证'。'将在Branch.io的后端转换为' - '(这似乎工作正常)。
  • 我最近有一个自定义子域CNAME到custom.bnc.lt(例如:myapp.mydomain.com)。
  • Branch.io仪表板中的链接设置已更新为使用自定义子域(更改有效:“域已正确设置且SSL正在运行。”)。

问题

  1. 所有预先存在的快速链接仍然具有旧的默认域名,即使他们“使用”新的子域名,也没有点击注册。
  2. 复制其中一个链接会获取新的子域名,但创建的URL是http,而不是https(这是我们创建的任何其他链接的默认值,似乎没有办法选择一个协议或者其他,也不能在仪表板中更新)。这似乎也导致链接点击无法在仪表板中跟踪。
  3. 我们使用解决方法镜像来自其他平台的链接(将'。'替换为' - '),这似乎也会导致链接点击不在仪表板中跟踪。
  4. 问题

    Branch.io如何处理使用自定义子域为应用设置的快速链接的链接点击次数?配置的链接是否需要与设备上单击的链接1:1匹配?

    如何修复原始链接,特别是如果我不能复制它们(以获取自定义子域),其方式与我创建的上一个链接的比例为1:1(因为新链接是http和其他是https,将在实时/生产环境中分发?)

    为什么我设置为x-y-z的x.y.z链接没有分支跟踪链接点击?这种别名工作正常,似乎在测试中跟踪点击次数。

1 个答案:

答案 0 :(得分:0)

Amruta from Branch.io here:

1. How does Branch.io handle link clicks for a quick link that has been set up for an app using a custom subdomain?

A: For all Branch links, every time a Branch link is clicked the click is is registered by Branch. Using a custom domain (if configured properly) should not cause any problems in registering clicks on the Branch dashboard neither should using Quick links cause any issues. Also Branch links with either schemes http:// or https:// register link clicks. Having Branch links with http:// scheme should not cause any issues with registering link clicks

2.All pre-existing quick links still have the old default domain

A: The old links created on the app.link will not be updated with your custom domain. If you wish to use links with your link domain, you can create new links with the same link parameters. (PS: both links on the old app.link domain and links on your custom domain should work as before if you still have your App configured to support the app.link domain links.)

3. Duplicating one of these links picks up the new subdomain, but the url that gets created is http, not https

A: At present, the Branch API creates Branch links for custom domains with the 'http://'scheme. This is because we are not sure if custom domains have the SSL certificate and creating links with the https:// scheme would break for such domains. Hence by default, all custom domain links are created using the http:// scheme. There is no direct way to create links using the https:// scheme using the Branch API, the only way you can do it is by manually changing the scheme from 'http' to 'https://'.

4. Why isn't Branch tracking link clicks for the x.y.z links that I set up as x-y-z? This aliasing works fine, and seemed to be tracking clicks fine in test.

I believe, the issue here has nothing to do with your custom domain but is maybe related to a key mismatch. You mention that the link clicks were tracked in the test version of the App, which leads me to believe that your app is still using the Branch key from the test version (key format: key_test_XXXXXXXXXXXXXXX). Please ensure that your App is using the correct key. The simple test for this: When you click on the Branch link, you get the link parameters in your app and the link parameters contain <string name="example_string">Line 1\Line2\Line n</string> . If so, the link click will be tracked on Branch's end.

If you still continue to face issues, you could write to <TextView android:id="@+id/textView" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/example_string" /> and our team would be more than happy to help you resolve the issue.