일괄 작업에 광고 그룹 기준 또는 애셋 그룹 등록정보 그룹 필터가 포함된 작업이 있는 경우 일괄 작업의 작업은 Google Ads API 서버에서 수신될 때 여러 하위 일괄로 분할됩니다. 일괄 작업의 표준 작업과 달리 등록정보 그룹 필터 작업이 포함된 각 하위 일괄 처리는 원자적으로 처리됩니다.
등록정보 그룹 필터가 포함된 일괄 작업이 하위 일괄 작업으로 분할되는 방식은 다음 요소에 따라 결정됩니다.
이 개념에 대해서는 다음 다이어그램을 참조하세요. 각 회색 상자는 Google Ads API를 사용하여 제출된 일괄 작업을 나타냅니다. 회색 상자 내에서 개별 작업은 Google Ads API 서버가 만드는 하위 배치로 나타내기 위해 색상별로 그룹화됩니다. 각 회색 상자의 작업 순서는 작업이 일괄 작업에 추가된 순서에 해당합니다.
제한사항
일괄 작업의 컨텍스트에서 등록정보 그룹 필터를 사용할 때는 다음 제한사항이 적용됩니다.
listing_group을 포함하고 동일한 AdGroup을 타겟팅하는 단일 AssetGroupListingGroupFilterOperation 작업 일괄 처리의 길이는 20,000개 작업을 초과할 수 없습니다. 하지만 작업이 10,000개를 초과하지 않는 것이 좋습니다.
동일한 AssetGroup을 타겟팅하는 단일 AssetGroupListingGroupFilterOperation 작업 일괄 처리는 10,000개 작업을 초과할 수 없습니다.
이러한 조건 중 하나라도 위반하면 전체 일괄 작업이 실패합니다.
문제 해결
일괄 작업의 등록정보 그룹 필터 작업은 하나의 트랜잭션으로 처리되므로 잘못된 작업이 소수여도 많은 작업이 실패하는 시나리오가 발생할 수 있습니다. 또한 BatchJob 작업이 처리되는 방식 때문에 실패의 근본 원인이 다운스트림 실패 전후의 색인에 표시될 수 있습니다.
예를 들어 ListBatchJobResults의 응답을 처리할 때 상태 메시지 Ad group is invalid due to the listing
groups it contains와 함께 여러 작업이 실패한 것을 확인할 수 있습니다. 이 메시지는 일반적으로 이 색인의 작업이 다른 색인의 작업 실패로 인해 취소되었음을 나타냅니다. 문제의 근본 원인을 파악하려면 BatchJobResult의 모든 상태 메시지를 Ad group is invalid 오류 메시지의 색인 전후로 반복하여 추가 오류 정보를 검색하는 것이 좋습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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."]]
