Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Batas dan kuota berikut berlaku untuk Data API.
Kategori Kuota
Data API memiliki tiga kategori kuota permintaan: Core, Real-Time, dan Funnel. Permintaan API ke metode Core menagih kuota Core. Permintaan API ke metode Realtime menagih kuota Realtime. Setiap permintaan hanya menggunakan
satu jenis kuota.
Core Server Errors Per Project Per Property Per Hour
10
50
Token Realtime Per Properti Per Hari
200.000
2.000.000
Token Realtime Per Properti Per Jam
40.000
400.000
Token Real-Time Per Project Per Property Per Hour
14.000
140.000
Permintaan Serentak Real-Time Per Properti
10
50
Realtime Server Errors Per Project Per Property Per Hour
10
50
Token Funnel Per Properti Per Hari
200.000
2.000.000
Token Funnel Per Properti Per Jam
40.000
400.000
Token Funnel Per Project Per Property Per Hour
14.000
140.000
Funnel Concurrent Requests Per Property
10
50
Error Server Funnel Per Project Per Property Per Hour
10
50
Permintaan serentak diukur berdasarkan jumlah permintaan yang
dieksekusi secara serentak. Untuk mengurangi konkurensi permintaan, tunggu
permintaan sebelumnya selesai sebelum mengirim permintaan tambahan.
Error Server adalah kode 500 dan 503. Kuota Error Server hanya ditagih saat permintaan menghasilkan error server. Jika kuota Server Errors
habis untuk pasangan project dan properti, semua permintaan ke properti dari
project akan diblokir.
Setiap permintaan menggunakan kuota untuk Token Per Properti Per Jam dan Token Per Project Per Properti Per Jam. Artinya, satu properti harus diakses oleh lebih dari 3 project sebelum kuota "Token Per Properti Per Jam" dapat habis sebelum kuota "Token Per Project Per Properti Per Jam".
Properti diizinkan untuk melakukan 120 permintaan yang berpotensi mencapai nilai minimum per jam. Dimensi
userAgeBracket, userGender, brandingInterest, audienceId, dan
audienceName berpotensi memiliki nilai minimum. Batas diterapkan agar
siapa pun yang melihat laporan tidak dapat menyimpulkan demografi atau minat
setiap pengguna.
Kuota Token Properti
Token dihitung dengan setiap permintaan, bergantung pada kompleksitas permintaan.
Sebagian besar permintaan akan mengenakan biaya 10 token atau kurang. Jika token kuota dalam jumlah besar
digunakan oleh permintaan, faktor-faktor berikut sering kali menjadi penyebabnya:
Jumlah baris yang besar
Jumlah kolom yang besar
Kriteria filter kompleks
Rentang tanggal panjang
Dengan setiap permintaan API, Anda dapat menentukan "returnPropertyQuota": true dalam
isi permintaan untuk menampilkan status token kuota properti saat ini. Status ini berisi jumlah yang digunakan oleh permintaan ini dan jumlah yang tersisa untuk setiap grup kuota. Misalnya, pertimbangkan untuk menentukan parameter ini di
RunReportRequest.
[null,null,["Terakhir diperbarui pada 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)."]]
