대부분의 서비스는 요청을 한 후 응답을 기다려야 하는 동기식 API를 제공하지만 BatchJobService를 사용하면 작업이 완료될 때까지 동기식으로 기다리지 않고 여러 서비스에서 일괄 작업을 실행할 수 있습니다.
서비스별 변이 작업과 달리 BatchJobService의 단일 작업은 캠페인, 광고 그룹, 광고, 기준, 라벨, 피드 항목의 혼합 컬렉션에 대해 작동할 수 있습니다.
제출된 작업은 병렬로 실행되며 BatchJobService는 비율 제한 오류와 같은 일시적인 오류로 인해 실패한 작업을 자동으로 재시도합니다. Google Ads API는 API 작업 계산 안내에 따라 각 작업을 일일 작업 한도에 포함하여 계산합니다.
[null,null,["최종 업데이트: 2025-08-27(UTC)"],[[["\u003cp\u003e\u003ccode\u003eBatchJobService\u003c/code\u003e enables asynchronous execution of multiple operations across various Google Ads services, reducing the need for synchronous waiting.\u003c/p\u003e\n"],["\u003cp\u003eIt supports a wide range of operations, allowing you to manage campaigns, ad groups, ads, criteria, labels, and feed items within a single job.\u003c/p\u003e\n"],["\u003cp\u003eFailed operations due to transient errors like rate limits are automatically retried, ensuring higher reliability.\u003c/p\u003e\n"],["\u003cp\u003eAlthough it minimizes API requests and retries failed operations, using \u003ccode\u003eBatchJobService\u003c/code\u003e does not inherently guarantee improved performance; experimentation is crucial to determine its suitability for specific use cases.\u003c/p\u003e\n"],["\u003cp\u003eCertain atomic operations like \u003ccode\u003eCampaignConversionGoalOperation\u003c/code\u003e, \u003ccode\u003eConversionGoalCampaignConfigOperation\u003c/code\u003e, \u003ccode\u003eCustomConversionGoalOperation\u003c/code\u003e, \u003ccode\u003eCustomerConversionGoalOperation\u003c/code\u003e, and \u003ccode\u003eCustomerOperation\u003c/code\u003e are not supported in batch jobs and should be executed using \u003ccode\u003eGoogleAdsService\u003c/code\u003e instead.\u003c/p\u003e\n"]]],[],null,["# Batch Processing\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nWhile most services provide synchronous APIs that require you to make a request\nand then wait for a response, [`BatchJobService`](/google-ads/api/reference/rpc/v21/BatchJobService)\nprovides a way to perform batches of operations on multiple services without\nsynchronously waiting for the operations to complete.\n\nUnlike service-specific mutate operations, a single job in\n[`BatchJobService`](/google-ads/api/reference/rpc/v21/BatchJobService) can operate against a mixed\ncollection of campaigns, ad groups, ads, criteria, labels, and feed items.\nSubmitted jobs run in parallel, and\n[`BatchJobService`](/google-ads/api/reference/rpc/v21/BatchJobService) automatically retries\noperations that fail due to transient errors such as rate limit errors. The\nGoogle Ads API still counts each operation towards your\n[daily operation limit](/google-ads/api/docs/access-levels#access-levels), following the\n[API operations](/google-ads/api/docs/rate-sheet#api-operations) counting instructions.\n\n[`BatchJobService`](/google-ads/api/reference/rpc/v21/BatchJobService) also lets you use\n[temporary IDs](/google-ads/api/docs/batch-processing/temporary-ids) within your requests so\nyou can submit dependent operations in a single job.\n| **Note:** Use of [`BatchJobService`](/google-ads/api/reference/rpc/v21/BatchJobService) can reduce the number of requests sent but its use must be evaluated to see if it's a good fit for your needs. The main reasons for using batch processing are to minimize the number of API requests and retry operations that fail due to transient errors. This doesn't guarantee improved performance resulting in higher throughput or quicker job completion. Experiment with different combinations of batch and non-batch processing to determine the optimal solution for your circumstances.\n\nOperations\n----------\n\n`BatchJobService` supports all of the operations listed in\n[`MutateOperation`](/google-ads/api/reference/rpc/v21/MutateOperation), with a few important\nexceptions.\n\nBecause the Google Ads API executes all operations in a job with\n[partial failure](/google-ads/api/docs/best-practices/partial-failures) enabled, if a job is\ncancelled or individual operations fail, operations that succeeded will *not*\nbe rolled back.\n\nThe following operations in `MutateOperation` must be\n[atomic](/google-ads/api/docs/mutating/bulk-mutate), and thus, don't support partial failure\nand are *not* supported within batch jobs. Avoid adding these operations to your\njobs, set `partial_failure` to `false` in your requests, and use the `mutate`\nmethod in [`GoogleAdsService`](/google-ads/api/reference/rpc/v21/GoogleAdsService) instead.\n\n#### Unsupported operations in BatchJobService\n\n- [`CampaignConversionGoalOperation`](/google-ads/api/reference/rpc/v21/CampaignConversionGoalOperation)\n- [`ConversionGoalCampaignConfigOperation`](/google-ads/api/reference/rpc/v21/ConversionGoalCampaignConfigOperation)\n- [`CustomConversionGoalOperation`](/google-ads/api/reference/rpc/v21/CustomConversionGoalOperation)\n- [`CustomerConversionGoalOperation`](/google-ads/api/reference/rpc/v21/CustomerConversionGoalOperation)\n- [`CustomerOperation`](/google-ads/api/reference/rpc/v21/CustomerOperation)"]]
