Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Google Ads resmi di server Komunitas Iklan dan Pengukuran Google.
Jika ada operasi dalam tugas batch yang berisi kriteria grup iklan atau
filter grup listingan grup aset, operasi dalam tugas batch akan dibagi
menjadi beberapa sub-batch saat diterima oleh server Google Ads API. Perhatikan bahwa
tidak seperti operasi standar dalam tugas batch, setiap sub-batch yang berisi operasi filter grup listingan
diperlakukan secara atomik.
Cara tugas batch yang berisi filter kelompok listingan dibagi menjadi sub-batch ditentukan oleh faktor berikut:
Jenis filter grup listingan
AdGroupCriterion atau AssetGroup yang ditargetkan oleh filter grup listingan
Semua operasi AdGroupCriterionOperation
berurutan yang berisi listing_group yang menargetkan AdGroup yang sama dikelompokkan bersama dalam sub-batch atomik (tidak ada
perilaku kegagalan sebagian).
Semua operasi berurutan lainnya dikelompokkan bersama dalam sub-batch non-atomik (perilaku kegagalan parsial).
Diagram berikut menggambarkan konsep tersebut. Setiap kotak abu-abu
mewakili tugas batch yang dikirimkan menggunakan Google Ads API. Dalam kotak abu-abu,
setiap operasi dikelompokkan berdasarkan warna untuk merepresentasikan sub-batch yang
dibuat oleh server Google Ads API. Urutan operasi di setiap kotak abu-abu
sesuai dengan urutan penambahan operasi ke
tugas batch.
Batasan
Saat menggunakan filter grup listingan dalam konteks tugas batch, batasan berikut berlaku:
Satu batch operasi AssetGroupListingGroupFilterOperation
yang berisi listing_group dan menargetkan AdGroup yang sama tidak boleh melebihi
20.000 operasi. Namun, sebaiknya jangan melebihi 10.000
operasi.
Satu batch operasi AssetGroupListingGroupFilterOperation yang menargetkan AssetGroup yang sama tidak boleh melebihi 10.000 operasi.
Jika salah satu kondisi ini dilanggar, seluruh tugas batch akan gagal.
Pemecahan masalah
Operasi filter grup listingan dalam tugas batch diproses sebagai satu transaksi,
yang dapat menyebabkan banyak operasi gagal karena sejumlah kecil operasi yang salah. Selain itu, karena cara pemrosesan operasi BatchJob, akar penyebab kegagalan dapat muncul pada indeks sebelum atau setelah kegagalan hilir.
Misalnya, saat memproses respons dari ListBatchJobResults, Anda mungkin menemukan bahwa beberapa operasi gagal dengan pesan status, Ad group is invalid due to the listing
groups it contains. Pesan ini biasanya menunjukkan bahwa operasi pada indeks ini dibatalkan karena operasi gagal pada indeks yang berbeda. Untuk
mengidentifikasi akar penyebab masalah, sebaiknya ulangi semua pesan status
di BatchJobResult—sebelum
dan setelah indeks pesan error Ad group is invalid—dalam penelusuran
informasi error tambahan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eWhen using listing group filters in batch jobs, operations are split into sub-batches based on the type of filter, target (AdGroup or AssetGroup), and order of operations.\u003c/p\u003e\n"],["\u003cp\u003eConsecutive operations targeting the same AdGroup or AssetGroup are grouped into atomic sub-batches, ensuring all operations within the sub-batch either succeed or fail together.\u003c/p\u003e\n"],["\u003cp\u003eOther consecutive operations are grouped into non-atomic sub-batches, allowing for partial failures where some operations may succeed while others fail.\u003c/p\u003e\n"],["\u003cp\u003eBatch jobs containing listing group filters have limitations on the number of operations allowed per batch to avoid failures, with recommendations to stay well below the maximum limits.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended to add operations targeting the same AdGroup or AssetGroup consecutively in a batch job for atomic processing during batch splitting.\u003c/p\u003e\n"]]],[],null,["# Listing group filters in batch jobs\n\nWhen you work with listing group filters in the context of an\n[`AdGroupCriterion.listing_group`](/google-ads/api/reference/rpc/v21/AdGroupCriterion#listing_group)\nor an\n[`AssetGroupListingGroupFilter`](/google-ads/api/reference/rpc/v21/AssetGroupListingGroupFilter),\ntake the following considerations into account when designing your integration.\n\nBatch splitting\n---------------\n\n| **Key Point:** We recommend adding `AssetGroupListingGroupFilterOperation` operations targeting the same `AssetGroup`, and `AdGroupCriterionOperation` operations containing a `listing_group` that targets the same `AdGroup`, to a batch job consecutively, so that the set of operations are treated atomically during batch splitting.\n\nIf there are any operations in a batch job that contain ad group criteria or\nasset group listing group filters, the operations in the batch job are split\ninto multiple *sub-batches* when received by the Google Ads API server. Note that\nunlike standard operations in a batch job, each sub-batch containing listing\ngroup filter operations is treated atomically.\n\nThe way in which batch jobs containing listing group filters are split into\nsub-batches is determined by the following factors:\n\n1. Type of listing group filter\n2. The `AdGroupCriterion` or `AssetGroup` the listing group filter is targeting\n3. Order of operations\n\nConsider how operations are grouped:\n\n- All consecutive [`AssetGroupListingGroupFilterOperation`](/google-ads/api/reference/rpc/v21/AssetGroupListingGroupFilterOperation) operations targeting the same [`AssetGroup`](/google-ads/api/reference/rpc/v21/AssetGroup) are grouped together in an atomic sub-batch (no partial failure behavior).\n- All consecutive [`AdGroupCriterionOperation`](/google-ads/api/reference/rpc/v21/AdGroupCriterionOperation) operations that contain a `listing_group` targeting the same [`AdGroup`](/google-ads/api/reference/rpc/v21/AdGroup) are grouped together in an atomic sub-batch (no partial failure behavior).\n- All other consecutive operations are grouped together in non-atomic sub-batches (partial failure behavior).\n\n| **Key Term:** **Consecutive** refers to the order of the operations in the batch job.\n\nThe following diagram illustrates this concept. Each of the gray boxes\nrepresents a batch job as submitted using the Google Ads API. Within the gray boxes,\nthe individual operations are grouped by color to represent the sub-batches that\nthe Google Ads API server creates. The order of the operations in each of the gray\nboxes corresponds to the order in which the operations would have been added to\nthe batch job.\n\nLimitations\n-----------\n\nWhen working with listing group filters in the context of batch jobs, the\nfollowing limitations apply:\n\n- A single batch of `AssetGroupListingGroupFilterOperation` operations containing a `listing_group` and targeting the same `AdGroup` cannot exceed 20,000 operations in length. However, it is recommended not to exceed 10,000 operations.\n- A single batch of `AssetGroupListingGroupFilterOperation` operations targeting the same `AssetGroup` cannot exceed 10,000 operations.\n- Violating either of these conditions results in the entire batch job failing.\n\nTroubleshooting\n---------------\n\nListing group filter operations in a batch job are processed as one transaction,\nwhich can lead to scenarios where many operations fail due to a small number of\nerroneous operations. Further, because of the way `BatchJob` operations are\nprocessed, the root cause of the failures may appear at an index before or after\nthe downstream failures.\n\nFor example, when processing a response from [`ListBatchJobResults`](/google-ads/api/reference/rpc/v21/BatchJobService#listbatchjobresults), you may find that several\noperations failed with a status message, `Ad group is invalid due to the listing\ngroups it contains`. This message typically indicates that the operation at this\nindex was cancelled because of a failed operation at a different index. To\nidentify the root cause of the issue, we recommend iterating through all status\nmessages in the [`BatchJobResult`](/google-ads/api/reference/rpc/v21/BatchJobResult)---before\nand after the index of the `Ad group is invalid` error message---in search\nof additional error information."]]
