Batch Processing

While most services provide synchronous APIs, requiring you to make a request and then wait for a response, MutateJobService provides a way to perform batches of operations on multiple services without synchronously waiting for the operations to complete.

Unlike service-specific mutate operations, a single job in MutateJobService can operate against a mixed collection of campaigns, ad groups, ads, criteria, labels, and feed items. Submitted jobs run in parallel, and MutateJobService automatically retries operations that fail due to transient errors such as rate limit errors.

In addition, MutateJobService allows you to use temporary IDs within your requests so you can submit dependent operations in a single job.

Note: Use of MutateJobService 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. You need to experiment with different combinations of batch and non-batch processing to determine the optimal solution for your circumstances.

Supported Operations

All supported operations are listed in MutateOperation. Each operation is counted towards your daily operation limit following the API operations counting instructions.