동시 요청 수는 동시에 실행되는 요청 수로 측정됩니다. 요청 동시 실행을 줄이려면 이전 요청이 완료될 때까지 기다린 후에 추가 요청을 전송하세요.
서버 오류는 500 및 503 코드입니다. 서버 오류 할당량은 요청으로 인해 서버 오류가 발생한 경우에만 청구됩니다. 프로젝트 및 속성 쌍의 서버 오류 할당량이 소진되면 프로젝트에서 속성에 대한 모든 요청이 차단됩니다.
각 요청은 시간당 속성별 토큰과 시간당 속성별 프로젝트당 토큰의 할당량을 모두 사용합니다. 즉, '시간당 속성별 토큰' 할당량이 '시간당 속성별 프로젝트당 토큰' 할당량보다 먼저 소진되려면 하나의 속성에 3개 이상의 프로젝트가 액세스해야 합니다.
속성은 시간당 기준점을 초과할 수 있는 요청을 120회 허용합니다. userAgeBracket, userGender, brandingInterest, audienceId, audienceName 측정기준은 잠재적으로 임곗값이 적용될 수 있습니다. 보고서를 조회하는 사용자가 개별 사용자의 인구통계 또는 관심분야를 유추하지 못하게 하는 데이터 기준이 적용됩니다.
속성 토큰 할당량
토큰은 요청의 복잡도에 따라 각 요청과 함께 계산됩니다.
대부분의 요청에는 10개 이하의 토큰이 청구됩니다. 요청에서 다량의 할당량 토큰이 사용되는 경우 다음 요소가 원인인 경우가 많습니다.
행이 많음
열이 많은 경우
복잡한 필터 기준
긴 기간
각 API 요청에서 요청 본문에 "returnPropertyQuota": true를 지정하여 현재 속성 할당량 토큰 상태를 반환할 수 있습니다. 이 상태에는 이 요청에서 사용한 금액과 각 할당량 그룹의 남은 금액이 모두 포함됩니다. 예를 들어 RunReportRequest에서 이 매개변수를 지정할 수 있습니다.
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eThe Google Analytics Data API uses a quota system to limit the number of requests and resources consumed, categorized into Core, Realtime, and Funnel based on the API methods used.\u003c/p\u003e\n"],["\u003cp\u003eEach request to the API consumes tokens and is subject to daily and hourly quotas, with separate limits for standard and Analytics 360 properties.\u003c/p\u003e\n"],["\u003cp\u003eExceeding any quota results in request failures with error messages, emphasizing the importance of managing request concurrency and minimizing server errors.\u003c/p\u003e\n"],["\u003cp\u003eThe token cost for each request varies depending on the request complexity, with factors like data volume, filtering, and date ranges significantly influencing token consumption.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can monitor quota usage by including \u003ccode\u003e"returnPropertyQuota": true\u003c/code\u003e in the request body to receive the current token status and remaining quota.\u003c/p\u003e\n"]]],["API requests consume quotas, categorized as Core, Realtime, or Funnel. Each request verifies and consumes quota within its category, failing if exhausted. Quotas include tokens per property, project, and concurrent requests, with different limits for standard and Analytics 360 properties. Server errors also have quotas, blocking requests upon exhaustion. Token consumption varies based on request complexity (rows, columns, filters, date ranges). Each request can check its quota status. Potentially thresholded data can also affect the result of the request.\n"],null,["# Data API limits and quotas\n\nThe following limits and quotas apply to the Data API.\n\nQuota Categories\n----------------\n\nThe Data API has three request quota categories: Core,\nRealtime, and Funnel. API requests to Core methods charge Core quotas. API\nrequests to Realtime methods charge Realtime quotas. Each request consumes only\none kind of quota.\n\n| Quota Category | API Methods |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Core | [runReport](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runReport), [runPivotReport](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runPivotReport), [batchRunReports](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/batchRunReports), [batchRunPivotReports](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/batchRunPivotReports), [runAccessReport](/analytics/devguides/config/admin/v1/rest/v1alpha/properties/runAccessReport), [getMetadata](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/getMetadata), [checkCompatibility](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/checkCompatibility), [createAudienceExports](/analytics/devguides/reporting/data/v1/rest/v1beta/properties.audienceExports/create) |\n| Realtime | [runRealtimeReport](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runRealtimeReport) |\n| Funnel | [runFunnelReport](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties/runFunnelReport) |\n\nAnalytics Property Quotas\n-------------------------\n\nAll requests consume property quotas.\n\n| Quota Name | Standard Property Limit | Analytics 360 Property Limit |\n|----------------------------------------------------------|-------------------------|------------------------------|\n| Core Tokens Per Property Per Day | 200,000 | 2,000,000 |\n| Core Tokens Per Property Per Hour | 40,000 | 400,000 |\n| Core Tokens Per Project Per Property Per Hour | 14,000 | 140,000 |\n| Core Concurrent Requests Per Property | 10 | 50 |\n| Core Server Errors Per Project Per Property Per Hour | 10 | 50 |\n| Realtime Tokens Per Property Per Day | 200,000 | 2,000,000 |\n| Realtime Tokens Per Property Per Hour | 40,000 | 400,000 |\n| Realtime Tokens Per Project Per Property Per Hour | 14,000 | 140,000 |\n| Realtime Concurrent Requests Per Property | 10 | 50 |\n| Realtime Server Errors Per Project Per Property Per Hour | 10 | 50 |\n| Funnel Tokens Per Property Per Day | 200,000 | 2,000,000 |\n| Funnel Tokens Per Property Per Hour | 40,000 | 400,000 |\n| Funnel Tokens Per Project Per Property Per Hour | 14,000 | 140,000 |\n| Funnel Concurrent Requests Per Property | 10 | 50 |\n| Funnel Server Errors Per Project Per Property Per Hour | 10 | 50 |\n\n- Concurrent requests are measured by the number of requests being simultaneously executed. To reduce your request concurrency, wait for previous requests to complete before sending additional requests.\n- Server Errors are 500 and 503 codes. Server Errors quotas are only charged when a request results in a server error. When the Server Errors quotas are exhausted for a project and property pair, all requests to the property from the project are blocked.\n- Each request consumes quota for both Tokens Per Property Per Hour and Tokens Per Project Per Property Per Hour. This means that one property must be accessed by more than 3 projects before the \"Tokens Per Property Per Hour\" quota could be exhausted before the \"Tokens Per Project Per Property Per Hour\" quota.\n\n| **Note:** All daily quotas are refreshed at midnight Pacific Standard Time. All hourly quotas are refreshed within an hour but not necessarily on the whole hour boundaries.\n\nProperties are allowed 120 potentially thresholded requests per hour. The\ndimensions `userAgeBracket`, `userGender`, `brandingInterest`, `audienceId`, and\n`audienceName` are potentially thresholded. Thresholds are applied to prevent\nanyone viewing a report from inferring the demographics or interests of\nindividual users.\n\n### Property Tokens Quota\n\nTokens are calculated with each request depending upon the request's complexity.\nMost requests will charge 10 or fewer tokens. When a large number\nof quota tokens are consumed by a request, these factors are often responsible:\n\n- Large number of rows\n- Large number of columns\n- Complex filter criteria\n- Long date range\n\nWith each API request, you can specify `\"returnPropertyQuota\": true` in the\nrequest body to return the current property quota tokens status. This status\ncontains both the amount consumed by this request and the amount remaining for\neach quota group. For example, consider specifying this parameter in\n[`RunReportRequest`](/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runReport#request-body)."]]
