Reminder about sunset, creation of target spend field for Maximize Clicks strategies in Ads APIs
Monday, May 18, 2020
On July 31st, 2019 we began to sunset the target spend field for Maximize Clicks bidding strategies. At the time, the feature was only removed from the UI, and the Google Ads APIs were not impacted.
Starting on June 30th, 2020, we will continue to sunset the target spend field in the Google Ads APIs as per our original blog post. This will affect all versions of both the AdWords API and the Google Ads API. The following behaviors will be blocked:
Change Description
Any
Performing any of the actions listed above will generate one of the following errors:
Starting on June 30th, 2020, we will continue to sunset the target spend field in the Google Ads APIs as per our original blog post. This will affect all versions of both the AdWords API and the Google Ads API. The following behaviors will be blocked:
- Populating the target spend field on existing standard and portfolio strategies
- Attaching portfolio strategies that have the deprecated field set to campaigns
Affected Target Spend Fields | |
---|---|
Google Ads API | campaign.target_spend.target_spend_micros bidding_strategy.target_spend.target_spend_micros |
AdWords API | Campaign.BiddingStrategyConfiguration.TargetSpendBiddingScheme.spendTarget SharedBiddingStrategy.TargetSpendBiddingScheme.spendTarget |
Change Description
Any
mutate
operations that set a target spend field for the first time will return an error. You will be able to update a target spend field that currently contains a value, but you cannot set previously empty fields to a new value. Additionally, any operation attaching a bidding strategy to a campaign where that bidding strategy has a value set for a target spend field, will throw an error. To manage Target Spend on any new campaigns, we recommend using campaign budget. In each of these cases an error will be thrown.Performing any of the actions listed above will generate one of the following errors:
OPERATION_NOT_PERMITTED_FOR_CONTEXT
UNSUPPORTED_FIELD_IS_SET