Google Ads Developer Blog

Google Ads conversion reporting issues starting April 9

2020-04-10T18:23:00.000-07:00

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 scriptsbetween 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

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

2020-04-07T06:11:00.000-07:00

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

2020-03-27T08:05:00.000-07:00

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,

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

Announcing v3_0 of the Google Ads API beta

2020-02-27T14:31:00.001-08:00

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:

Added the ability to stream results from GoogleAdsService.SearchStream(). This is the recommended way for retrieving large scale data from GoogleAdsSearch. Please see this guide for more details.
Added support for moving a client customer to a new manager customer with CustomerManagerLinkService.MoveManagerLink().
Added PaymentMode.GUEST_STAY to enable the pay per stay mode of Hotels Commissions campaigns. This payment mode can only be used in conjunction with campaigns with AdvertisingChannelType.HOTEL, BiddingStrategyType.COMMISSION, and BudgetType.HOTEL_ADS_COMMISSION.

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

2020-02-06T09:52:00.000-08:00

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:

Google Ads API - Where the standard Shopping campaign advertising_channel_type is SHOPPING and the NetworkSettings for target_content_network is true, the reporting metrics for segment field ad_network_type of CONTENT will include Gmail in addition to YouTube and Google Discover.
AdWords API - Where the standard Shopping campaign AdvertisingChannelType is SHOPPING and the NetworkSetting for targetContentNetwork is true, the SHOPPING_PERFORMANCE_REPORT metrics for segment fields AdNetworkType1 and AdNetworkType2 of type CONTENT will include Gmail in addition to YouTube and Google Discover.

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:

Google Ads API - Modify the NetworkSettings of the standard Shopping campaign and set target_content_network to true (opt-in) or false (opt-out).
AdWords API - Modify the NetworkSetting of the standard Shopping campaign and set targetContentNetwork to true or false.

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

2020-01-29T09:01:00.000-08:00

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

2020-01-13T11:32:00.000-08:00

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

Display Keyword Performance Report in the AdWords API and Google Ads scripts
Display_keyword_view in the Google Ads API.

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.

Automatic Placement Performance reports and Display Topics Performance report can be used in the AdWords API and Google Ads scripts to get granular performance data about these campaigns in the Display Network. If you use the Google Ads API, you can use group_placement_view and topic_view instead.
Reports such as Campaign Performance report or Ad Group Performance report can be used in the AdWords API and Google Ads scripts to fetch aggregate performance stats for these campaigns. You need to filter by AdNetworkType2 = CONTENT for Display Network stats. If you use the Google Ads API, you can use the campaign or ad_group view instead.

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

2019-12-19T13:42:00.002-08:00

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

2019-12-16T08:07:00.000-08:00

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

AdFormat Change in AdWords API and Google Ads scripts Starting January 31, 2020

2019-12-12T06:24:00.000-08:00

On January 31, 2020, the AdWords API and Google Ads scripts will start returning UNKNOWN for AdFormat in the Geo Performance Report. All other reports with AdFormat will not be affected. The Google Ads API is not affected as the field does not exist.

Please update your code where it uses these fields:

AdWords API	Google Ads API	Google Ads scripts
AdFormat in `GEO_PERFORMANCE_REPORT`	NOT AFFECTED	AdFormat in `GEO_PERFORMANCE_REPORT`

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

Conversion reporting issues for November 11 through November 20

2019-11-21T19:33:00.002-08:00

Update (Nov 27, 2019 15:00 PST): An issue that impacted Google Ads reporting for conversions occurring between Nov 11 and Nov 20 (Pacific Time) for advertisers using non-last click attribution models has been fixed and the data is now correct in all reports, including the Search Query Performance, Geo Performance, Keywordless Query, and Keywordless Category reports.

An issue that impacted Google Ads reporting for conversions occurring between Nov 11 and Nov 20 (Pacific Time) for advertisers using non-last click attribution models has been fixed and the data is now correct.

If you downloaded any of the fields in the table below or any derivative custom columns using the AdWords API, Google Ads API or Google Ads scripts since November 20th 9:00 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.

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

AdWords API

Google Ads API beta

--Stan Grinberg, Google Ads API Team

Video and Channel IDs Change in AdWords API, Google Ads API, and Google Ads Scripts Starting November 15, 2019

2019-10-15T08:13:00.000-07:00

On November 15, 2019, AdWords API, Google Ads API, and Google Ads scripts will start returning null ID criteria for YouTube channels and videos that have been deleted, due to changes in our data retention policy. The criteria itself remains for a given ad group, but referencing the video ID or channel ID for that criteria will return null.

In the AdWords API v201809, null values are returned as two dashes (--) in reporting.
In the Google Ads API, NULL values are returned as NULL values.
In Google Ads Scripts, null values are returned as null JavaScript values.

Please update your code where it uses these fields:

AdWords API	Google Ads API	Google Ads Scripts
YouTubeVideo.videoId	YouTubeVideoInfo.video_id	YouTubeVideo.getVideoId()
YouTubeChannel.channelId	YouTubeChannelInfo.channel_id	VideoYouTubeVideo.getVideoId()
Criteria in `CAMPAIGN_CRITERIA_REPORT`		Media.getYouTubeVideoId()
Criteria in `CRITERIA_PERFORMANCE_REPORT`
Criteria in `SHARED_SET_CRITERIA_REPORT`

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

Python 2 Deprecation in Google Ads API Client Library

2019-10-09T12:08:00.000-07:00

On June 11, 2019 we deprecated support for Python 2 in the AdWords/Google Ad Manager client library for Python. As part of our previously announced plans, in mid-November 2019 we will be deprecating support in the Google Ads client library for Python as well.

When version 4.0.0 of the Google Ads client library for Python is released, we will officially end support for Python 2 and versions of Python 3 prior to 3.6.0.

If you use the Google Ads client library for Python, please take note of the following:

If you are already using Python version 3.6.0 or later, you can upgrade to Google Ads client library 4.0.0 and no other action is needed. If not, please do not upgrade to version 4.0.0 until you’ve upgraded to Python version 3.6.0 or later.
Version 4.0.0 will continue to support previous API versions such as v1_3 but we won't support client library issues related to Python 2 compatibility. For example, we won't release version 4.0.1 to fix a bug that only exists for Python 2 users.

If you have questions about the Python 3 migration, please submit an issue on the Google Ads client library repository’s Issues page, and for general API support please reach out to us on the Google Ads API forum.

Ben Karl, Google Ads API Team

Upcoming sunset of accelerated budget delivery

2019-10-01T12:00:00.000-07:00

This is a reminder that, starting October 14, 2019, accelerated budget delivery will no longer be generally available in AdWords API, Google Ads API, and Google Ads scripts for use with shared budgets, search campaigns, and shopping campaigns.

We encourage all developers to review our announcement of the sunset, which has been recently updated to include the most up-to-date information on expected error codes that could be returned after this change goes into effect.

Please don’t hesitate to contact us via the AdWords API and Google Ads API Forum or the Google Ads scripts forum if you have any questions.

Adam Ohren, Google Ads API Team

Restricting Payments account usage across manager account hierarchies

2019-08-23T10:56:00.000-07:00

Starting September 9, 2019, we are rolling out a change to prevent the same Payments accounts in the Google Ads API (billing accounts in the AdWords API) from being used across manager account hierarchies. Only valid Payments accounts belonging to the Google Ads manager account hierarchy can be used to create and update billing setups in the Google Ads API.

How does this affect you?
For your authenticated Google Ads client account

PaymentsAccountService.ListPaymentsAccounts() will return only valid Payments accounts belonging to your Google Ads manager account hierarchy, and
BudgetOrderService.getBillingAccounts() will return only valid billing accounts belonging to your Google Ads manager account hierarchy.

Therefore, you may get fewer results from those API calls than before.

What do you need to do?
Google Ads API
When creating/updating a new billing setup, you will need to select a valid Payments account returned by PaymentsAccountService.ListPaymentsAccounts(). If you use an invalid Payments account during the above processes, the INVALID_PAYMENTS_ACCOUNT error will be thrown.

AdWords API
When creating a new budget order, you will need to specify a valid billingAccountId (the ID of a valid billing account returned by BudgetOrderService.getBillingAccounts()). If you use an invalid billingAccountId during the above process, the BudgetOrderError.INVALID_BILLING_ACCOUNT error will be thrown.

As always, if you have any questions, feel free to post your questions on the Google Ads API forum.

- Thanet Knack Praneenararat, Google Ads API Team

Sunsetting accelerated budget delivery

2019-08-21T10:36:00.002-07:00

Update (Oct 1, 2019): We have updated the error codes that will be returned in the table below.

Starting October 14, 2019, accelerated budget delivery will no longer be available for use with search campaigns, shopping campaigns, or shared budgets. This will affect budgets in all versions of the AdWords API, Google Ads API, and Google Ads scripts.

All three developer surfaces will stop accepting ACCELERATED delivery method setting on budgets for search campaigns, shopping campaigns, or shared budgets. Campaigns using accelerated delivery with these campaign and budget types will be automatically migrated over to STANDARD delivery, starting October 7, 2019.

Note: When a new budget is created using the API or scripts, it is shared by default. Thus, a newly created budget will behave as STANDARD. To explicitly create a budget with ACCELERATED delivery, all of the following conditions must be met:

The budget’s isExplicitlyShared field is set to false
The budget’s delivery method is set to ACCELERATED
It is not associated with a search or shopping campaign post creation

Affected API and scripts operations

After this change goes into effect, API clients and scripts will no longer be able to use the ACCELERATED delivery method setting on search campaigns, shopping campaigns, or shared budgets. Any programmatic operations that create or modify such budgets, or that would result in the following states, may result in errors according to the following criteria.

AdWords API Operation
Creating new budget	isExplicitlyShared: true deliveryMethod: `ACCELERATED` Campaign Type: (N/A) Service: `BudgetService` Error: `OperationAccessDenied.ACTION_NOT_PERMITTED`*
Modifying existing budget	isExplicitlyShared: true deliveryMethod: `ACCELERATED` Campaign Type: All Service: `BudgetService` Error: `OperationAccessDenied.ACTION_NOT_PERMITTED`*
Modifying existing budget	isExplicitlyShared: false deliveryMethod: `ACCELERATED` Campaign Type: Search, Shopping Service: `BudgetService` Error: `OperationAccessDenied.ACTION_NOT_PERMITTED`*
Attaching existing budget to campaign	isExplicitlyShared: false deliveryMethod: `ACCELERATED` Campaign Type: Search, Shopping Service: `CampaignService` Error: `OperationAccessDenied.ACTION_NOT_PERMITTED`*

*For the Google Ads API beta, an analogous OperationAccessDeniedError.ACTION_NOT_PERMITTED will be thrown.

If you have any questions about this change, please don’t hesitate to contact us via the AdWords API and Google Ads API Forum or the Google Ads scripts forum.

Adam Ohren, Google Ads API Team

Announcing v2_1 of the Google Ads API beta

2019-08-08T13:11:00.000-07:00

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

Here are the highlights:

Introduced AdService for updating existing ads that were created using AdGroupAdService. Updating ads maintains existing metrics.
Introduced summary rows when retrieving data from GoogleAdService.Search() by setting return_summary_row to true in the request. The summary row contains the report totals.
Introduced the AdGroupAdAssetView resource for querying ad asset metrics.
Introduced the DistanceView resource (equivalent to the User Ad Distance Report in the AdWords API).
Introduced the UserLocationView resource (equivalent to the Geo Performance Report where isTargetingLocation is false in the AdWords API).
Added the ability to retrieve all label resource names associated with the AdGroup resource using AdGroup.labels and with the Campaign resource using Campaign.labels.
Added time_zone, test_account, manager, descriptive_name, currency_code, and id to CustomerClient to make it easier to retrieve customers in an account hierarchy.

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 by August 16. If you have any questions or need additional help, please contact us via the forum.

Nadine Sundquist, on behalf of the Google Ads API Team

Sunset of the Average Position Metric in AdWords and Google Ads APIs

2019-07-25T13:46:00.000-07:00

Update (Jul 30, 2019): clarified the sunset schedule.

Starting the week of September 30, 2019, the average position metric will be sunset. This change was announced this past February in the Google Ads Help Center. The new alternatives were described in this November 2018 blog post. Once the sunset occurs, requests for the average position (AdWords API, Google Ads API) will return NULL values.

In the AdWords API v201809, NULL values are returned as two dashes. In the Google Ads API, NULL values are returned as NullValues.

If you use ValueTrack parameters, we encourage you to remove the ValueTrack parameter {adposition} from your tracking templates. When average position is sunset, the ValueTrack parameter {adposition} will begin returning the empty string.

Note that average position has already been removed from the current beta version of the Google Ads API, but is accessible in the earlier V1_x versions.

In lieu of average position, we recommend you use the new metrics of Impression (Absolute Top) %" and "Impression (Top) %. These are the new metrics:

Absolute Top Metrics
AdWords API	Google Ads API
AbsoluteTopImpressionPercentage	absolute_top_impression_percentage
SearchAbsoluteTopImpressionShare	search_absolute_top_impression_share
SearchBudgetLostAbsoluteTopImpressionShare	search_budget_lost_absolute_top_impression_share
SearchRankLostAbsoluteTopImpressionShare	search_rank_lost_absolute_top_impression_share

Top Metrics
AdWords API	Google Ads API
TopImpressionPercentage	top_impression_percentage
SearchTopImpressionShare	search_top_impression_share
SearchBudgetLostTopImpressionShare	search_budget_lost_top_impression_share
SearchRankLostTopImpressionShare	search_rank_lost_top_impression_share

As always, don't hesitate to reach out to us on the developer forum with any questions.
David Wihl, Google Ads API Team

Campaign IDs and Budget IDs as 64-bit in Google Ads

2019-07-22T05:19:00.000-07:00

Update (Aug 5, 2019): Please also include SharedSet ID in your verification for 64-bit compliance.
Update (Jul 26, 2019): Please also include Asset ID in your verification for 64-bit compliance.

In the AdWords API and Google Ads API, Campaign IDs and Budget IDs are 64-bit signed integers and are of type xsd:long in the AdWords API and INT64 in the Google Ads API. Applications that integrate with the API should handle ID values in that range.

Historically, Campaign and Budget IDs in Google Ads were within the maximum value of 32-bit signed integer, but will soon be exceeding this range. In order to avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
--Stan Grinberg, Google Ads API Team

Upcoming changes to App campaigns

2019-06-11T08:29:00.000-07:00

We will be rolling out the improved version of App campaigns in the AdWords API and Google Ads API over the coming months. Please make sure you get your code ready before the migration of all campaigns to the new structure on August 6, 2019.

What's changing
Once this change is rolled out to a given account, all App campaigns for that account will immediately begin using the new fields. You will no longer use a UniversalAppCampaignSetting, which included both information about the app and references to media and descriptions that would be used for ads in that campaign.

Instead, you will specify an AppCampaignSetting in the Google Ads API (UniversalAppCampaignInfo in the AdWords API), which contains only basic details about the app you want to promote through advertising. All the specific ad-level details will be added in the new AppAdInfo in the Google Ads API (UniversalAppAd in the AdWords API). This improved structure allows you to have a single campaign for each app you want to advertise, and offers the flexibility to have a variety of different ads within that campaign.

For reporting, stats at the ad group level will be available in the Google Ads API only.

Update schedule
For this update, we are rolling out the changes in two phases.

On June 17, 2019, all test accounts will be updated to use the new App campaign settings. Starting on this date, you can write test code against a test account you own to ensure that your code is ready for the full migration.
On August 6, 2019, all Google Ads accounts will be updated to use the new App campaign settings. Make sure that you have tested and deployed your new code to adapt to the changes by this date.

If you have any questions or concerns, please don't hesitate to contact us via our forum.
- Mike Cloonan, Google Ads API Team

Content API for Shopping live webinar on May 31st (Mandarin, Chinese)

2019-05-30T09:30:00.004-07:00

We are running a live webinar this Friday, May 31, on the Content API for Shopping. This webinar is for our Chinese-speaking developers that are interested in using the API to manage products and Shopping ads at scale.

The webinar will cover topics on:

Content API for Shopping use case
Merchant Center setup
Content API features
Best practices
API request/response demo

You will be able to submit questions throughout the live event. We will answer questions during the Q&A session in the webinar.

Note: The webinar content will be delivered in Mandarin, Chinese.

The webinar will begin at 10:00am (China Time, GMT +8) on Friday, May 31, 2019.

Join @ https://www.youtube.com/watch?v=aQ7qzgfTIbo

Please contact us via the Content API forum if you have any questions or need help.

If you’d like to review some of our previous webinars covering the Google Ads API, you can find them at the following links:

Fei Xiang, Google Ads API Team

Migrating from position to impression share bidding strategies in Google Ads

2019-05-29T10:10:00.000-07:00

In June 2019, we will shut off the ability to add new Target Search Page Location and Target Outranking Share bidding strategies. This will affect both the AdWords API and the Google Ads API. Later this year, existing campaigns on these strategies will automatically be migrated to the new Target Impression Share bidding strategy, which offers more flexible and granular controls to optimize for your desired impression share and search page location.

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

Google Ads API Users
Please start using the TARGET_IMPRESSION_SHARE BiddingStrategyType rather than TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED.

If you attempt to create a TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED after they are removed, you will get an error.

AdWords API Users
If you attempt to use the AdWords API to add a TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED bidding strategy after they are removed, you will get an error.

All existing campaigns using the old bidding strategies will be automatically migrated to use Target Impression Share for both APIs. The AdWords API does not support the Target Impression Share bidding strategy, so we recommend migrating to the Google Ads API if you need this functionality.

If you have any questions about this change or any other API feature, please contact us via the forum.
- Mike Cloonan, Google Ads API Team

Join us for a live webinar on Google Ads API and Hotel Ads

2019-05-28T07:27:00.000-07:00

Please join us later this week for a livestream webinar covering the latest Hotel Ads features in the Google Ads API. In particular, we’ll cover using hotel listing groups and leveraging Hotel Ads-specific reporting features. We’ll also be answering some of your questions during the event.

The webinar will begin at 11:00am EDT on Thursday, May 30, 2019.

Join @ https://www.youtube.com/watch?v=omVQ7SAnjJI

As always, please contact us via the Google Ads API forum if you have any questions or need help.

If you’d like to review some of our previous webinars on related topics, you can find them at the following links:

Google Ads API: Intro - https://youtu.be/7ZOETqEzCWU
Google Ads API: Hotel Ads Overview - https://youtu.be/nY6cfIvI-Lg
Google Ads API: Roadmap and migration - https://youtu.be/d-cSJCficyk

Adam Ohren, on behalf of the Google Ads API Team

Announcing v1_3 of the Google Ads API

2019-05-22T12:11:00.002-07:00

Today we’re announcing the v1_3 release of the Google Ads API. With this version, you’ll continue pointing to v1 as your endpoint; however, you'll need to update your client libraries in order to use v1_3 features.

Here are the highlights:

Added support for campaign drafts and experiments with the CampaignDraft and CampaignExperiment resources (equivalent to Campaign Drafts and Experiments in the AdWords API).
Added the ability to retrieve all label resource names associated with the Campaign resource using Campaign.labels.

What resources are available?
The following resources should help you get going with v1_3 of the Google Ads API:

The updated client libraries and code examples will be published by May 24, 2019. If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the Google Ads API Team

Expanding your Shopping ads to additional Google platforms

2019-05-14T12:16:00.000-07:00

YouTube and Google Discover power visually rich experiences and play a part of millions of users’ shopping journeys. Soon your Standard Shopping campaigns will be able to reach users who discover and continue their shopping journey on these additional Google platforms.

We’re excited to announce that Shopping ads (both Product Shopping ads and Showcase Shopping ads) in your standard Shopping campaigns will be eligible to appear on YouTube and Google Discover beginning the week of July 15th, 2019. Shopping ads served on YouTube and Google Discover will be reported under the Google Display Network.

In preparation for this change, standard Shopping campaigns that are enabled for Search Network will be automatically enabled for YouTube and Discover, beginning the week of June 17th, 2019. This means that any standard Shopping campaigns that target the Search Network will automatically enabled to target the Content Network. After this process, developers using the Google Ads API or the AdWords API can give users the ability to opt-in/opt-out. They can do this by changing the campaign target network as follows:

Google Ads API - Modify the NetworkSettings of the standard Shopping campaign to set target_content_network to true or false.
AdWords API - Modify the NetworkSetting of the standard Shopping campaign to set targetContentNetwork to true or false.

Ads with these settings will only be eligible to appear on YouTube and Google Discover from the week of July 15th, 2019. During that week, you may start seeing new metrics as part of your reporting data. Depending on which API you are using you can access the metrics by doing the following:

Google Ads API - Use GoogleAdsService.Search to request reporting data and check the segment field ad_network_type for type CONTENT.
AdWords API - Download the SHOPPING_PERFORMANCE_REPORT and check either of the two segment fields AdNetworkType1, AdNetworkType2 for type CONTENT.

Note: If you would like to upgrade to the Google Ads API from the AdWords API, please see more information our blog.

If you have any questions or need help, please contact us via the forum.
- Ian Ballantyne, on behalf of the Google Ads API Team