Suite | All plans |
Support with | Guide all plans |
您可以在 Guide 中,或使用 Google Analytics(分析)或 Zendesk Explore 报告 Zendesk Guide 数据。本文解答了使用这三个工具报告数据有何差异的常见问题。
本文章包含以下主题:
为什么 Explore 中的 Guide 数据与 Google Analytics(分析)中的数据不一致?
Google Analytics(分析)是一个通用工具,用于跟踪用户在网站上的活动。因此,它提供的功能比 Guide 与 Explore 的整合要广泛得多。
但是,与 Guide 和 Explore 的整合相比,Google Analytics(分析)提供的背景信息较少。例如,Google Analytics(分析)不会自动区分专员和终端用户的页面查看数。
这两个工具在设计时考虑的目标不同,因此实施方式也不同。此外,Google Analytics(分析)是用户可配置的,这意味着其行为因个人安装的版本而异。
我们能解决这两个工具的差异问题吗?
一般情况下不能,因为我们无法了解 Google Analytics(分析)是如何实施的。我们只能根据为 Guide 与 Explore 整合提供支持的类似机制,推测其跟踪和聚合功能的行为。
为什么已删除或取消发布的文章仍有查看数?
文章在删除或取消发布后仍然显示被查看可能有多种原因。
-
最常见的情况是,已删除或取消发布的文章有多个翻译版,但只有一个翻译版被删除或取消发布,这种情况下就会获得查看数。例如,如果您同时发布了一篇文章的法语和英语翻译版,但仅删除了英语翻译版,则法语翻译版可能仍会获得查看数。要排除已删除或取消发布的翻译版,您可以在 Explore 中按语言进行筛选。
-
Explore 也可以记录已存档文章的查看数,因为 Explore 依靠用户的网络浏览器来记录活动。在正常情况下,导致 Explore 跟踪查看数的事件顺序如下:
- 用户在其浏览器中访问文章 URL。
- 帮助中心服务器返回文章内容以及一些代码,要求用户的浏览器将查看数记录到我们的活动跟踪系统。
- 用户的浏览器会向我们的活动跟踪系统发送一个请求,其中包含帮助中心提供的信息(例如是哪篇文章或哪个用户查看了该文章)。
- 我们的活动跟踪系统接收来自用户浏览器的请求并记录查看数。
在大多数情况下,第 3 步几乎是在第 2 步之后立即进行的,因此用户的浏览器只需几毫秒即可发出请求。还是,由于浏览器的行为不是我们控制的,我们无法确定完成第 3 步需要多长时间。
例如,在第 2 步和第 3 步之间,如果用户的网络连接发生中断,之后又重新连接,我们可能在其重新连接后才能记录该活动。再例如用户的浏览器发生崩溃时,第 3 步在用户重新启动浏览器后才会发生。
当我们最终收到跟踪活动日志时,我们才能确定用户确实查看了文章。但是,我们无法保证收到跟踪活动日志的时间就是实际发生查看数的时间。
为什么 Explore 中看不到 2021 年 1 月 18 日之前的知识库数据?
Explore 中的知识库数据集已于 2021 年 1 月 18 日推出。Explore 中不提供该日期之前的数据。
为什么“原生”报告和 Explore 面板之间会有差异?
我们即将把 Zendesk 专员界面中的“原生”报告面板替换为 Explore 数据集。例如,知识库数据集取代了专员界面报告部分的知识库标签。虽然我们正在设法让这两个报告工具的功能保持一致,但它们的实施方式却有所不同。因此,两者之间可能存在差异。当 Explore 中提供数据集时,应将其视为事实来源。
Explore 为什么不报告所有的文章查看数?
Explore 中的文章查看数与 Google Analytics(分析)中的文章查看数不一致可能有多种原因:
- 广告拦截器可能会阻止 Explore 记录文章查看数。
- Explore 没有记录草稿、已存档和已删除文章的查看数。
3 条评论
Adam Szakacs
We are also seeing too much discrepancies with simple things like article views (or page load in google analytics) - we even went as far as writing our own client side tracker as we also had issues with the lack of configurability (for our needs) in google analytics…numbers are still too far apart unfortunately…
0
Rebecca
We also really need more information or support as to the Knowledge Base (aka Guide, or Help Center) metrics or analytics. Currently we are seeing huge differences between what Zendesk Explore reports, vs. other analytics tools. There is not currently a clear way to explain these differences or compare to other tools because we don't know how or what exactly Zendesk is calculating. Our org has started to lose confidence in Explore data due to continual questioning without answers as to discrepancies, so more information would be super helpful to try and navigate this.
0
CJ Johnson
"We are replacing “native” reporting dashboards in the Zendesk agent interface with Explore datasets. For example, the Knowledge Base dataset replaces the Knowledge Base tab in the reporting section of the agent interface. While we aim to provide feature parity between the two reporting tools, they are implemented differently. As a result, discrepancies might exist. Once a dataset is available in Explore, it should be considered the source of truth."
This doesn't really make any sense from a reporting perspective. I'm seeing massive differences in the numbers and the answer being "well they just aren't quite the same" doesn't really cut it when we're talking about 20% +/- differences in the number of visitors (and we're talking 4 digits and higher visitor counts only).
As a customer, I need to be able to trust the accuracy of the data and being told to just "accept this new version in Explore as the source of truth" with absolutely no explanations as to what exactly you're doing differently, doesn't give me any confidence in either reporting methodology. Can you tell us exactly why these are coming up so wildly differently? Can you provide some transparency here about how you're changing your collection methods and why the results are so drastically different?
5
登录再写评论。