试用 Google Analytics 的 MCP 服务器。从
GitHub 安装,并参阅
公告了解详情。
PropertyQuota
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
此 Google Analytics 媒体资源的所有配额的当前状态。如果某个媒体资源的任何配额用尽,则针对该媒体资源的所有请求都会返回“资源耗尽”错误。
字段 |
tokensPerDay |
object (QuotaStatus )
标准 Google Analytics 媒体资源每天最多可使用 20 万个令牌;Analytics 360 媒体资源每天最多可使用 200 万个令牌。大部分请求消耗的令牌数都少于 10 个。
|
tokensPerHour |
object (QuotaStatus )
标准 Google Analytics 媒体资源每小时最多可使用 4 万个令牌;Analytics 360 媒体资源每小时最多可使用 40 万个令牌。一个 API 请求会消耗一个令牌数量,该数量会从所有小时配额、每日配额和每个项目的小时配额中扣除。
|
concurrentRequests |
object (QuotaStatus )
标准 Google Analytics 媒体资源最多可以发送 10 个并发请求;Analytics 360 媒体资源最多可以使用 50 个并发请求。
|
serverErrorsPerProjectPerHour |
object (QuotaStatus )
标准版 Google Analytics 媒体资源和云项目对每小时最多可以有 10 个服务器错误;Analytics 360 媒体资源和云项目对每小时最多可以有 50 个服务器错误。
|
potentiallyThresholdedRequestsPerHour |
object (QuotaStatus )
Google Analytics 媒体资源每小时最多可以发送 120 个可能包含阈值维度的请求。在批量请求中,如果报告请求包含可能达到阈值的维度,则系统会单独统计每个报告请求的此配额。
|
tokensPerProjectPerHour |
object (QuotaStatus )
Google Analytics 媒体资源每小时最多可使用其令牌的 35%。也就是说,标准 Google Analytics 媒体资源每个项目每小时最多可使用 14,000 个令牌,Analytics 360 媒体资源每个项目每小时最多可使用 14 万个令牌。一个 API 请求会消耗一个令牌数量,该数量会从所有小时配额、每日配额和每个项目的小时配额中扣除。
|
QuotaStatus
JSON 表示法 |
{
"consumed": integer,
"remaining": integer
} |
字段 |
consumed |
integer
此请求消耗的配额。
|
remaining |
integer
此请求后剩余的配额。
|
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThis document details the current quota status for Google Analytics properties, including daily and hourly token limits, concurrent request limits, and error limits.\u003c/p\u003e\n"],["\u003cp\u003eStandard Analytics properties have lower quotas compared to Analytics 360 properties across various metrics, such as daily tokens and concurrent requests.\u003c/p\u003e\n"],["\u003cp\u003eIf any specific quota is exhausted for a property, any requests to that property will result in Resource Exhausted errors.\u003c/p\u003e\n"],["\u003cp\u003eQuota usage is tracked across various dimensions, including daily, hourly, per-project hourly, and concurrent requests, ensuring fair usage and preventing abuse.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eQuotaStatus\u003c/code\u003e provides information about the consumed and remaining quota for a specific quota group, enabling users to monitor their usage.\u003c/p\u003e\n"]]],["The content outlines the quota system for Analytics Properties, detailing six quota categories: tokens per day, tokens per hour, concurrent requests, server errors per project per hour, potentially thresholded requests per hour, and tokens per project per hour. Each quota has specific limits for Standard and Analytics 360 Properties. Quota consumption is tracked, showing consumed and remaining amounts for each request. If quotas are exceeded, the system returns \"Resource Exhausted\" errors.\n"],null,["# PropertyQuota\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n- [QuotaStatus](#QuotaStatus)\n - [JSON representation](#QuotaStatus.SCHEMA_REPRESENTATION)\n\nCurrent state of all quotas for this Analytics Property. If any quota for a property is exhausted, all requests to that property will return Resource Exhausted errors.\n\n| JSON representation |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ``` { \"tokensPerDay\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) }, \"tokensPerHour\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) }, \"concurrentRequests\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) }, \"serverErrorsPerProjectPerHour\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) }, \"potentiallyThresholdedRequestsPerHour\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) }, \"tokensPerProjectPerHour\": { object (/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus) } } ``` |\n\n| Fields ||\n|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `tokens``Per``Day` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Standard Analytics Properties can use up to 200,000 tokens per day; Analytics 360 Properties can use 2,000,000 tokens per day. Most requests consume fewer than 10 tokens. |\n| `tokens``Per``Hour` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Standard Analytics Properties can use up to 40,000 tokens per hour; Analytics 360 Properties can use 400,000 tokens per hour. An API request consumes a single number of tokens, and that number is deducted from all of the hourly, daily, and per project hourly quotas. |\n| `concurrent``Requests` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Standard Analytics Properties can send up to 10 concurrent requests; Analytics 360 Properties can use up to 50 concurrent requests. |\n| `server``Errors``Per``Project``Per``Hour` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Standard Analytics Properties and cloud project pairs can have up to 10 server errors per hour; Analytics 360 Properties and cloud project pairs can have up to 50 server errors per hour. |\n| `potentially``Thresholded``Requests``Per``Hour` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Analytics Properties can send up to 120 requests with potentially thresholded dimensions per hour. In a batch request, each report request is individually counted for this quota if the request contains potentially thresholded dimensions. |\n| `tokens``Per``Project``Per``Hour` | `object (`[QuotaStatus](/analytics/devguides/reporting/data/v1/rest/v1beta/PropertyQuota#QuotaStatus)`)` Analytics Properties can use up to 35% of their tokens per project per hour. This amounts to standard Analytics Properties can use up to 14,000 tokens per project per hour, and Analytics 360 Properties can use 140,000 tokens per project per hour. An API request consumes a single number of tokens, and that number is deducted from all of the hourly, daily, and per project hourly quotas. |\n\nQuotaStatus\n-----------\n\nCurrent state for a particular quota group.\n\n| JSON representation |\n|-------------------------------------------------------|\n| ``` { \"consumed\": integer, \"remaining\": integer } ``` |\n\n| Fields ||\n|-------------|-----------------------------------------------|\n| `consumed` | `integer` Quota consumed by this request. |\n| `remaining` | `integer` Quota remaining after this request. |"]]