直接使用Google Analytics(分析)Measurement Protocol API的速率限制是多少? [英] What is the rate limit for direct use of the Google Analytics Measurement Protocol API?
问题描述
在 Google Analytics(分析)收集限制和配额的文档中
它给出了由Google提供的各种库实现的rate limits.我似乎找不到直接发布到测量协议的用户的发布速率限制( https://www.google-analytics.com/collect ).
It gives the rate limits that are implemented by the various Google-provided libraries. I can't seem to find a published rate limit for users that are POSTing directly to measurement protocol (https://www.google-analytics.com/collect).
有一个，如果是，那是什么?
Is there one and if so what is it?
2015年7月10日编辑-
Edit on 10 July 2015 -
一些评论者要求提供我正在发送的数据类型的示例.
A few commenters asked for an example of the kind of data I am sending in.
使用一系列对wget的调用，每个调用之间的睡眠时间为一秒钟.
Using a series of calls to wget with a sleep of one second between each call.
以下是删除应用名称和跟踪代码的示例:
Here is an example with the app name and tracking code removed:
wget -nv --post-data 'ul=en&qt=7150000&av=0.0.1&ea=PLET&v=1&tid=<my_tracking_code>&ec=Move+to+Object&cid=1434738538-738-654031&an=<my_app_name>&t=event' -O /dev/null 'https://www.google-analytics.com/collect'
我尝试将这些查询发送到/debug端点，并且所有这些查询均有效.我的第一次上传按预期工作，报告看起来不错.随后将同一数据集上传到不同的GA属性的结果则好坏参半.有时报表中没有数据.有时，部分数据会出现在报告中.在上传过程中，实时报告始终显示活动.
I've tried sending these queries to the /debug endpoint and all of them are valid. My first upload worked as expected and reports looked good. Subsequent uploads of the same data set to different GA properties have had mixed results. Sometimes no data appears in reports. Sometimes partial data appears in reports. During upload, realtime reports always show activity, though.
推荐答案
直接来自文档 Google Analytics(分析)集合限制和配额
这些限制适用于网络媒体资源/媒体资源/跟踪ID.
These limits apply to the Web Property / Property / Tracking ID.
1000万次点击
测量协议
已启用通用分析
Universal Analytics Enabled
这适用于analytics.js，Android iOS SDK和 Measurement 协议.
This applies to analytics.js, Android iOS SDK, and the Measurement Protocol.
200,000次点击每个会话500次点击(不包括) 电子商务(项目和交易匹配类型).如果您经过任何一个 这些限制，将不会为该会话处理其他匹配/ 分别.这些限制也适用于高级版.
200,000 hits per user per day 500 hits per session not including ecommerce (item and transaction hit types). If you go over either of these limits, additional hits will not be processed for that session / day, respectively. These limits apply to Premium as well.
现在，我同意它并没有具体说明测量协议的per second it rate，而是将上面的一个测量值与analytics.js一起转储了，所以我认为我们可以假定它为
Now I agree it doesn't specifically state the per second it rate for measurement protocol but the above one dumped Measurement in with analytics.js so I think we can assume its
analytics.js:
analytics.js:
每个analytics.js跟踪器对象均以20个匹配项开头 以每秒2次命中的速度补充.适用于所有匹配 用于电子商务(项目或交易).
Each analytics.js tracker object starts with 20 hits that are replenished at a rate of 2 hit per second. Applies to all hits except for ecommerce (item or transaction).
但是为了确保我向开发团队发送电子邮件，他们应该更清楚地指出每秒测量协议的速率在哪里.收到他们的回信后，我会在这里重新发布
But just to make sure I am sending an email off to the development team they should make it more clear where the per second rate of the measurement protocol lies. I will repost here when I hear from them
来自Google的回复
Measurement Protocol不执行任何类型的速率限制或 通过IP地址或跟踪ID或类似名称进行配额分配.然而， 大多数客户端库都以某种形式进行速率限制.
The Measurement Protocol does not do any kind of rate limiting or quota-ing by IP address or tracking ID or anything like that. However, most of the client libraries do rate limit in some form or another.
正如琳达在回答中指出的那样，存在各种限制和配额 由后端强加，但是这些是在处理时完成的，而不是 收集时间.
As Linda points out in her answer, there are various limits and quotas imposed by the back end, but those are done at processing time, not collection time.
结论
通过测量协议发送数据没有限制.但是在处理数据时可能会受到限制.我认为他们可能指的是每月最多200万次点击.似乎是库对可发送数据的速度施加了限制，而不是直接对测量协议进行限制.
There is no limit to sending data through the measurement protocol. But when the data is processed limit may be applied. I think they may be referring to the max 2 million hits a month. It seems it's the libraries that apply limits on how fast you can send data not the measurement protocol directly.
这篇关于直接使用Google Analytics(分析)Measurement Protocol API的速率限制是多少?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
