📘
The request object must include 2 properties:

campaigns - a list of Campaign IDs to update (passed as numbers).

update - an object containing the fields to update. (It must be a supported field - see below.)

Supported fields

Field	Notes
`branding_text`
`is_active`
`cpc`
`spending_limit`
`marketing_objective`
`start_date`	Can only be updated if the existing `start_date` lies in the future (existing `start_date` > today).
`end_date`
`country_targeting`
`sub_country_targeting`
`region_country_targeting`
`dma_country_targeting`
`city_targeting`
`platform_targeting`
`os_targeting`
`connection_type_targeting`
`publisher_targeting`
`external_brand_safety`

📘
Although name is a supported field, we recommend giving each campaign a unique name.

🚧
Guidelines

Use the POST verb.

Limit each request to a maximum of 200 campaigns.

For each request, the API will skip any unsupported fields, and attempt to update the others.

If any fields are read-only, a 400 response is returned. Otherwise, a 200 response is returned, regardless of any skipped fields (see previous point).

By default, if the update operation fails for 1 campaign, then no campaigns will be updated. To override this behavior, pass ?is_atomic=false.

🚧
This endpoint supports the network account
You can use a network account to update campaigns across the network:
POST backstage/api/1.0/{network-account}/campaigns/bulk-update
For more information about the network account see: Network Accounts.

Example

{
   "campaigns": [
      1001,
      1002,
      1003
   ],
   "update": {
      "spending_limit": 2000,
      "cpc": 2,
      "is_active": false
   },
   "country_targeting": {
      "type": "INCLUDE",
      "value": [
         "AU",
         "GB"
      ]
   },
   "platform_targeting": {
      "type": "INCLUDE",
      "value": [
         "TBLT",
         "PHON"
      ]
   }
}

📘
See also

Update a Campaign (above).

Bulk update items across campaigns.