Google Analytics(分析)唯一事件不正确

本文介绍了Google Analytics(分析)唯一事件不正确的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们有一个Google Analytics(分析)帐户，用于跟踪某些文件的下载.例如，当您使用事件标签"(用户)作为主要字段，并使用事件操作"(文件名)作为辅助字段来创建报告时，GA会说唯一事件的数量为168.将这些数字相加时但是，在唯一事件"列中，它们总计为322.将表导出为CSV文件并在Excel中查看也将获得322.

We have a Google Analytics account set up to track downloads on certain files. When you create a report with, for example, Event Label (user) as the primary field, and Event Action (file name) as the secondary field, GA will say that the number of unique events is 168. When you add up the numbers in the unique events column, however, they add up to 322. Exporting the table as a CSV file and viewing it in Excel will also give you 322.

我还应该补充一点，表中有270行，因此对于168个唯一事件，这意味着某些用户/文件组合将具有0个唯一事件，这没有任何意义.

I should also add that there are 270 rows in the table, so for there to be 168 unique events, that would mean some user/file combinations would have 0 unique events, which doesn't make any sense.

有人能说明为什么会这样吗?

Can anybody shed some light on why this is happening?

推荐答案

与 Unique Events 指标有很多混淆. GA并未计算事件的类别/操作/标签的唯一组合的发生次数，而是在统计报告中包含的每个维度的唯一组合！ 最后，该指标现在已被弃用，并重命名为唯一事件(旧版). 取而代之的是，我们获得了一个真实的唯一事件(新)指标，其行为与预期的一样.

There is a lot of confusion with Unique Events metric. Instead of counting a number of times an event with unique combination of category/action/label happened, GA was counting unique combination of every dimension included in the report! Finally that metric is deprecated now and renamed to Unique Events (legacy). Instead we get a real Unique Events (new) metric which behave like expected.

我的博客文章中有更多解释 www.internetrix.au/blog/google-analytics-unique-events-are-dead-long-live-unique-events/

More explanation in my blog post www.internetrix.au/blog/google-analytics-unique-events-are-dead-long-live-unique-events/