Google Ads Developer Blog: google_ads

Google Ads API v2 sunset reminder

Thursday, August 27, 2020

sunsetAfter this date, all v2 API requests will begin to fail.newer version

Upgrading to the newest version

Release notes

forumgoogleadsapi-support@google.com

- Thanet Knack Praneenararat, Google Ads API Team

Announcing v5 of the Google Ads API beta

Wednesday, August 26, 2020

Google Ads API betaclient librariesmigration guide

Return metrics for entities not formally supported in the API, such as Discovery campaigns, are now available. These entities will show UNKNOWN enum values returned. See the release notes for more details.

New request parameter to opt into returning all mutable fields in the response during a mutate.

The API is moving towards using field presence such as optional string and optional double instead of wrapper types such as StringValue and DoubleValue. Your code will be easier to use and simplifies the API with payloads that are significantly smaller. Approximately half of our resources have been updated in this release. The full list is in the migration guide, and our code examples have been updated. The rest of the resources will change to field presence in a future release.

Subfields of AdGroupAd.policy_summary are now selectable. Non-repeated subfields of AdGroupAd.policy_summary are now filterable.

Support for Keyword Planner:

Added KeywordPlanKeywordHistoricalMetrics.close_variants to return the close variant keywords that have been merged to compute the historical metrics.
Added KeywordPlanService.GenerateForecastTimeSeries that returns the weekly forecast trend for Keyword Plan for the next 52 weeks.

Where can I learn more?

Release Notes

Guides

Reference

Upgrading to the newest version

forum

Nadine Wang, on behalf of the Google Ads API Team

Changes to campaign_bid_modifier reporting in the Google Ads API

Friday, July 10, 2020

Starting on September 1, 2020, we will be making a change to how the Google Ads API reports campaign-level bid modifiers to make the API’s results more consistent with the Google Ads UI.

Currently, Google Ads Query Language queries for campaign_bid_modifier resources only return rows if either of the following conditions are met:

A non-zero bid modifier is set, or
The row’s associated criterion_id has accrued metrics for the CALLS interaction type.

After this change goes into effect, queries for campaign_bid_modifier resources will return rows for all campaigns, more closely matching what a user sees in the Google Ads UI’s Advanced bid adj. > Interactions screen.

Users who wish to keep using a restricted view of their campaign_bid_modifier reports can add a predicate such as “WHERE campaign_bid_modifier.bid_modifier != 1.0" (where a 1.0 value is equivalent to a bid adjustment of ±0%) to their queries to limit reporting to non-zero bid modifier rows.

This change will not affect the behavior of the AdWords API.

If you have any questions about this change, please reach out to us on the forum.
- Adam Ohren, The Google Ads API team

Announcing v4 of the Google Ads API beta

Wednesday, July 8, 2020

Today, we’re announcing the v4 release of the Google Ads API beta. To use the v4 features, update your client library. If you are upgrading from v1, v2, or v3, some of your code may require changes when you switch to the new v4 endpoint. For more information on breaking changes, see the migration guide. If you are using v1, upgrade by July 29, 2020.

Here are the highlights:

Local campaigns. Local campaigns streamline the process for you, making it easy to promote your stores across Google’s largest properties including the Google Search Network, Maps, YouTube, and the Google Display Network.
Support for retrieving and reporting on Smart campaigns.
Support for account-level optimization score.
Keyword Planning. See the Planning section in the release notes for details.
Linking third party app analytics accounts to Google Ads accounts. See the Account Management section in the release notes for details.

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published next week. If you have any questions or need additional help, contact us via the forum.

Nadine Wang, on behalf of the Google Ads API Team

Google Ads API beta v1 sunset reminder

Tuesday, June 16, 2020

Google Ads API beta v1 will sunset on July 29, 2020. After this date, all v1 API requests will begin to fail. Please migrate to a newer version prior to July 29, 2020 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.

Nadine Wang, Google Ads API Team

Entity IDs as 64-bit in AdWords API, Google Ads API beta, Google Ads scripts, and Content API for Shopping

Monday, June 15, 2020

In the AdWords API, the Google Ads API beta, Google Ads scripts, and the Content API for Shopping, all entity IDs are 64-bit signed integers. They are of type:

Applications that integrate with the API should handle ID values in that range.

Historically, the following IDs were within the maximum value of 32-bit signed integer, but will soon be exceeding this range. Over the years, all of you have been so productive that we need to make sure 64-bit signed integers are available to allow the creation of more entities with unique IDs. This was announced starting in July 2019. To avoid any issues, please make sure your applications handle these IDs within a range of 64-bit signed integer values. Also make sure that your application is ready to support a 64-bit signed integer for any other entity IDs not listed below.

Which IDs are affected in the AdWords API and the Google Ads API beta?

	AdWords API	Google Ads API beta
Bidding Strategy	`BiddingStrategyConfiguration.bidding_strategy_id` `BiddingStrategyId` (multiple reports)	`BiddingStrategy.id`
Budget	`BudgetOrder.id`	`AccountBudget.id` `BillingSetup.id`
User List	`UserList.id` `CriterionUserList.userListId` `CLICK_PERFORMANCE_REPORT.UserListId` `AUDIENCE_PERFORMANCE_REPORT.Id`	`UserList.id`
Shopping Campaigns	`ServiceLink.serviceLinkId` `ShoppingSetting.merchantId` `SHOPPING_PERFORMANCE_REPORT.MerchantId` `SHOPPING_PERFORMANCE_REPORT.AggregatorId`	`MerchantCenterLink.id` `ShoppingSetting.merchant_id` `segments.product_merchant_id` `segments.product_aggregator_id`
Conversion Action	`ConversionTracker.id` `ConversionTrackerId` (multiple reports) `ConversionTracker.originalConversionTypeId`	`ConversionAction.id`
Account Conversion Tracking Configuration	`ConversionTrackingSettings.effectiveConversionTrackingId`	`ConversionTrackingSetting.conversion_tracking_id` `ConversionTrackingSetting. cross_account_conversion_tracking_id`

Which IDs are affected in Google Ads scripts?
JavaScript can only accurately represent integers up to 53 bits, so it's strongly advised that you begin treating all IDs in Google Ads scripts as string to avoid any possible future errors with high ID numbers.

	Google Ads scripts
Bidding Strategy	`AdsApp.BiddingStrategy.getId()`
Budget	`AdsApp.BillingAccount.getId()` `AdsApp.BudgetOrder.getId()`
User List	`AdsApp.Audience.getId()` `AdsApp.ExcludedAudience.getId()` `AdsApp.UserList.getId()` `AdsApp.ShoppingCampaignAudience.getAudienceId()` `AdsApp.ShoppingCampaignAudienceBuilder.withAudienceId()` `AdsApp.ShoppingCampaignAudienceSelector.withIds()` `getAudienceId()` and `withAudienceId()` for all Targeting -> Audience `Search` methods.

Which IDs are affected in the Content API for Shopping?
All IDs are returned as string in REST and as INT64 in the client libraries. If you convert IDs to a number in your application, please make sure the application can handle 64-bit signed integers. An example of this is merchant ID that is set in the client library’s configuration or in the REST URL.

Content API for Shopping

Merchant Center AccountIdentifier.merchantId

Order.merchantId

OrdersCustomBatchRequestEntry.merchantId

RegionalinventoryCustomBatchRequestEntry.merchantId

ProductsCustomBatchRequestEntry.merchantId

ProductstatusesCustomBatchRequestEntry.merchantId

AccountsCustomBatchRequestEntry.merchantId

OrderReportDisbursement.merchantId

OrderReportTransaction.merchantId

LocalinventoryCustomBatchRequestEntry.merchantId

ReturnpolicyCustomBatchRequestEntry.merchantId

Shopping Campaign AccountIdentifier.aggregatorId

Where can I get support?
If you have any API questions or need help, you can reach us at:

AdWords API and Google Ads API beta forum or googleadsapi-support@google.com.
Google Ads scripts forum.
Content API for Shopping forum.

Nadine Wang, on behalf of the entire Google Ads Team

Update on the Google Ads API Beta

Tuesday, May 26, 2020

Since our last announcement in July, we've made several updates to improve the performance of the Google Ads API. Your feedback was essential to us in making these improvements and will continue to be throughout the remainder of the Beta.

What has been fixed?
Over the past several months, we've rolled out performance improvements to Google Ads API read and mutate functionality. Some of these updates are visible in recent versions of the API, such as the launch of GoogleAdsService.SearchStream() in v3_0, while other improvements have sped up the response times of existing services and methods.

What's next for the Google Ads API Beta?
It is our top priority to get the Google Ads API ready for general availability. This involves rolling out features for key user journeys, for example: a service for asynchronous batch updates. If you have any feedback on the API's readiness to address your tool's requirements, we'd like to hear from you!

Which API should I use?
Throughout the remainder of the Beta, the AdWords API will continue to be the primary API for programmatically accessing and managing Google Ads campaigns. When deciding whether to use the Google Ads API Beta to run production systems, please keep in mind that we may release updates in preparation for general availability. As a reminder, changes will be released in new versions of the Google Ads API Beta. They will not affect your existing code unless announced otherwise on this blog.

If you have any feedback or questions regarding the performance, feature availability and overall usability of the Google Ads API Beta, please contact us at googleadsapi-support@google.com.
-- The Google Ads API team

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:

Populating the target spend field on existing standard and portfolio strategies
Attaching portfolio strategies that have the deprecated field set to campaigns

Read on to see how this will affect your API usage:

	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

If you have any questions about this change or any other API feature, please contact us via the forum.

- Cory Liseno, Google Ads API Team

Announcing v3_1 of the Google Ads API beta

Wednesday, April 29, 2020

Today we’re announcing the v3_1 release of the Google Ads API beta. To use the v3_1 features, please update your client library. If you are upgrading from v1 or v2, some of your code may require changes when you switch to the new v3 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published next week. If you have any questions or need additional help, please contact us via the forum.

Nadine Wang, on behalf of the Google Ads API Team

Google Ads conversion reporting issues starting April 9

Friday, April 10, 2020

Update (April 10, 2020 19:35 PST): Conversion data in all reports has been fixed.

An issue that impacted Google Ads reporting for Search and Shopping conversions occurring between April 9 and April 10 (Pacific Time) for advertisers using non-last click attribution models has been fixed and the data is now correct in all reports.
If you downloaded any of the fields in the table below or any derivative custom columns using the AdWords API, Google Ads API and Google Ads scripts between April 9th 8:00 PM PST and April 10th 7:20 PM PST, you may have incorrect data in your systems. Please re-download the affected fields to ensure accurate conversions reporting.
We appreciate your patience as we worked to resolve this issue as quickly as possible.

AdWords API

Google Ads API beta

Conversions
ConversionValue
ConversionRate
ValuePerConversion
CostPerConversion
AllConversions
AllConversionValue
AllConversionRate
ValuePerAllConversion
CostPerAllConversion
CurrentModelAttributedConversions
CurrentModelAttributedConversionValue
ValuePerCurrentModelAttributedConversion
CostPerCurrentModelAttributedConversion

metrics.all_conversions
metrics.all_conversions_from_click_to_call
metrics.all_conversions_from_interactions_rate
metrics.all_conversions_from_interactions_value_per_interaction
metrics.all_conversions_value
metrics.all_conversions_value_per_cost
metrics.conversions
metrics.conversions_from_interactions_rate
metrics.conversions_from_interactions_value_per_interaction
metrics.conversions_value
metrics.conversions_value_per_cost
metrics.cost_per_all_conversions
metrics.cost_per_conversion
metrics.cost_per_current_model_attributed_conversion
metrics.cross_device_conversions
metrics.current_model_attributed_conversions
metrics.current_model_attributed_conversions_from_interactions_rate
metrics.current_model_attributed_conversions_from_interactions_value_per_interaction
metrics.current_model_attributed_conversions_value
metrics.current_model_attributed_conversions_value_per_cost
metrics.value_per_all_conversions
metrics.value_per_conversion
metrics.value_per_current_model_attributed_conversion

On April 9, 2020 at approximately 8pm PST, a bug caused Google Ads Search and Shopping conversions occurring between April 9 12:01 AM PST onwards to be underreported for advertisers using non-last click attribution models. This bug impacts reports in all Google Ads interfaces, including any report data downloaded via the AdWords API, Google Ads API and Google Ads scripts. Google Ads bid strategies are not impacted by this issue.
We are actively working on fixing the bug and correcting the conversion data.

- Josh Radcliff, Google Ads API Team

Updates to the AdWords API and Google Ads API

Tuesday, April 7, 2020

As communities respond to COVID-19, we know that this time presents unique challenges for everyone. Below are updates and resources to help you navigate and plan through these challenging times.

How does this impact the APIs?
We realize you are balancing a lot in your life. Here’s what we’re doing to help:

Delaying the sunset of the Google Ads API v1: The Google Ads API’s v1 sunset is delayed until July 29, 2020. The AdWords API will continue to be available for production use.
Giving additional time: Any new changes that require updates in your AdWords API and Google Ads API code will be given additional time or will be deferred.

We will continue releasing new versions of the Google Ads API to get new features to you.

What are some customer resources?
Google Ads has provided the following resources for business and customers:

Where can I get support?
The Google Ads Help Center posted a delay for non-API related support. This delay includes developer token approvals and changes.

If you have any API questions or need help, you can reach us at googleadsapi-support@google.com or on our Google Ads API and AdWords API forum.

Nadine Wang, on behalf of the entire Google Ads API Team

Changing statuses of app and app engagement ads that do not serve

Friday, March 27, 2020

On April 17, 2020, app ads and app engagement ads that do not serve will have their statuses changed automatically from ENABLED to DISABLED. For each ad group in App campaigns, only the first created ad is ever eligible to serve, so we’re disabling other ads in the same ad group to prevent confusion. This means that you may see some changes in the number of report rows if your queries have a condition that includes ad_group_ad.status for the Google Ads API or AdGroupAdStatus for the AdWords API.

What do you need to do?
If you’re not interested in the disabled ads, you don’t need to take any action. Only beware that the number of report rows returned by your query may change. For example, if your queries have a condition to get only enabled ads, you may see fewer report rows.

If you still wish to see the performance data of the disabled ads, make sure your report queries also include the disabled ads. Note that as they don’t serve anymore, these ads won’t accrue any more performance stats beyond the above-mentioned date.

In case you need more information on reporting, follow the below links:
For the Google Ads API,

For the AdWords API,

Reporting
AdWords Query Language

As always, if you have any questions, feel free to reach out to us on the AdWords API and Google Ads API forum.

- Thanet Knack Praneenararat, Google Ads API Team

Preventing App engagement campaigns for prohibited apps

Tuesday, March 10, 2020

Starting on April 1, 2020, the Google Ads API will prevent the creation of new App engagement campaigns for apps in prohibited categories.

The Google Ads API currently allows you to create App engagement campaigns for any category of app. But if an app from a prohibited category is chosen, those campaigns are prohibited from serving ads. This can lead to confusion among advertisers.

Enabling the API to validate that such campaigns are indeed eligible to serve before their creation will allow developers to take corrective action early on and also ensure client accounts are able to serve their intended ads.

Change details
App engagement campaigns are identified in the API as campaign objects with the following properties.

Once this change goes into effect, API calls to create campaigns of the above type will fail if the campaign’s app_campaign_setting.app_id references an app in a prohibited category.

Versions v3 and later of the API will throw a SENSITIVE_CATEGORY_APP error. Earlier versions of the API will throw a more generic UNKNOWN error, since the error code is not published in those versions. These errors may surface from the following services and operations.

API Version	Service	Operation	Error
v3+	`CampaignService`	`create`	`CampaignError.SENSITIVE_CATEGORY_APP`
v1, v2	`CampaignService`	`create`	`CampaignError.UNKNOWN`

For instances of error code CampaignError.UNKNOWN, the GoogleAdsError’s details.unpublished_error_code field will indicate, “CampaignError.SENSITIVE_CATEGORY_APP”.

Implementation and support
If you create App engagement campaigns with the Google Ads API, please add error handling for apps in prohibited categories. In order to leverage the new SENSITIVE_CATEGORY_APP error, please upgrade to v3 of the Google Ads API first where possible.

If you’re unable to upgrade versions before the change goes into effect, please check for error code CampaignError.UNKNOWN upon campaign creation, and verify that the error’s details.unpublished_error_code string matches the error name documented in the previous section, to indicate a prohibited category may be in use.

For more details on implementing support for App campaigns, see our App Campaigns developer guide for more information. And as always, if you have any questions about this change, don’t hesitate to reach out to us on the Google Ads API developer forum.
Adam Ohren, Google Ads API Team

Announcing v3_0 of the Google Ads API beta

Thursday, February 27, 2020

Today we’re announcing the v3_0 release of the Google Ads API beta. To use the v3_0 features via the new endpoint, please update your client libraries. If you are upgrading from v1 or v2, some of your code may require changes when you switch to the new v3 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published next week. If you have any questions or need additional help, please contact us via the forum.

Nadine Wang, on behalf of the Google Ads API Team

Gmail on standard Shopping campaigns

Thursday, February 6, 2020

Beginning the week of Mar 4th, 2020, Shopping ads (both Product Shopping ads and Showcase Shopping ads) in your standard Shopping campaigns that target the Google Display Network will be eligible to appear on Gmail in addition to YouTube and Google Discover. This means that reporting information will include Gmail in addition to YouTube and Google Discover for the following configurations:

To allow your advertisers to opt-in/opt-out of Gmail, YouTube and Google Discover for standard Shopping campaigns, you will need to enable or disable the following setting:

If you have any questions or need help, please contact us via the forum.

- Ian Ballantyne, on behalf of the Google Ads API Team

Complete sunset of accelerated budget delivery

Wednesday, January 29, 2020

Last October, we announced the sunset of accelerated budget delivery for use with Search campaigns, Shopping campaigns, and shared budgets. These campaigns have since been made unavailable for use with accelerated budget delivery.

Later this year, accelerated budget delivery will also be sunset for all other remaining campaign types for both shared and non-shared budgets. This includes Display, App, video campaigns, and others, and this sunset will affect budgets in all versions of the AdWords API, Google Ads API, and Google Ads scripts.

Starting at the end of April, 2020, scripts and both APIs will prevent campaigns from using new and existing budgets with the ACCELERATED delivery method.

Creating a new budget with its delivery method field set to ACCELERATED will no longer be allowed.
Changing an existing budget from STANDARD to ACCELERATED delivery method will no longer be allowed.
Setting a campaign to use a pre-existing budget with an ACCELERATED delivery method will no longer be allowed.

Any of the above operations will result in errors from the APIs and scripts, according to the following:
AdWords API

Service	Field Value	Error
BudgetService	deliveryMethod: `ACCELERATED`	OperationAccessDenied.ACTION_NOT_PERMITTED
CampaignService	budget* [*]only if set to accelerated delivery	OperationAccessDenied.ACTION_NOT_PERMITTED

Google Ads API

Service	Field Value	Error
CampaignBudgetService	delivery_method: `ACCELERATED`	OperationAccessDenied.ACTION_NOT_PERMITTED
CampaignService	campaign_budget* [*] only if set to accelerated delivery	OperationAccessDenied.ACTION_NOT_PERMITTED

Google Ads scripts

Method	Error
`AdsApp.Budget.setDeliveryMethod(“ACCELERATED”)`	“Action not permitted”

Making changes to existing ACCELERATED budgets (e.g., updating amount or status fields in the API, or using their corresponding AdsApp.Budget methods in scripts) will still be allowed until May 2020, after which any modification to these budgets will also result in analogous errors.

Future versions of the Google Ads API and Google Ads scripts may remove support for the accelerated budget delivery option altogether.

Please don’t hesitate to reach out to us on the AdWords API / Google Ads API forum or the Google Ads scripts forum if you have any questions about this change.
Adam Ohren, Google Ads API Team

Changes to stats retrieval for Search campaigns with Display Expansion

Monday, January 13, 2020

What’s changing?

We are changing how stats for Search campaigns with Display Expansion (previously known as Search campaigns with Display Select) are reported by the AdWords API, the Google Ads API, and Google Ads scripts.

Starting the week of Feb 17, 2020, we will no longer return display keyword stats for Search campaigns with Display Expansion in

Why is this changing?

Search campaigns with Display Expansion historically used keywords to perform Display Expansion. As we strive to improve targeting for Display Expansion, it is no longer possible to meaningfully and consistently attribute stats to keywords. As a result, this view has been removed from the Google Ads UI. The changes in this announcement aim to create parity between APIs and UI.

What should I do?

Before the sunset date, we recommend switching to alternate reports for fetching stats for Search campaigns with Display Expansion.

If you have any questions or need help, please contact us via the Google Ads scripts forum or the AdWords API and Google Ads API forum. - Anash P. Oommen, Google Ads API Team

Upcoming sunset of message extensions in AdWords and Google Ads APIs and Google Ads scripts

Thursday, December 19, 2019

Update (Jan 21, 2020): Clarified impact in more detail on both APIs.

On January 27, 2020, message extensions will be sunset in AdWords and Google Ads APIs and Google Ads scripts. After the sunset date:

All existing message extensions will no longer serve.
You will not be able to create new message extensions or update existing extensions.
You will still be able to retrieve data for existing message extensions until the end of 2020.
You will also be able to remove the existing message extensions until the end of 2020.

What will happen when you try to create or update message extensions after the sunset date?
If you try to create or update a message extension, you will see the following errors:

Google Ads API

Trying to create or update a TextMessageFeedItem will result in the ExtensionSettingError.INVALID_FEED_TYPE error.
Trying to create a message extension via FeedMapping with placeholder_type set to MESSAGE will result in the FeedMappingError.INVALID_PLACEHOLDER_TYPE error.
Trying to create or update CampaignFeeds, AdGroupFeeds, or CustomerFeeds by specifying MESSAGE in laceholderTypes will result in the CampaignFeedError.INVALID_PLACEHOLDER_TYPE, AdGroupFeedError.INVALID_PLACEHOLDER_TYPE, and CustomerFeedError.INVALID_PLACEHOLDER_TYPE errors, respectively.

AdWords API

Trying to create or update a MessageFeedItem will result in the ExtensionSettingError.INVALID_FEED_TYPE error.
Trying to create a message extension via FeedMapping using placeholder type ID 31 will result in the FeedMappingError.INVALID_PLACEHOLDER_TYPE error.
Trying to create or update CampaignFeeds, AdGroupFeeds, or CustomerFeeds by specifying ID 31 in placeholderTypes will result in the CampaignFeedError.INVALID_PLACEHOLDER_TYPES, AdGroupFeedError.INVALID_PLACEHOLDER_TYPES and CustomerFeedError.INVALID_PLACEHOLDER_TYPES errors, respectively.

Google Ads scripts
Trying to execute the following operations will result in the error, “Cannot operate on deprecated placeholder type” (translated to the language based on your locale):

Creating a message extension via AdsApp.MessageBuilder
Updating a message extension via any methods beginning with set of AdsApp.Message
Attaching a message extension to Campaign or AdGroup via addMessage

What do you need to do?

Retrieve all the data from your existing message extensions that you need. All message extension data will be deleted at the end of 2020.
Ensure that your programs don’t contain any code trying to create or update message extensions after the sunset date.

As always, if you have any questions, feel free to reach out to us on the Google Ads API forum.

- Thanet Knack Praneenararat, Google Ads API Team

Smart Display Campaigns Change in AdWords API and Google Ads API Starting January 31, 2020

Monday, December 16, 2019

On January 31, 2020, the AdWords API and Google Ads API will no longer allow positive user list criteria in Smart Display campaigns.

What happens to my existing Smart Display Campaigns?
Existing Smart Display campaigns with positive user list targeting:

Will continue to serve without interruption.
Will no longer allow adding a positive CampaignCriterion or AdGroupCriterion with a user list criterion.
Will no longer serve if the ad group is paused and then restarted.

What code do I need to change?
Please update your code that manages Smart Display campaigns per the following updated validation rules:

AdWords API	Google Ads API
Positive CampaignCriterion.criterion set to CriterionUserList can no longer be added.	Positive CampaignCriterion.user_list can no longer be added.
Positive AdGroupCriterion.criterion set to CriterionUserList can no longer be added.	Positive AdGroupCriterion.user_list can no longer be added.

You will receive a CANNOT_TARGET_CRITERION error if you try to add one of these criteria.

Why is this changing?
Adding these criteria for Smart Display campaigns was never formally supported as outlined in our Smart Display campaigns guide. Additional validation is being put in place now to make sure that these values are not being set. Please see the guide for supporting criteria.

If you have any questions while updating your code, please reach out to us on our Google Ads API and AdWords API forum.

Nadine Wang, Google Ads API Team

Ads Developer Blog

Google Ads API v2 sunset reminder

Announcing v5 of the Google Ads API beta

Changes to campaign_bid_modifier reporting in the Google Ads API

Announcing v4 of the Google Ads API beta

Google Ads API beta v1 sunset reminder

Entity IDs as 64-bit in AdWords API, Google Ads API beta, Google Ads scripts, and Content API for Shopping

Update on the Google Ads API Beta

Reminder about sunset, creation of target spend field for Maximize Clicks strategies in Ads APIs

Announcing v3_1 of the Google Ads API beta

Google Ads conversion reporting issues starting April 9

Updates to the AdWords API and Google Ads API

Changing statuses of app and app engagement ads that do not serve

Preventing App engagement campaigns for prohibited apps

Announcing v3_0 of the Google Ads API beta

Gmail on standard Shopping campaigns

Complete sunset of accelerated budget delivery

Changes to stats retrieval for Search campaigns with Display Expansion

Upcoming sunset of message extensions in AdWords and Google Ads APIs and Google Ads scripts

Smart Display Campaigns Change in AdWords API and Google Ads API Starting January 31, 2020

Labels

Archive

Feeds

Google Ads API [+]

AdWords API [+]

Google Ads scripts [+]

Content API for Shopping [+]

Google Ad Manager API [+]

DCM API [+]

Mobile Ads [+]

IMA SDK [+]