Google Ads Developer Blog: 2023

Changes in dynamic ad targets reporting

Thursday, September 28, 2023

Starting on September 20, 2023, we’ve started rolling out a backend improvement on Google Ads dynamic ad targets reporting to include criteria that were removed and then added back as negative. Before this change, report queries for web page criteria (that is, queries against the webpage_view resource) requesting historical data did not include criteria that were removed and then added back as negative. This resulted in unexpected values in reports for the time frame when these criteria were accruing metrics (that is, when they were targeted and had negative = false), because the metrics they accrued in this time period were not returned in report query results. The change only affects cases where a positive criterion was removed and added back as negative: all other criteria will return the same values they did before this change. After this change is released, criteria metrics will take into account removed criteria and criteria that were re-added as negative. Required actions You don’t need to change anything in your GAQL queries; however, be aware that you may notice differences in criteria reporting after this change due to the correct values being reported. If you have any questions or concerns, please don't hesitate to contact us via the forum.

- Mattia Tommasone, Google Ads API Team

Google Ads Shopping Campaign Enhanced CPC Deprecation

Thursday, September 21, 2023

Starting in early October 2023, any Shopping campaigns using Enhanced cost-per-click (eCPC) will behave as if they are using Manual cost-per-click (CPC) bidding. Enhanced CPC was the first Smart Bidding strategy launched by Google over 10 years ago. It has been replaced by more advanced bidding strategies such as Target ROAS and Maximize conversion value, as well as fully automated campaigns like Performance Max. What happens if I change nothing? If you choose to not make changes to your campaign by October 2023, it will operate as if it's using Manual CPC bidding. All your existing campaigns using eCPC will continue serving using the manual bids that you set. If you set ManualCpc.enhanced_cpc_enabled to true in a Shopping campaign, the API ignores the setting and the campaign will only use Manual CPC bidding. What should I change? If you want to continue to use Manual CPC, remove any code that sets ManualCpc.enhanced_cpc_enabled to true for Shopping campaigns. We recommend these alternatives to Manual CPC:

Target ROAS

Our newest fully automated solution: Performance Max campaigns

Where can I get support? If you have questions, please reach out to us on the forum or at googleadsapi-support@google.com.

Nadine Wang, Google Ads API Team

Google Ads API support for importing and editing conversions from Google Analytics

Thursday, September 21, 2023

What's changingOctober 9, 2023ConversionAction

An update that modifies status, primary_for_goal, category, name, or value_settings.

A remove that removes the conversion action.

Why this is importantcreate a link

Importing each conversion from your GA4 property into your Google Ads account by modifying its status field from HIDDEN to ENABLED.

Configuring the primary_for_goal and category fields of each imported conversion to indicate how it should impact Google Ads bidding and reports.

conversion goalsConversionAction

name

value_settings

ConversionActionremoveupdateConversionActionWhat you should doConversionActionOperationMUTATE_NOT_ALLOWEDupdateremovetypeConversionActionGOOGLE_ANALYTICS_4_CUSTOMGOOGLE_ANALYTICS_4_PURCHASEHow to get helpsupport page

- Josh Radcliff, Google Analytics and Google Ads API Team

Buy on Google For Search and Shopping Deprecation

Wednesday, September 20, 2023

Buy on Google for Search and Shopping will no longer be available starting September 26, 2023. All Merchant and Consumer support will end for Buy on Google on Search on November 25, 2023. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data. See below for the specific timeline of when Buy on Google methods will no longer be available for the Search and Shopping program. June 28, 2023 onwards:

buyongoogleprograms.requestreview

buyongoogleprograms.onboard

buyongoogleprograms.activate

buyongoogleprograms.pause

September 30, 2023:

buyongoogleprograms.get

buyongoogleprograms.patch

October 31, 2023: All the orders related resources (orders, orderinvoices, orderreports, orderreturns, ordertrackingsignals) and all their underlying methods. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data. If you are currently using the Buy on Google endpoints for Search and Shopping via the Content API, you will need to stop using these services for Search and Shopping before the dates listed above, as your requests will start to fail after that date. If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Performance Max: create listing groups using batch processing

Tuesday, September 19, 2023

What’s New Starting on October 4, 2023, AssetGroupListingGroupFilters can be created asynchronously using batch processing with the Google Ads API. If you use BatchJobService to create AssetGroupListingGroupFilter entities and other Performance Max resources in a single request, errors in the listing group tree creation will not block the creation of the remaining entities. However, the operations to create a listing group tree will still be atomic. This means that if any operation related to the creation of a listing group tree returns an error, all operations related to that listing group tree will also fail, save a few caveats, which are detailed in this Jobs & listing group filters guide. This update does not change the behavior of any existing batch jobs that do not include operations that create listing group filters. Previous Behavior Prior to October 4, 2023, AssetGroupListingGroupFilters could only be created synchronously using the GoogleAdsService.Mutate or AssetGroupListingGroupFilterService.MutateAssetGroupListingGroupFilters method. Requests using the GoogleAdsService.Mutate method are always atomic when they contain AssetGroupListingGroupFilterOperation operations. This is because partial_failure is not supported for these operations, which means that an error in listing group tree creation would block all other operations in the request. If you tried creating AssetGroupListingGroupFilter entities prior to October 4, 2023 using batch processing, you would receive a MutateError.OPERATION_DOES_NOT_SUPPORT_PARTIAL_FAILURE error. Change Rationale Batch processing is a powerful feature in the Google Ads API that allows you to dispatch a set of operations, which may be interdependent, to multiple services without synchronously waiting for the operations to complete. We have made batch processing available for AssetGroupListingGroupFilters in response to your feedback to provide another option for creating listing group trees asynchronously and without blocking other operations in the same request. Implementation Details In order to add an AssetGroupListingGroupFilter using a batch job:

Create a MutateOperation containing an AssetGroupListingGroupFilterOperation. This is no different than creating a MutateOperation using the GoogleAdsService.Mutate service.

Add the MutateOperation to the batch job as you would with any other type of operation.

The example below demonstrates the process of adding a single AssetGroupListingGroupFilter to an existing batch job. See the Creating Shopping Listing Groups guide to learn more about creating product partition trees using AssetGroupListingGroupFilter entities. // Constructs the AssetGroupListingGroupFilter. AssetGroupListingGroupFilter listingGroupFilter = AssetGroupListingGroupFilter.newBuilder() .setAssetGroup(assetGroupResourceName) .setType(ListingGroupFilterType.UNIT_INCLUDED) .setVertical(ListingGroupFilterVertical.SHOPPING) .build(); // Constructs the operation to create the AssetGroupListingGroupFilter. MutateOperation operation = MutateOperation.newBuilder() .setAssetGroupListingGroupFilterOperation( AssetGroupListingGroupFilterOperation .newBuilder() .setCreate(listingGroupFilter)) .build(); // Sends a request to add the operation to the batch job. AddBatchJobOperationsResponse response = batchJobServiceClient.addBatchJobOperations( AddBatchJobOperationsRequest.newBuilder() .setResourceName(batchJobResourceName) .addMutateOperations(operation) .build()); The following resources contain additional information to help you with your integration:

Jobs & listing group filters guide

Listing groups guide

Batch processing guide

Improving Performance Max integrations Blog Series This article is part of a series that discusses new and upcoming features that you have been asking for. We’ll cover what’s new and how it differs from the current implementation approach. Keep an eye out for further updates and improvements on our developer blog, continue providing feedback on Performance Max integrations with the Google Ads API, and as always, contact our team if you need support.

- Devin Chasanoff, on behalf of the Google Ads API Team

Planned Content API maintenance from 15:00 UTC to 17:00 UTC on September 28, 2023

Thursday, September 14, 2023

The Content API for Shopping will undergo planned maintenance on September 28, 2023, from 15:00 to 17:00 UTC.forum

Benji Rothman, Content API for Shopping Team

Introducing a new way to discover Display & Video 360 bulk tools

Wednesday, September 6, 2023

Today we’re announcing a new guide to help Display & Video 360 users discover available bulk tools that they can use to optimize their integrations. The guide offers a high-level overview of each of the following tools that allow you to integrate with Display & Video 360 at scale:

Display & Video 360 Interface Bulk Features

Display & Video 360 API

Structured Data Files

Display & Video 360 API BigQuery Connector

Bid Manager API

Reporting Data Transfer

The guide also provides a recommendations page that can help you choose the right bulk tool based on your needs and circumstances and a page proposing potential platform-wide integrations using multiple bulk tools. You can navigate to this new guide from the existing Display & Video 360 API, Bid Manager API, or Reporting Data Transfer documentation using the Discover Bulk Tools tab at the top of the page.

- Trevor Mulchay, Display & Video 360 API Team

Developer token-less experience for Google Ads API

Tuesday, September 5, 2023

We are accepting early sign-ups for a Google Ads API pilot program that lets you make API calls without requiring a developer token. Your API access levels will instead be identified by your Google Cloud project IDs and Google Cloud organizations. This pilot provides benefits such as:

No more need to secure developer tokens

Better integration with Google Cloud console API quota management tools

Refer to our developer documentation to learn more about this feature. If you have any questions, please contact us on the forum.

- Anash P. Oommen, Google Ads API Team

August 2023 update to Display & Video 360 API v2

Wednesday, August 30, 2023

Today we’re announcing the August 2023 update to Display & Video 360 API v2. This update includes the following features:

A new effectiveContentCategory field that surfaces the YoutubeAndPartnersContentCategory used by a YouTube & Partners line item when serving ads. When values are set at the advertiser and line item level, the stricter category is applied and will be reflected in this field.

Support of two new bidding strategy types for YouTube & Partners line items.

Support of two new exchanges.

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 need help with these new features, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Google Ads API v12 sunset reminder

Monday, August 28, 2023

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

Upgrading to the newest version

Release notes

Google Cloud Console

Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.

Click on Google Ads API in the table.

On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v12.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.

(Optional) Click on the time frame at the top right of the page if you need to change it.

forumgoogleadsapi-support@google.com

- Thanet Knack Praneenararat, Google Ads API Team

Launching the Merchant Support Service

Thursday, August 24, 2023

Content API for ShoppingMerchantSupportdeveloper guide

Render account issues: provides UI elements with text in the language you select to display account issues to your merchants and redirect link to Merchant Center for merchants to request a re-review or perform other actions

Render product issues: provides UI elements with text in the language you select to display product issues to your merchants and redirect link to Merchant Center for merchants to request a re-review or perform other actions

MerchantSupportMerchantSupportMerchantSupportforum

Benji Rothman, Content API for Shopping Team

Deprecation of Structured Data Files v5.4

Thursday, August 24, 2023

Today we’re announcing the deprecation of Structured Data Files (SDF) v5.4. This version will be fully sunset on February 27, 2024. Please migrate to v6, the most recent version, by the sunset date. Once v5.4 is sunset::

The default version of partners and advertisers using those versions will be updated to the oldest supported version, v5.5.

sdfdownloadtasks.create requests declaring the sunset versions in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing v202308 of the Google Ad Manager API

Tuesday, August 22, 2023

We're pleased to announce that v202308 of the Google Ad Manager API is available starting today, August 23, 2023. This release brings support for new ThirdPartyMeasurementSettings providers. For the full list of changes, check the release notes. Feel free to contact us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

Announcing v14_1 of the Google Ads API

Wednesday, August 9, 2023

Google Ads APIclient libraries

Added new recommendation types:

Added support for search terms insights to show information on how customers are searching and engaging with your business on Google. Insights are available as two new views: customer_search_term_insight and campaign_search_term_insight. We also released new segments and metrics that support grouping the data into search categories and subcategories.

You can now use Customer.customer_agreement_setting to check if the customer has accepted the lead form term of service.

Added primary_status and primary_status_reasons to AssetGroup and AssetGroupAsset to provide insight into why an asset group or an asset group asset is not serving or not serving, respectively. For AssetGroupAsset, primary_status_details is also available.

Added new fields to Invoice and AccountSummary which return information on export charges.

(Allowlisted accounts only) Added DiscoveryCampaignSettings that contain upgraded_targeting. When you set this field to true, you can add a location and a language as an ad group criterion to that campaign.

(Allowlisted accounts only) Added support for Discovery video responsive ad:

New ad type: AdType.DISCOVERY_VIDEO_RESPONSIVE_AD
New ad info: DiscoveryVideoResponsiveAdInfo

Where can I learn more?

Release Notes

Guides

Reference

forum

- Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Change to updates of Google Ads custom audience types

Tuesday, August 8, 2023

Starting September 27, 2023 you will see a change if you use custom audiences. You will no longer be able to update a custom audience type once you create the custom audience. For example, if you set the type to AUTO or INTEREST, then you cannot update it to the type SEARCH in the Google Ads API. This change ensures that your campaign continues to serve by making sure that your custom audience remains eligible. What do I need to change? Modify your code so it avoids attempting to update the type of an existing CustomAudience. If your code attempts to update the type field after September 27, 2023 then the API will return a CustomAudienceError.INVALID_TYPE_CHANGE error. Where can I get support? If you have questions, please reach out to us on the forum or at googleadsapi-support@google.com.

Nadine Wang, Google Ads API Team

We’ve Made Updates to the User Messaging Platform SDK APIs

Monday, August 7, 2023

In case you missed it, we announced new consent management platform requirements for serving ads in the EEA and UK. Beginning January 16, 2024, Google will require all publishers to use a Google-certified consent management platform (CMP) when serving ads to users in the European Economic Area or the UK. In addition to growing our list of certified CMPs, we explored how to improve the User Messaging Platform (UMP) SDK developer experience for those who choose to use Google’s consent management solution. We are excited to share several updates in the latest iOS and Android versions that we think will streamline your integration. Loading and presenting a consent form The latest UMP SDK release introduces a new API, loadAndPresentIfRequired(), that consolidates the existing individual load and present consent form methods into a single method. The new API loads a consent form and if consent is required, automatically presents the consent form. This method is intended to be used at the beginning of a new app session. Here is a code example of how to use the new API on iOS: class ViewController: UIViewController { private var isMobileAdsStartCalled = false override func viewDidLoad() { super.viewDidLoad() UMPConsentInformation.sharedInstance.requestConsentInfoUpdate(with: parameters) { [weak self] requestConsentError in guard let self else { return } // Call the helper method once consent information has been updated. UMPConsentForm.loadAndPresentIfRequired(from: self) { [weak self] loadAndPresentError in guard let self else { return } if UMPConsentInformation.sharedInstance.canRequestAds { self.startGoogleMobileAdsSDK() } } } // canRequestAds will be true if consent was gathered in the previous session. if UMPConsentInformation.sharedInstance.canRequestAds { startGoogleMobileAdsSDK() } } private func startGoogleMobileAdsSDK() { DispatchQueue.main.async { guard !self.isMobileAdsStartCalled else { return } self.isMobileAdsStartCalled = true // Initialize the Google Mobile Ads SDK. GADMobileAds.sharedInstance().start() // Request an ad. GADInterstitialAd.load(...) } } }Checking when to request ads We added a new boolean property canRequestAds to use as a check before initializing the Google Mobile Ads SDK and requesting ads. canRequestAds returns true when the consent status is either OBTAINED or NOT_REQUIRED; as a result you don’t need to implement any enum checking yourself. You should use the canRequestAds API in two places (as seen in the code snippet above):

Once consent has been gathered in the current session.

Immediately after you have called requestConsentInfoUpdate. It is possible consent has been gathered in the previous session in which case it is not necessary to wait for the callback to finish.

Checking privacy options requirement status GDPR requires that publishers allow users to withdraw their consent choices at any time. It should be as easy to withdraw consent as it is to gather consent. To simplify this process, we have added two new APIs:

privacyOptionsRequirementStatus to determine whether you should include a UI element that can re-present the consent form, such as a button in your application’s settings page.

presentPrivacyOptionsForm() to show the form so the user can update their consent status at any time.

Here is a code example of how to use the new APIs on iOS: // Show a privacy options button if required. private var isPrivacySettingsButtonEnabled: Bool { return UMPConsentInformation.shared.privacyOptionsRequirementStatus == .required } // Present the privacy options form when a user interacts with your app. @IBAction func privacySettingsTapped(_ sender: UIBarButtonItem) { UMPConsentForm.presentPrivacyOptionsForm(from: self) { [weak self] formError in guard let self, let formError else { return } // Handle the error. } }Developer resources We updated our AdMob banner samples applications for iOS and Android to showcase integrating the UMP SDK. Keep an eye out as we add UMP SDK support to the rest of our samples soon. Also take a look at our iOS and Android developer documentation for instructions on how to implement the UMP SDK. If you have any questions or need additional help integrating the UMP SDK, please contact us via the developer forum.

- Justin Malandruccolo, Mobile Ads Developer Relations

Upcoming permission changes to MerchantLinkService in the Google Ads API

Monday, August 7, 2023

What’s Changing Starting the week of September 4, 2023, MerchantLinkService.MutateMerchantCenterLink method will fail with an AuthorizationError.ACTION_NOT_PERMITTED error for authorized users without Admin access levels. Required Actions If your application mutates Merchant Center links using the MutateMerchantCenterLink method, review the account permissions of the users authorizing API calls and update their permissions appropriately to ensure they have the required access levels. Refer to the help center guide for instructions. Change Rationale This change will align the Google Ads API behavior with other products such as the Google Ads UI and Google Ads Editor, which only allow Administrator users to mutate Merchant Center links. Currently, the Google Ads API allows users with Standard Access levels but without Admin access level permissions to mutate Merchant Center links using the MerchantLinkService. If you have any questions, please reach out to us on the forum.

- Anash P. Oommen, Google Ads API Team

Image and Location Assets in New Accounts

Monday, July 24, 2023

What’s changing? On July 6, 2023 we announced the auto-migration of image and location extensions to assets. Once the auto-migration starts on August 2, 2023, new accounts will only be able to create image and location assets and not extensions. New accounts will be treated as accounts that have been migrated. How do I verify my account? Use the following fields from v13 or greater in the Customer resource to track the status of your account:

bool image_asset_auto_migration_done

string image_asset_auto_migration_done_date_time

bool location_asset_auto_migration_done

string location_asset_auto_migration_done_date_time

What if I try to create an extension on a new or migrated account? If your account has been migrated or is new and you attempt to create an extension the mutate request will be rejected and you will receive the error: LEGACY_EXTENSION_TYPE_READ_ONLY If you have any questions, please reach out to us on the forum.
Bob Hancock, Google Ads API Team

Effectively use the Attribution Reporting API for ad measurement

Wednesday, July 19, 2023

Overview Historically, ad-tech providers have used third-party cookies (3PC) as a mechanism for conversion measurement, and for attributing conversions to ad interactions. Conversion measurement provides critical ad performance data to advertisers, and helps optimize auction-based bidding strategies. Currently, the online advertising ecosystem is pivoting towards improved ways to protect user privacy. Chrome’s Attribution Reporting API (ARA), a part of the larger Privacy Sandbox initiative, offers an alternative for measurement after the third-party cookie deprecation in 2024. Ad-tech providers, including Google’s ads platforms, should consider adopting the ARA to maintain high-quality conversion measurement and support the pivot toward user privacy protection. Google Ads has made significant investments to use the ARA more effectively and to help advertisers achieve more accurate measurement. We encourage other ad-tech providers to integrate with the ARA, configure the integration to retrieve the data they need, and process the ARA's output to help maintain accurate measurement after the planned third-party cookie deprecation in 2024. Goals of the ARA The ARA has two goals:

Protect users’ cross-site and cross-app identities from ad-tech providers, advertisers, publishers and other entities by using differential privacy techniques, such as aggregation, or adding an element of noise to the data.

Provide useful measurement information to ad-tech providers, advertisers, and publishers.

The ARA represents a change to both the format and granularity of conversion data available to ad-tech providers. As a result, ad-tech providers must change their current measurement protocols in order to start leveraging the ARA. A glimpse into our approach Ad-tech providers who participate in the Privacy Sandbox initiative receive data from the ARA in two forms: event-level reports and aggregate summary reports. This way, two independent views of the same underlying data are available. We encourage ad-tech providers to configure the reporting settings in the API to optimize for better measurement accuracy without 3PC, as well as improve how these two types of reports can be post-processed and used together. There are many possible ways to utilize the ARA reports. The methodology that works for an ad-tech provider will ultimately depend on its conversion data and measurement requirements. Google Ads has found that leveraging both report types can help the industry benefit from the strengths of each report.

Google Ads leverages both event types to produce a more complete, ad event-level log. We are committed to sharing our process and engaging with the ecosystem to help our partners and the broader industry transition into a future without third-party cookies. For more details on how we’re implementing the Attribution Reporting API, please refer to our detailed technical guide. Harikesh Nair, Director, Data Science, Ads Measurement

Announcing New Reporting Script for Performance Max

Monday, July 17, 2023

How can I get started?Find the script hereforumDavid Stevens, Google Ads Scripts Product Manager

Display & Video 360 API v1 will sunset on September 14, 2023

Monday, July 17, 2023

As announced in March 2023, Display & Video 360 (DV360) API v1 will sunset on September 14, 2023. Please migrate to DV360 API v2 before the sunset date to avoid an interruption of service. You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1 to v2. If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Generic mutate support in Google Ads scripts

Thursday, July 13, 2023

generic mutate functionalityconst budgetResult = AdsApp.mutate({ campaignBudgetOperation: { create: { amountMicros: 10000000, explicitlyShared: false } } }); MutateOperation reference documentationnew guideforum - Mike Cloonan, Google Ads API Team

Performance Max success story driven by Google Ads API with Kueez

Wednesday, July 12, 2023

Kueezsuccess storyGoogle Ads APIPerformance Max

Kueez leverages Google Ads to drive platform ad views from high-quality and engaged traffic across their portfolio of publisher partners, and owned and operated websites.

Using the power of Google Ads API, Kueez implemented Performance Max campaigns to broaden their reach, and attract additional audiences that exhibit similar or better conversion rates than they had before using Performance Max.

Within 45 days of activating Performance Max campaigns, Kueez achieved an increase of over 50% engaged visits at a similar CPA, and drove +20% ROAS.

Where can I learn more?

Check out the full case study here

this formforumDavid Stevens, Google Ads API Product Manager

Deprecating outcome-based buying in Display & Video 360 API and Structured Data Files on August 1, 2023

Tuesday, July 11, 2023

On August 1, 2023, outcome-based buying will be deprecated in Display & Video 360. After this date, all resources using outcome-based buying will be archived, line items using outcome-based buying will stop serving, and you will no longer be able to create resources that use outcome-based buying. Outcome-based buying is set at the insertion order level, and is used by their child line items. Outcome-based buying is set in the following ways:

In Display & Video 360 API, outcome-based buying is used if the billableOutcome field of the InsertionOrder resource is set to BILLABLE_OUTCOME_PAY_PER_CLICK or BILLABLE_OUTCOME_PAY_PER_VIEWABLE_IMPRESSION.

In Structured Data Files, outcome-based buying is used if the “Billable Outcome” column of the Insertion Order file row is set to “Click” or “Active View.”

Effective August 1, 2023, all relevant insertion orders and line items will be archived. Display & Video 360 API requests creating new insertion orders and line items using outcome-based buying will return 400 errors. Structured Data File uploads will fail for rows attempting to do the same. Read more about this change on our Announced Deprecations page. If you have questions regarding these changes, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Image and Location Auto-migration August 2023

Thursday, July 6, 2023

What’s changing? Beginning on August 2, 2023, we will start auto-migrating image and location extensions to assets. The auto-migration will end on September 30, 2023. Once the image and location extensions have been migrated to assets, you won’t be able to mutate the image and location extensions. The image and location assets will be the entities that are served. Metrics for the extensions will be available until sometime in 2024. Why is this changing? Extensions are migrating to assets. What do I need to do? Upgrade to version v13 or greater of the Google Ads API since v12 will sunset at the end of September 2023. We recommend that you upgrade to v14. The auto-migration will not keep a mapping of feed IDs to asset IDs. If you would like to keep a record of feed ID to asset ID mappings, create a new asset image or location based on your feed, and save that ID mapping locally. Can I opt-out of the auto-migration? No. We offered an opt-out for the first batch of auto-migration, but you can’t opt out of this auto-migration. How will the migrations occur? The migrations occur at an account level. During the migration of an account, which will take several minutes, you won’t be able to execute any image or location mutations of either extensions or assets. When the migration is complete, you will have access to the assets. The image and location migrations are not synchronized. It is likely they will occur at different times for each account. How do I know when an account has been migrated? Use the following fields from v13 or greater in the Customer resource to track the status of the migration:

bool image_asset_auto_migration_done

string image_asset_auto_migration_done_date_time

bool location_asset_auto_migration_done

string location_asset_auto_migration_done_date_time

If you are using v12, you can instead consult the UI and you will see an alert once your account has been migrated. What happens after the auto-migration? Accounts that have been migrated will reject mutate calls for feed-based entities. If you have any questions, please reach out to us on the forum. Bob Hancock, Google Ads API Team

Upcoming changes in keyword validation

Wednesday, July 5, 2023

Starting on July 5, 2023 we will gradually release a backend improvement on Google Ads keyword policy validation. You might see an increase in keyword policy violation failures when you send Google Ads API requests that create keyword criteria. The Google Ads API will catch more keywords that don’t adhere to our keyword policy as soon as you send the API request, rather than validating them offline after the keywords have been submitted. Note that not all keywords created through successful API calls will be accepted. Keywords still undergo offline review. Due to the new realtime check, you might need to account for new policy violation terms in the PolicyViolationDetails field of the responses you receive from the Google Ads API. Use this field to apply for keyword policy exemption; for further details on how to do so, please refer to the guide on keyword policy exemptions. If you have any questions or concerns, please don't hesitate to contact us via the forum.

- Mattia Tommasone, Google Ads API Team

Announcing v14 of the Google Ads API

Wednesday, June 7, 2023

Google Ads APIclient libraries

Added the following recommendation types: DynamicImageExtensionOptInRecommendation, LowerTargetRoasRecommendation, RaiseTargetCpaRecommendation.

Added Customer.offline_conversion_client_summaries to show the status and diagnostic information of the customer’s offline conversion uploads and adjustments.

Added support for retrieving, creating and updating account-level negative keywords through CustomerNegativeCriterion.negative_keyword_list.

Added conversion action types and ConversionAction.google_analytics_4_settings to support identifying Google Analytics conversions and determining whether a conversion is imported from a GA4 or Universal Analytics property.

Removed support for retrieving the campaign_criterion_simulation report.

Added KeywordPlanIdeaService.GenerateKeywordForecastMetrics to replace multiple methods removed in KeywordPlanService. This new method doesn’t require you to create a keyword plan first.

Where can I learn more?

Release Notes

Guides

Reference

Diff between v13 and v14

forum

- Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Launching Structured Data Files v6

Monday, June 5, 2023

Today we’re launching Structured Data Files (SDF) v6. This version can now be used when uploading and downloading SDFs in the Display & Video 360 UI or downloading SDFs through the Display & Video 360 API. Significant changes have been made from SDF v5.5 to v6:

Support for Optimized Targeting configurations in a new Line Item file column.

Support for Audience Expansion configurations in a new YouTube Ad Group file column.

Support for proximity and proximity list targeting in Line Item and Insertion Order files.

Removal of “Audience Targeting - Similar Audiences” columns in Line Item and Insertion Order files.

Full details on the changes made in v6 can be found in our Structured Data Files release notes. Assign v6 as the default SDF version in Display & Video 360 at the Partner or Advertiser level. Generate v6 SDFs when using the Display & Video 360 API with the new SdfVersion value SDF_VERSION_6. If you run into issues or need help with this new version, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Campaign criterion simulations being removed in the Google Ads API

Tuesday, May 30, 2023

We are announcing that the campaign_criterion_simulation report will be deprecated in the Google Ads API. This change will be effective on July 10, 2023. After this date, all campaign_criterion_simulation report requests will return blank responses. We recommend that you start updating your applications to account for this change as soon as possible. Please contact us on our forum or at googleadsapi-support@google.com if you have any questions. - Mike Cloonan, Google Ads API Team

Announcing v202305 of the Google Ad Manager API

Wednesday, May 24, 2023

We're pleased to announce that v202305 of the Google Ad Manager API is available starting today, May 23rd. This release brings support for new DAI ingestion statuses and removes deprecated SPM reporting dimensions. For the full list of changes, check the release notes. Feel free to contact us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

Deprecating Python 3.7 Support in the Google Ads Client Library for Python

Wednesday, May 24, 2023

June 27, 2023end-of-lifeGoogle Ads client library for Pythonissues or bugsissuerepository

- Ben Karl, on behalf of the Google Ads API Team

Prepare to test Privacy Sandbox APIs with Google’s ads platforms

Monday, May 22, 2023

announced the upcoming general availability of Privacy Sandbox APIsencouraging results from our recent interest-based advertising experimentsTopicsProtected AudienceAttribution ReportingadvertiserspublishersChrome plans to deprecate third-party cookies for one percent of its users

If you’re a Google Authorized Buyer or participant in Open Bidding, see integration guidance for Topics and Protected Audience.

If you’re a publisher platform working with Google Ads or Google Marketing Platform (Display & Video 360 or Campaign Manager 360), see integration guidance for Topics, Protected Audience and Multiple seller testing.

If you’re a measurement provider working with Google Marketing Platform (Display & Video 360 or Campaign Manager 360), see integration guidance for the Protected Audience API.

If you’re a publisher or ad tech provider working with Google Marketing Platform (Display & Video 360, Campaign Manager 360 or Search Ads 360), see integration guidance for the Attribution Reporting API.

Dan Taylor, Vice President, Global Ads

Announcing new testing features for ad inspector

Tuesday, May 2, 2023

We’re excited to announce the launch of new testing features on ad inspector across all platforms for our AdMob and Ad Manager publishers. Previously, ad inspector tested all ads in context - in other words, you had to fire up your app, navigate to the appropriate screen in the UI, and have your ad load as it would for any other user. While this provides for the most accurate testing scenario, it also puts more work on you as the publisher and tester of your app. You don’t want ads buried in more obscure screens in your app to lose out on the testing attention and care they need! With our latest update, you can now use test ads to load requests for any ad unit - no matter where it's located in your app. Rather than needing to navigate through your app to test each ad unit, you can execute your tests directly from ad inspector. How do I use ad inspector’s new testing features? Beginning with version v10.0.0 on iOS and v21.4.0 on Android of the Google Mobile Ads SDK, ad inspector supports running tests directly from the ad unit detail screen via a “Request test ad” button:

All of your requests made from your app’s UI or within ad inspector will appear in the SDK request log; your requests made from within ad inspector will be differentiated by being labeled with “Requested from ad inspector”. For these special requests you’ll be able to tap the “View” button one time to view the actual ad, see which network filled the slot, and more. Alongside single ad source testing, these new testing features will allow you to rigorously test each individual ad network integration in your app. To learn more about how to test your ads with ad inspector, check out our developer guides here:

Android (AdMob | Ad Manager)

iOS (AdMob | Ad Manager)

Flutter (AdMob | Ad Manager)

Unity (AdMob)

C++ (AdMob)

If you have any questions or need additional help, please contact us via the developer forum. - Chris Giglio, Mobile Ads Developer Relations

Deprecating Audience Composition Reports in Bid Manager API on June 8, 2023

Thursday, April 27, 2023

On June 8, 2023, Audience Composition Reports will be deprecated in Display & Video 360. This means that you will no longer be able to retrieve, create or run Audience Composition Reports using the Bid Manager API. In the Bid Manager API, an Audience Composition Report is a Query resource with a ReportType of AUDIENCE_COMPOSITION assigned to params.type. After deprecation:

Any request to the queries or queries.reports services identifying an Audience Composition Report will return an error.

All queries.create requests creating a new Audience Composition Report will return an error.

All queries.list responses will no longer include Audience Composition Report queries.

To avoid an interruption of service, we recommend that you stop creating or retrieving any existing reports of this type. If you have questions regarding this change, please contact us using our support contact form.

- Trevor Mulchay, Bid Manager API Team

Announcing v13_1 of the Google Ads API

Wednesday, April 26, 2023

Google Ads APIclient libraries

You can now retrieve bid simulations at a campaign level for Performance Max through campaign_simulation.

We added several recommendation types related to Shopping campaigns, such as recommendations to migrate to Performance Max and recommendations to fix a Merchant Center account’s suspension.

Google Ads now accepts SKAdNetwork conversion value schemas for iOS App campaigns. Learn more about setting up your schema and best practices for your iOS campaigns.

We added LeadFormField.has_location_answer to support specifying whether locations of the location assets at the campaign or customer level should be displayed with a lead form.

(Allowlisted feature) Performance Max campaigns now have a VEHICLES listing type in the newly Campaign.listing_type field. This replaces ShoppingSetting.use_vehicles_inventory, which will be reserved for Smart Shopping campaigns.

Where can I learn more?

Release Notes

Guides

Reference

forum

- Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Removing support for PHP 7 in the Google Ad Manager SOAP API Client Library for PHP

Wednesday, April 26, 2023

In August 2023, the Google Ad Manager SOAP API Client Library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for Google Ad Manager API v202305 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until Google Ad Manager API v202305 is sunset, but no new features will be added. All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible. Here are useful resources to help with the PHP migration:

The PHP support version calendar

How to migrate from PHP 7.4.x to PHP 8.0.x

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.

Pierrick Voulet, Google Ads API Team

Ad Manager API v202205 sunset and v202202 extension

Tuesday, April 25, 2023

On Wednesday, May 31, 2023, in accordance with the deprecation schedule, v202205 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors. Additionally, support for Ad Manager API v202202 is being extended until the same date, May 31, 2023. We've heard from a number of users that they need additional time to complete the Ad Exchange Historical report migration. Note that v202202 is the last version with support for Ad Exchange Historical reports. When you’re ready to upgrade, check the full release notes to identify any breaking changes. Here are a few examples of changes that may impact your applications:

v202211

Replaced the string field thirdPartyImpressionTrackingUrl with the list field thirdPartyImpressionTrackingUrls for multiple creative types including ImageCreative. Currently only a single URL may be provided in the list.
Removed support for OPTIMIZATION reporting columns.

As always, feel free to contact us on the developer forum with any questions.

- Chris Seeley, Ad Manager API Team

New Merchant IDs are now 64-bit in Content API for Shopping

Monday, April 24, 2023

Content API for Shoppinginformed you last JuneforumBenji Rothman, Content API for Shopping Team

New Validations for Google Ads Account Names

Monday, April 24, 2023

descriptive_nameACTION_NOT_PERMITTEDdescriptive_nameforumgoogleadsapi-support@google.com

- Ben Karl, on behalf of the Google Ads API Team

Changes coming to Display & Video 360 API in May and June 2023

Thursday, April 20, 2023

Throughout May and June 2023, we will be making four changes in the Display & Video 360 API that may impact your integration. These changes and relevant dates are as follows, with links to further details:

On May 17, 2023, we will begin deprecating manual triggers in Display & Video 360.

On May 20, 2023, we will begin deprecating a subset of GoogleAudience and FirstAndThirdPartyAudience types in Display & Video 360.

On May 30, 2023, existing Display & Video 360 API quota limits will be replaced with new, per-advertiser quota limits.

On June 8, 2023, LIST request filter parameters will no longer allow OR operators between restrictions of different fields and two filterable fields will be deprecated for insertion order and line item LIST methods.

With the announcement of these deprecations, we are launching a new Announced Deprecations page listing all announced deprecations and sunsets. This includes version deprecations and API-wide feature deprecations. If you have questions regarding these changes, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

First click, linear, time decay, and position-based attribution models are going away in Google Ads API

Thursday, April 20, 2023

UPDATE: The start of this change will now begin mid-July instead of June as mentioned in the original blog post. What’s changing?simplifying attribution model optionsmid-July 2023conversion actions

First click (GOOGLE_SEARCH_ATTRIBUTION_FIRST_CLICK)

Linear (GOOGLE_SEARCH_ATTRIBUTION_LINEAR)

Time decay (GOOGLE_SEARCH_ATTRIBUTION_TIME_DECAY)

Position-based (GOOGLE_SEARCH_ATTRIBUTION_POSITION_BASED)

data-driven attributionGOOGLE_SEARCH_ATTRIBUTION_DATA_DRIVENGOOGLE_ADS_LAST_CLICKexternal attributionWhat do I need to do?conversion actionsConversionActionServiceAttributionModelSettingsdata-driven attributionGOOGLE_SEARCH_ATTRIBUTION_DATA_DRIVENlast click attributionGOOGLE_ADS_LAST_CLICKmid-July 2023September 2023If you don’t want your conversion actions to use data-driven attribution, update your conversion actions to the last click attribution model before September 2023.GoogleAdsService.SearchGoogleAdsService.SearchStreamSELECT conversion_action.attribution_model_settings.attribution_model FROM conversion_action forum

Ian Ballantyne, Google Ads API Team

Ads Developer Blog

Labels

Archive