Google分析测量协议会话超时和查询时间限制 [英] Google analytics measurement protocol session timeout and query time limits

问题描述

假设我们的目标是设置使用测量协议进行跟踪的离线事件，但我们的唯一限制就是我们需要每天发布一次事件Feed，并通过GA UI提供正确的标准报告进行GA设置。

p>

GA限制： b
$ b

• 会话超时限制为4小时;
  
• 发生报告的时间与发送时间之间的最大时间增量 - qt参数也限制为4小时;

测试用例：
$ b 0 。会话超时限制设置为最多4小时。

1. 创建第一个会话的第一个会话。


2. 他需要10分钟才能获得拨打电话所需的信息。


3. 用户在上午9点10分拨打电话和电话订购。独特的非个人身份识别码与呼叫一起传递给CRM，并保存在GA维和uid中。


4. 在下午6点，呼叫报告CRM生成呼叫报告，并使用测量协议事件上传HTTP请求将其传递给GA。


5. 在下午6点，呼叫报告CRM生成交易报告并传递电话订单值&使用测量协议事务请求将数字转换为GA。

问题：

1）测试用例第5步描述的请求中的qt参数是否需要等于：

1.1）可能的最大值 - 4小时（因为否则可能无法按照此规则处理超过四小时的值可能导致点击未被处理。）
1.2）实际值 - 8小时& 50分钟。

2）1.1会导致第一次会话超时吗？

3）1.1是否会导致第二个会话被创建，即：

• 开始时间等于下午4点& 50分钟;
  
• 结束时间等于4 p.m& 50分钟;
  
• user-agent by-default等于测量协议HTTP请求中使用的值; 默认情况下为
  
• 没有关闭，所以如果第二次用户访问是在下午4点，这次访问的访问将被发送到这个会话;

4）第二个会话会影响标准报表参数的值，例如：
$ b

• 平均会话长度;
  
• 平均跳出率&退出率;
  
• 每个会话的平均页面数量;

5）第二次会话是否会影响流量报告或任何其他Google报告的错误？

它应该等于可能的最大值或0，如果它自日期起超过4小时，则应写入

是的，如果上一次会话过期，将创建一个新的会话。

是。

流量报告基于用户而不是会话。

Let's assume we have a goal to setup offline events tracking using measurement protocol, the only limitations from our side is that we need to post the events feed once daily and have a GA setup with correct standart reports from GA UI.

GA limits:

• Session timeout limit is 4 hours;
• Max time delta between when the hit being reported occurred and the time the hit was sent - the qt parameter, is also limited to 4 hours;

Test case:

"0". Session timeout limit is set to the max 4 hours.

1. User visits site at 9 a.m first session is created.
2. It takes him 10 minutes to get the info needed for making a call.
3. User makes a call and an phone order at 9:10 a.m. Unique, non personally identifiable code is passed with the call to CRM and saved in GA dimension and uid.
4. At 6 p.m call-report CRM generates the call-report and passes it to GA using measurement protocol event upload HTTP requests.
5. At 6 p.m call-report CRM generates the transaction-report and passes the phone order value & number to GA using measurement protocol transaction requests.

Questions:

1) Does the qt parameter in request described on the 5'th step of test case needs to be equal to:

1.1) Possible maximum value - 4 hours (because otherwise it may be not processed by this rule "Values greater than four hours may lead to hits not being processed.") 1.2) Actual value - 8 hours & 50 minutes.

2) Does 1.1 result in a first session timeout?

3) Does 1.1 result in a second session being created, which:

• start-time is equal to 4 p.m & 50 minutes;
• end time is equal to 4 p.m & 50 minutes;
• user-agent by-default is equal to the value which has been used in measurement protocol HTTP request;
• by-default is not closed, so if a second user visit is on 4 p.m this visit's hits will be sent to this session;

4) Does this second session affect the value of standart report's parameters, such as:

• average session length;
• average bounce rate & exit rate;
• average pages per session;

5) Does the second session affect the flow reports or any other Google reports making in incorrect?

解决方案

1. It should be equal to possible max value, or 0, if it's more then 4 hours since the date, and you should write the actual date as a custom field and process the data later.
2. Yes, a new session will be created, if the last session expired.
3. Somewhat.
4. Yes.
5. Flow reports are based on users not sessions.

这篇关于Google分析测量协议会话超时和查询时间限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！