Today we’re releasing an update to the Display & Video 360 API which includes the following features:

• A new insertion order targeting service and bulk list method enabling the retrieval of insertion order targeting.
• Additional output-only fields mp3Audio and oggAudio for third-party audio creatives.
• Support for more performance goal types to assign to insertion orders and campaigns, including click and impression conversion rate performance goals.

Read More

Today we’re releasing an update to the Display & Video 360 API which includes the following features:

• A new insertion order targeting service and bulk list method enabling the retrieval of insertion order targeting.
• Additional output-only fields mp3Audio and oggAudio for third-party audio creatives.
• Support for more performance goal types to assign to insertion orders and campaigns, including click and impression conversion rate performance goals.

More detailed information about this update can be found in the Display & Video 360 API release notes.

Before using these new features, make sure to update your client library to the latest version.
If you run into issues or need help with these new features, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

The sunset of deprecated services in the DoubleClick Bid Manager (DBM) API, originally scheduled for February 26, 2021, has been postponed to April 15, 2021. The deprecated services scheduled for sunset include the entirety of ...Read More

The sunset of deprecated services in the DoubleClick Bid Manager (DBM) API, originally scheduled for February 26, 2021, has been postponed to April 15, 2021. The deprecated services scheduled for sunset include the entirety of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service.

Prior blog posts regarding this sunset give instructions on how to migrate from these deprecated services to either the DBM API v1.1 Reporting service or the Display & Video 360 (DV360) API. Consult these previous announcements for more information.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Update (March 12, 2021): Updated the language in this post to emphasize that this change is a reorganization of existing features.
The v6 release of the Google Ads API added support ...Read More

Update (March 12, 2021): Updated the language in this post to emphasize that this change is a reorganization of existing features.
The v6 release of the Google Ads API added support for Maximize conversions and Maximize conversion value bid strategies in Search campaigns. This includes a new read-only MaximizeConversions.target_cpa field. Bid strategies having either this new target_cpa field or the read-only MaximizeConversionValue.target_roas field act identically to TargetCpa and TargetRoas bid strategies, respectively. In the future, bid strategies for Search campaigns will be reorganized for simplification.

What’s changing
Starting in April 2021, the Google Ads UI will start allowing some users to create MaximizeConversions and MaximizeConversionValue bid strategies with their target_cpa and target_roas fields set, in lieu of the old-style TargetCpa and TargetRoas bid strategies. This change will gradually ramp-up to more accounts over time.

There will be no impact to bidding behavior due to these changes. The MaximizeConversions bid strategy using the new optional target_cpa setting will still behave like the TargetCpa strategy does today, and likewise, MaximizeConversionValue using the new optional target_roas setting will behave like TargetRoas.

Before	After
TargetRoas	MaximizeConversionValue.target_roas
TargetCpa	MaximizeConversions.target_cpa

The target_roas and target_cpa fields will remain read-only to API users until a future version of the API enables mutate functionality. Be on the lookout for such an announcement in the API’s release notes.

What to do
Developers should ensure their code treats Search campaigns that have MaximizeConversions with a set target_cpa field and MaximizeConversionValue with a set target_roas field the same way it treats TargetCpa and TargetRoas bid strategies, respectively.

Developers can continue to create TargetCpa or TargetRoas bid strategies or manage existing TargetCpa or TargetRoas bid strategies, even after we introduce the new representations in April. We will publish an update on the blog when the above fields are mutable, along with several months' notice before we start moving to the new representations of the bid strategies for existing Search campaigns.

If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.
Adam Ohren, Google Ads API Team

On April 5, 2021, support for Showcase Shopping ads will be removed from the AdWords API. Users will no longer be able to create or update the following Showcase Shopping objects, and attempts to do so will result in the following errors.Read More

On April 5, 2021, support for Showcase Shopping ads will be removed from the AdWords API. Users will no longer be able to create or update the following Showcase Shopping objects, and attempts to do so will result in the following errors.

Object	Error
AdGroups with adGroupType SHOPPING_SHOWCASE_ADS	OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE
AdGroupAds containing ShowcaseAds	OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE

Any remaining Showcase ad groups will be set to REMOVED status, and remaining AdGroupAds containing ShowcaseAds will be set to DISABLED status and stop serving. Developers can still retrieve historical metrics for these ads and ad groups by fetching reports that explicitly filter to include REMOVED or DISABLED objects.

This change only affects AdWords API users. Management of Showcase Shopping ads is not supported by Google Ads API or Google Ads scripts.

If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.
Adam Ohren, Google Ads API Team

Read More

We're happy to announce that v202102 of the Google Ad Manager API is available starting today. Upgrade to this version to take advantage of new functionality, including CreativeSizeType.IGNORED for click-tracking entities, where size doesn't matter, or for entities that allow all requested sizes, where the size represents all sizes.

Additionally, there are several highly-requested report dimensions added in v202102.

Dimension name	Report data break down
BROWSER_NAME	Name and version number of the user's browser
VIDEO_PLACEMENT_NAME	Video placement (e.g., in-article, in-stream, and in-feed)
CLASSIFIED_YIELD_PARTNER_NAME	Detected yield partner name, as classified by Google
DOMAIN	Top private domain, such as "example.co.uk" (excludes subdomains)

Finally, if you use the Ad Manager API to create video LineItems, v202102 now requires that LineItem.videoMaxDuration is greater than 0. This new validation applies to newly created video LineItems as well as updates. If you think you might be affected, you should update any code that creates video LineItems to set videoMaxDuration to be greater than 0 and scan your network for existing video LineItems with videoMaxDuration set to 0.

For the full list of changes for v202102 and all other active API versions, check the release notes. Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

 - Donovan McMurray, Ad Manager API Team

Starting March 25, 2021, we are rolling out a change in the Google Ads API and AdWords API, to require advertisers who apply to the latest Personalized advertising policies ...Read More

Starting March 25, 2021, we are rolling out a change in the Google Ads API and AdWords API, to require advertisers who apply to the latest Personalized advertising policies to acknowledge these changes in the Google Ads UI. Campaign creation requests via the API will be rejected for these advertisers until they click to accept the changes.

Who will be impacted?
Advertisers promoting housing, employment, or credit products or services to audiences in the U.S. and Canada will be impacted.

What's changing?
You will receive the following errors when trying to create new campaigns via the API if the new policies have not been acknowledge:

API Version	Error Code	Error Message
Google Ads API v6.1	CampaignError.HEC_AGREEMENT_REQUIRED	Customers with Housing, Employment, or Credit ads must accept updated personalized ads policy to continue creating campaigns
Google Ads API (older versions)	CampaignError.UNKNOWN	Same as above.
AdWords API (v201809)	CampaignService.OperationAccessDenied	Same as above.

What should you do?

• Before March 25, 2021, make sure to add support for the new policy errors in your application.
• Ensure that the account administrators have accepted the policy changes in the Google Ads UI following this guide.

If you have any questions or need additional help, contact us through the Google Ads API and AdWords API forum or at googleadsapi-support@google.com.
Fan Wang, Google Ads API Team

Today, we’re announcing the v6.1 release of the Google Ads API. To use some of the v6.1 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This version has no breaking changes.Read More

Today, we’re announcing the v6.1 release of the Google Ads API. To use some of the v6.1 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This version has no breaking changes.

Here are the highlights:

• Retrieving and managing recommendations for adding responsive search ads.
• Added support for managing user invitations for a Google Ads account.
• Added Feed, FeedItem, CampaignFeed, AdGroupFeed, and AdGroupAd resources to the list of resource types returned in queries against the change_event resource.
• New conversion metrics by conversion date.
• New call_view resource for reporting on call extensions and call only ads.

Where can I learn more?
The following resources can help you get started:

• Release Notes
• Guides
• Reference

If you have any questions or need additional help, contact us via the forum.
Josh Radcliff, on behalf of the Google Ads API Team

Today, we're announcing the general release of Publisher Ads Audits for Lighthouse v1.4.1. The major highlights of this release are:

• New audits to check for Google Publisher Tag errors and warnings.
• Updated thresholds for ad and bid requests when using simulated throttling.
• Updates to support Lighthouse v7.0.0.

Read More

Today, we're announcing the general release of Publisher Ads Audits for Lighthouse v1.4.1. The major highlights of this release are:

• New audits to check for Google Publisher Tag errors and warnings.
• Updated thresholds for ad and bid requests when using simulated throttling.
• Updates to support Lighthouse v7.0.0.

A number of smaller enhancements and fixes are also included. For complete details, see the changelog on GitHub. Additional Lighthouse changes included in this release can be found in the v6.5.0 release notes.

Helping ensure Google Publisher Tags are used correctly

The Google Publisher Tag (GPT) library is designed with flexibility in mind, to support displaying ads across the widest variety of sites. However, this flexibility means that sites sometimes end up using the library in unexpected ways or provide configurations that don't quite work the way they intend. Although the library throws various warnings and errors when these sorts of issues are encountered, they can be easy to miss if you're not looking for them. To help raise awareness, we're introducing two new audits:

• deprecated-api-usage - this audit looks for usage of GPT API features that have been deprecated. These features may be removed in the future and are no longer actively maintained. Consult the GPT release notes for alternatives to use.
• gpt-errors-overall - this audit surfaces all warnings and errors thrown by GPT during page load. The severity of these issues can vary depending on a number of factors, so you need to review the results and decide whether there's anything that needs to be addressed for your site.

These new audits are being presented as informational only in this release, so they won't affect scores right now. However, we plan to give these audits weights in a future release. Users are therefore encouraged to address any newly uncovered issues now, to avoid a negative impact on their scores later.

Try it out and let us know what you think

Publisher Ads Audits v1.4.1 is available to use right now. You can try generating an updated report from the web app, or grab the latest CLI release from GitHub or npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 91 release (est. May 2021).

Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our GitHub repo.

 - Jonathon Imperiosi, Publisher Ads Audits Team

On March 22, 2021 we will begin to sunset portfolio (shared) Enhanced cost-per-click (ECPC) bid strategies. The following behaviors will be blocked in all versions of both the AdWords API and the Google Ads API ...Read More

On March 22, 2021 we will begin to sunset portfolio (shared) Enhanced cost-per-click (ECPC) bid strategies. The following behaviors will be blocked in all versions of both the AdWords API and the Google Ads API:

• Creating new portfolio ECPC strategies.
• Attaching portfolio ECPC strategies to campaigns.

Note that standard (non-portfolio) ECPC strategies will not be affected.

	Affected Portfolio Enhanced CPC Strategies
Google Ads API	Bidding_strategy.type = BiddingStrategyType.ENHANCED_CPC
AdWords API	SharedBiddingStrategy.type = MANUAL_CPC, SharedBiddingStrategy.biddingScheme.enhancedCpcEnabled = TRUE

Change Description
Any operation creating new portfolio ECPC strategies, or attaching a portfolio ECPC strategy to a campaign, will generate one of the following errors:

	Error Upon Creation	Error Upon Attaching
Google Ads API	BIDDING_STRATEGY_NOT_SUPPORTED	CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN
AdWords API	BIDDING_STRATEGY_NOT_SUPPORTED	CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN

Migration Description
In the future, we will remove the portfolio ECPC strategy entirely, in favor of standard ECPC. In order to prepare for this change, you can proactively migrate all your portfolio ECPC strategies to standard ECPC strategies using the instructions below.

All remaining portfolio ECPC campaigns and strategies will be automatically migrated at a later date. We will post an update on this blog ahead of that migration.

Self-migration using Google Ads API
Update a campaign by using CampaignService.MutateCampaigns() to set its manual_cpc.enhanced_cpc_enabled field to true. Be sure to set the update_mask on your request to match:

operations: [
  {
    update: {
      resource_mame: customers/CUSTOMER_ID/campaigns/CAMPAIGN_ID,
      manual_cpc: {
        enhanced_cpc_enabled: true
      }
    },
    update_mask: manual_cpc.enhanced_cpc_enabled
  }
]

Self-migration using AdWords API
Update a campaign by using CampaignService.mutate() to set its biddingStrategyType to MANUAL_CPC, and its biddingScheme.enhancedCpc field to true:

<operations>
  <operator>SET</operator>
  <operand>
    <id>CAMPAIGN_ID</id>
    <biddingStrategyConfiguration>
      <biddingStrategyType>MANUAL_CPC</biddingStrategyType>
      <biddingScheme>
        <enhancedCpcEnabled>true</enhancedCpcEnabled>
      </biddingScheme>
    </biddingStrategyConfiguration>
  </operand>
</operations>

If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.
Adam Ohren, Google Ads API Team

On February 4, 2021, we announced upcoming changes to phrase match and broad match modifier. To simplify the keyword portfolio and help advertisers reach more relevant user searches, we are bringing behaviors of broad match modifier (BMM) into phrase match, and phasing out support for BMM. This will be a gradual rollout that will change the back end processing for keyword match types ...Read More

On February 4, 2021, we announced upcoming changes to phrase match and broad match modifier. To simplify the keyword portfolio and help advertisers reach more relevant user searches, we are bringing behaviors of broad match modifier (BMM) into phrase match, and phasing out support for BMM. This will be a gradual rollout that will change the back end processing for keyword match types (AdWords API, Google Ads API, Google Ads scripts) in order to simplify keywords and make it easier to reach relevant customers.

The updated phrase match will contain the best of both match types: the control of phrase match, and the expanded reach of broad match modifier. Both phrase and BMM keywords will continue to work and beginning February 18, 2021 for our first wave of languages (English, German, Spanish, French, Italian, Dutch, Portuguese, Russian), keywords using the phrase or BMM notations will begin to use the updated phrase match behavior. In Q2 we will begin the same process for all other Google Ads languages, and expect to complete in July 2021.

In July 2021, once all languages have the updated phrase match behavior, advertisers will be prevented from creating new BMM keywords (but any legacy BMM keywords will still work).

The changes to phrase match and BMM will not impact negative keyword match types.

How does this change affect the AdWords API, Google Ads API and Google Ads scripts?
Starting in July 2021, you will no longer be able to create new BMM keywords (i.e. matchType of BROAD and keyword text in which tokens begin with +). We will do a separate reminder announcement as we get closer to this milestone.

What impact should advertisers expect?
Impact will depend on each advertiser's usage of phrase and/or BMM and how comprehensive their query coverage is.

• Advertisers predominantly using phrase match are expected to see an incremental increase in clicks and conversions
  • This is due to the additional queries to which these keywords will now be eligible to match. For example, “holidays in zambia” as a phrase keyword will now begin to match to “holiday spots in zambia”, which was previously only eligible for BMM.
• Advertisers predominantly using BMM are expected to see a slight decrease in clicks and conversions
  • The majority of this loss is from BMMs where the modifier was only applied to part of the keyword, e.g. tennis +shoes.
  • In addition we are now considering word order when it’s important to the meaning of the keyword, so some matches that previously matched to BMM will be filtered out.

What should I do?
Advertisers may experience traffic shifts. User queries that previously matched to keywords in one match type may become eligible to match to a phrase or legacy BMM keyword causing the volume to move across keywords. For this reason it is important for advertisers to monitor their accounts and adjust budgets if needed to accommodate additional volume. Additional best practices are outlined in the announcement.

If you have any questions or need additional help, contact us via the forum.
David Wihl, Google Ads API Team

The InvoiceService is now available for all API users starting with version 6 of the Google Ads API. Earlier API versions will continue to only support this service for allowlisted accounts.Read More

The InvoiceService is now available for all API users starting with version 6 of the Google Ads API. Earlier API versions will continue to only support this service for allowlisted accounts.

This service retrieves the monthly invoices of Google Ads accounts. Each returned Invoice comes loaded with data (for example: adjustments, regulatory costs, taxes, account budgets) and can be downloaded as a PDF file. Google Ads manager accounts can use the data to automatically reconcile customer invoices. To get started, read through our dedicated guide.

If you have any questions or need additional help, contact us through the forum or at googleadsapi-support@google.com.
Pierrick Voulet, Google Ads API Team

On March 8, 2021 we're disabling mutates to the Lead category in the AdWords API. The Google Ads API ConversionActionCategory is not affected. This is a follow-on to the conversion category changes ...Read More

On March 8, 2021 we're disabling mutates to the Lead category in the AdWords API. The Google Ads API ConversionActionCategory is not affected. This is a follow-on to the conversion category changes and expanded conversion categories announced in September 2020, which provided a finer grained categorization of conversions.

We are making this change because we are seeing some advertisers change their new category conversion types back to Lead category through the AdWords API, resulting in ambiguity since multiple new categories map to this old category. The following table summarizes how the AdWords API will respond to mutates that set the conversion category to Lead.

Existing Category	AdWords API READs (Existing behavior)	AdWords API Mutate to LEAD Response
Lead	Lead	OK
“Old” category	“Old” category	ERROR
“New” lead category	Lead	OK
“New” non-lead category	“Old” category	ERROR

Since the AdWords API does not support all the new conversion categories, reading in a new fine grained Lead conversion category will be mapped to Lead upon read, but will continue to be persisted as the finer grained new category. If read through the Google Ads UI or Google Ads API, the new conversion category will be accurately retrieved.

As a recap from our September 2020 announcement, here is the mapping of new conversion category types to existing AdWords API ConversionTracker.Category enum values:

New Conversion Category	Mapping to ConversionTracker.Category
Add to cart	LEAD
Begin checkout	LEAD
Purchase	PURCHASE
Subscribe	PURCHASE
Sign-up	SIGNUP
Phone call lead	LEAD
Imported lead	LEAD
Submit lead form	LEAD
Book appointment	LEAD
Request quote	LEAD
Get directions	LEAD
Outbound click	LEAD
Contact	LEAD
Download	DOWNLOAD
Page view	PAGE_VIEW
Engagement	DEFAULT
Store visit	DEFAULT
Store sale	PURCHASE
Other	DEFAULT

If you have any questions or need additional help, contact us via the forum.
David Wihl, Google Ads API Team