直接使用 Google Analytics Measurement Protocol API 的速率限制是多少? [英] What is the rate limit for direct use of the Google Analytics Measurement Protocol API?
问题描述
在 Google Analytics 收集限制和配额的文档中
它给出了由各种 Google 提供的库实现的速率限制.我似乎找不到直接发布到测量协议的用户的已发布速率限制 (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 的调用，每次调用之间有 1 秒的睡眠时间.
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 万次点击
10 million hits per month per property
测量协议
启用通用分析
这适用于 analytics.js、Android iOS SDK 和 Measurement协议.
This applies to analytics.js, Android iOS SDK, and the Measurement Protocol.
每位用户每天 200,000 次点击每个会话 500 次点击不包括电子商务(项目和交易命中类型).如果你超过任何一个这些限制，不会为该会话处理额外的命中/天，分别.这些限制也适用于 Premium.
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.
现在我同意它没有具体说明测量协议的每秒速率，但上面的一个使用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 的回复
测量协议不做任何类型的速率限制或通过 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.
正如 Linda 在她的回答中指出的那样，有各种限制和配额由后端强加，但这些是在处理时完成的，而不是收集时间.
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屋！
