Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Google Ads resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
GoogleAdsService.Search mendukung
penomoran halaman dalam ukuran halaman tetap 10.000 baris. Kumpulan hasil kueri dibagi
menjadi beberapa respons, yang masing-masing berisi 10.000 objek.
Jika akun Anda berisi 50.000 kata kunci, set hasil akan berisi 10.000 objek
GoogleAdsRow dalam respons pertama,
bersama dengan
next_page_token.
Untuk mengambil 10.000 baris berikutnya, kirim permintaan lagi, tetapi perbarui
page_token permintaan ke
next_page_token respons.
Perhatikan bahwa
next_page_token
tidak diisi dalam respons yang berisi kumpulan baris terakhir.
Library klien kami menangani penomoran halaman secara otomatis. Anda hanya perlu melakukan iterasi
melalui baris respons. Setelah semua baris di halaman saat ini ditampilkan, library klien akan otomatis mengambil halaman baris baru atas nama Anda hingga seluruh set data diambil. Jika menggunakan REST, bukan gRPC, Anda harus membuat permintaan secara eksplisit untuk setiap halaman baru.
Google Ads API secara internal menyimpan seluruh set data dalam cache, sehingga permintaan berikutnya lebih cepat daripada permintaan awal.
Kueri Anda harus tetap sama persis dalam permintaan berikutnya untuk memanfaatkan
data yang di-cache. Permintaan tidak akan berkontribusi terhadap kuota Anda, terutama untuk tingkat Akses Dasar. Jika
kueri berbeda dan dikirim bersama dengan token halaman yang sama, error akan
ditampilkan.
[null,null,["Terakhir diperbarui pada 2025-08-27 UTC."],[[["\u003cp\u003e\u003ccode\u003eGoogleAdsService.Search\u003c/code\u003e returns data in fixed pages of 10,000 rows, requiring multiple requests to retrieve larger datasets.\u003c/p\u003e\n"],["\u003cp\u003eTo retrieve subsequent pages, use the \u003ccode\u003enext_page_token\u003c/code\u003e from the previous response in your next request's \u003ccode\u003epage_token\u003c/code\u003e field.\u003c/p\u003e\n"],["\u003cp\u003eClient libraries automate paging, but when using REST, you must manually request each page.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Ads API caches the entire dataset, making subsequent requests with the same query faster and not counted towards quota.\u003c/p\u003e\n"],["\u003cp\u003eFor custom pagination scenarios, it's recommended to retrieve and store results locally, implementing your own pagination logic.\u003c/p\u003e\n"]]],[],null,["# Paging through results\n\n| **Note:** The `page_size` field was removed in v19 of the Google Ads API. See the [announcement](https://ads-developers.googleblog.com/2024/07/upcoming-changes-to-page-size-in-google.html). The `page_size` field has a default value of 10,000. Don't attempt to set the `page_size` value, as that will throw an error.\n\n[`GoogleAdsService.Search`](/google-ads/api/reference/rpc/v21/GoogleAdsService/Search) supports\npaging in fixed page sizes of 10,000 rows. The result set of the query is split\ninto multiple responses, each of which 10,000 objects.\n\nAs an example, consider the following query: \n\n SELECT\n ad_group.id,\n ad_group_criterion.type,\n ad_group_criterion.criterion_id,\n ad_group_criterion.keyword.text,\n ad_group_criterion.keyword.match_type\n FROM ad_group_criterion\n WHERE ad_group_criterion.type = KEYWORD\n\nIf your account contains 50,000 keywords, the result set will contain 10,000\n[`GoogleAdsRow`](/google-ads/api/reference/rpc/v21/GoogleAdsRow) objects in the first response,\nalong with a\n[`next_page_token`](/google-ads/api/reference/rpc/v21/SearchGoogleAdsResponse#next_page_token).\n\nTo retrieve the next 10,000 rows, send the request again, but update the\nrequest's `page_token` to the response's\n[`next_page_token`](/google-ads/api/reference/rpc/v21/SearchGoogleAdsResponse#next_page_token).\nNote that\n[`next_page_token`](/google-ads/api/reference/rpc/v21/SearchGoogleAdsResponse#next_page_token)\nis not populated in the response that contains the last batch of rows.\n\nOur client libraries handle paging automatically. You only have to iterate\nthrough the rows of the response. When all rows in the current page have\nbeen returned, the client library fetches a new page of rows automatically on\nyour behalf until the entire dataset is retrieved. If using REST instead\nof gRPC, you must explicitly make a request for each new page.\n\nThe Google Ads API internally caches the entire dataset, so subsequent requests are\nfaster than the initial one.\n\nYour query must remain exactly the same in subsequent requests to take advantage\nof the cached data. The requests won't contribute towards your quota,\nparticularly for [Basic Access level](/google-ads/api/docs/access-levels#basic_access). If\nthe query differs and is sent along with the same page token, an error is\nreturned.\n| **Key Point:** If you need manual paging, such as for custom web pagination, we recommend that you retrieve and store the results locally, such as in a database, and build your own pagination logic."]]
