Service to fetch data and metrics across resources.
Creates, updates, or removes resources. This method supports atomic transactions with multiple types of resources. For example, you can atomically create a campaign and a campaign budget, or perform up to thousands of mutates atomically.
This method is essentially a wrapper around a series of mutate methods. The only features it offers over calling those methods directly are:
Note: Only resources that support atomic transactions are included, so this method can't replace all calls to individual services.
Atomicity makes error handling much easier. If you're making a series of changes and one fails, it can leave your account in an inconsistent state. With atomicity, you either reach the desired state directly, or the request fails and you can retry.
Temp resource names are a special type of resource name used to create a resource and reference that resource in the same request. For example, if a campaign budget is created with
To create a temp resource name, put a negative number in the part of the name that the server would normally allocate.
It's important to group mutates by resource type or the request may time out and fail. Latency is roughly equal to a series of calls to individual mutate methods, where each change in resource type is a new call. For example, mutating 10 campaigns then 10 ad groups is like 2 calls, while mutating 1 campaign, 1 ad group, 1 campaign, 1 ad group is like 4 calls.
Returns all rows that match the search query.
Returns all rows that match the search stream query.