Google analytics 用于后期跟踪的GA360访问ID上的平均分析功能

希望从我们的GA 360出口产品中获得visitid的平均延迟跟踪

设置以下查询，但出现以下错误，我不确定原因，因为所有这些都是聚合函数：SELECT list expression references hits.latencyTracking.serverResponseTime，它在[3:5]处既没有分组也没有聚合

---

您编写查询的方式-AVG不仅仅是，而是

为了使其工作，您可以删除，这样平均值将真正成为这里对应于分组的聚合函数

select 
TIMESTAMP_SECONDS(visitStartTime) as visitStartTime,
AVG(hits.latencyTracking.serverResponseTime) as avgServerResponseTime,
AVG(hits.latencyTracking.serverConnectionTime) as avgServerConnectionTime,
AVG(hits.latencyTracking.domInteractiveTime) as avgdomInteractiveTime,
AVG(hits.latencyTracking.pageLoadTime) as avgpageLoadTime
from `xxx.xxx.ga_sessions_2018*`,
UNNEST(hits) AS hits
where hits.latencyTracking.serverResponseTime is not null
group by visitStartTime   

将windows和GroupBy结合使用可能会令人困惑。 在您的情况下，这甚至不是必需的，平坦化也不是必需的-您可以编写简单的子查询来获取每个会话的编号：

选择 时间戳\u SECONDSvisitStartTime作为visitStartTime， 选择AVGlatencyTracking.serverResponseTime 来自t.hits 其中latencyTracking.serverResponseTime作为avgServerResponseTime不为NULL， 选择AVGlatencyTracking.serverConnectionTime 来自t.hits 其中latencyTracking.serverConnectionTime与avgServerConnectionTime一样不为NULL， 选择AVGlatencyTracking.domInteractiveTime 来自t.hits 其中latencyTracking.domInteractiveTime作为AvgDominInteractiveTime不为NULL， 选择AVGlatencyTracking.pageLoadTime 来自t.hits 其中latencyTracking.pageLoadTime与avgpageLoadTime一样不为NULL 摘自'xxx.xxx.ga_sessions_2018*` 它也不涉及分组，这使它更快

select 
TIMESTAMP_SECONDS(visitStartTime) as visitStartTime,
AVG(hits.latencyTracking.serverResponseTime) as avgServerResponseTime,
AVG(hits.latencyTracking.serverConnectionTime) as avgServerConnectionTime,
AVG(hits.latencyTracking.domInteractiveTime) as avgdomInteractiveTime,
AVG(hits.latencyTracking.pageLoadTime) as avgpageLoadTime
from `xxx.xxx.ga_sessions_2018*`,
UNNEST(hits) AS hits
where hits.latencyTracking.serverResponseTime is not null
group by visitStartTime