Google Ads Developer Blog: 2025

Explorer access is now available for Google Ads API developers

martes, 28 de octubre de 2025

We are rolling out a new Explorer Access level access tier for Google Ads API over the next couple of weeks. This will allow new developers signing up for Google Ads API to gain immediate access to production accounts, no longer limited to test accounts. Here’s how it will work:

Most new developers who sign for the Google Ads API will immediately be given Explorer Access level upon completing onboarding steps.

Explorer Access level will give developers the ability to work with live serving accounts immediately.

To limit abuse, developer tokens with Explorer Access will have some restrictions on functionality, such as creating new advertiser accounts and keyword planning.

Explorer Access will allow 2880 operations/day.

Developers can apply for Basic Access or Standard Access levels to increase the daily operation limits and remove the restrictions on functionality.

Existing developers are unaffected by this change. For example, those with Test Account Access, Basic Access and Standard Access levels will continue to have these access levels. In the future, the Google Ads API team will continue to streamline the onboarding process with additional improvements, so stay tuned. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Anash P. Oommen, Google Ads API Team

October 2025 update to Display & Video 360 API

lunes, 27 de octubre de 2025

Today, we’re announcing the October 2025 update to the Display & Video 360 API. This update includes the following:

The ability to create and retrieve assets that are used in YouTube and Demand Gen ads.

Support for retrieving Demand Gen AdGroupAd resources.

A new adPolicy field in AdGroupAd resources to expose policy reviews and appeal options for YouTube and Demand Gen ads.

Support for Structured Data Files versions v9.1 and v9.2.

For a complete list of new features in this update, see 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 Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing v22 of the Google Ads API

miércoles, 15 de octubre de 2025

Today, we’re announcing the v22 release of the Google Ads API. To use some of the v22 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published. Here are some of the key features in this release:

Smart Bidding Exploration for Target ROAS bidding strategies on Search: You can now retrieve time-segmented diversity metrics via the API. Learn more about Smart Bidding Exploration from our blog post and help center article.

Improvements for DemandGen campaigns: We have added support for new asset generation automation options and bidding strategies for DemandGen campaigns.

Generative AI support for asset generation: We have introduced a new AssetGenerationService in beta that generates text and image assets using generative AI.

Improvements for Performance Max campaigns: We have added campaign level API support for image enhancement and image extraction asset automation settings. Additionally, we’ve enhanced the reporting for Performance Max campaigns with added reporting segments and a new feed_types field to indicate which types of feeds are attached to the campaign.

Improvements for App campaigns for installs (ACi): We have added new bidding goals for App campaigns for installs (ACi) to optimize without specifying a target, which is useful for rapid scaling or when it is challenging to determine the right target.

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

Release Notes

Upgrade from a previous version

Guides

Reference

Diff between v22 and v21

Please come join us for a walkthrough of this release in our "Google Ads API Release Highlights" event on discord on October 16th at 11am ET. If you have any questions or want to discuss this post, please also reach out to us in the #ads-api channel there. For technical support issues, please reach out to https://support.google.com/google-ads/gethelp

- Anash P. Oommen, Google Ads API Team

Upgrade your Call-Only Ads to Responsive Search Ads with Call Assets in the Google Ads API

jueves, 9 de octubre de 2025

Google Ads is deprecating the call-only ad format. Google Ads API users currently creating or managing call-only ads will need to transition to using Responsive Search Ads (RSAs) with call assets. This change will help advertisers achieve better campaign performance and leverage the latest ad innovations. What’s Changing? The call-only ad type, based on the legacy Expanded Text Ad (ETA) framework, is being phased out. Moving forward, phone call lead generation will be fully supported through Responsive Search Ads (RSAs) combined with call assets. RSAs offer greater flexibility and performance by utilizing machine learning to optimize ad creatives. Why This Change?

Improved Performance: Advertisers generally see better results and lower costs per call lead with RSAs and call assets compared to the static nature of call-only ads.

Modern Infrastructure: RSAs benefit from ongoing improvements in AI and machine learning. The underlying ETA framework for call-only ads is deprecated.

Consistency: This move aligns call-based advertising with the standard for all other Search ad formats, simplifying campaign management.

Impact on Google Ads API Users If your application uses the Google Ads API to create or manage call-only ads, you will be affected.

New Call-Only Ad Creation: Starting January 2026, coinciding with the v23 API release, you will no longer be able to create new call-only ads or duplicate existing ones through the API. The call-only ad type will be removed from the latest API version.

Existing Call-Only Ads: Your existing call-only ads will continue to serve and be manageable via the API until February 2027.

API Support Sunset: Support for call-only ads will be progressively removed from all active API versions, with full cessation by February 2027.

Key Dates for API Users:

January 2026:

Creation of new call-only ads (including duplication) is blocked in all Google Ads API versions and all other interfaces (Google Ads UI, Google Ads Editor, SA360).

Until February 2027:

Existing call-only ads continue to serve.
API users can still update existing call-only ads. We strongly recommend using this time to migrate.

As of February 2027:

All call-only ads will stop serving.
Full support for call-only ads is removed from all active Google Ads API versions.

What You Need to Do:

Update API Integrations: Modify your API client libraries and applications to stop creating call-only ad types.

Migrate to RSAs with Call Assets: Transition your ad creation and management workflows to use Responsive Search Ads. Ensure you attach call assets to these RSAs to continue driving phone call leads.

To create an RSA, you'll provide multiple headlines and descriptions.
Phone numbers are added as assets linked at the customer, campaign, or ad group level.

Benefits of Migrating Early:

Take advantage of the better performance of RSAs.

Ensure a smooth transition without service interruption.

Maintain full control over your ad copy and settings.

We recommend updating your API integrations and migrating your call-only ad strategies well before the deadlines. Please refer to the Google Ads API developer documentation for the latest guidance on working with Responsive Search Ads and call assets. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server. Bob Hancock, Google Ads API Team

Bidding enforcement for conversion environment in in-app conversions no longer planned

miércoles, 8 de octubre de 2025

On June 30, 2025 we announced that we would roll out a change that would cause our bidding models to start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions for campaign performance. That change, which may have caused performance degradation in certain campaigns where this is not set, will no longer be implemented. However we still recommend that users who import conversions using the Google Ads API set the conversion_environment field in order to gain the following benefits:

Accurate cross-environment attribution: Understand the full value of your campaigns across website and app sources.

Ad destination reporting: Gain insights into where the user lands after clicking your ad, and the relative performance of each segment.

Streamlined Google support: Receive faster and more effective troubleshooting.

For more details see this Help Center article. If you have any questions or need help, see the Google Ads API support page for options.

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

Open Source Google Ads API MCP Server

martes, 7 de octubre de 2025

We're thrilled to announce the open source release of the Google Ads API Model Context Protocol (MCP) Server, available here. This project marks a significant step in democratizing access to Google Ads data for the next generation of AI tools and agent developers. The Model Context Protocol (MCP) is the open standard that allows Large Language Models (LLMs), like Google Gemini, to connect with and act upon external data sources and applications. By releasing an MCP Server specifically for the Google Ads API, we are making it possible for any MCP-compatible AI application to understand and analyze advertising campaigns through natural language. This initial release is read-only, meaning it can be used for reporting and diagnostics but will not make changes to your account. Please use the GitHub repo for technical issues with the MCP server. For technical support issues with the API, reach out to the Google Ads API support channel. If you have other questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Dean Lukies, Google Ads API Team

Correction of an error in the BudgetPerDayMinimumErrorDetails message

jueves, 2 de octubre de 2025

When we released V21 of the Google Ads API, we released a field with the wrong name in the BudgetPerDayMinimumErrorDetails message: the field minimum_budget_amount_micros was mistakenly released as minimum_bugdet_amount_micros, with the word “budget” misspelled. We already corrected the error in V22 of the API; however, we are also retroactively correcting it in V21 starting from October 15th, 2025 (the same day of the V22 release). What do I need to do? If you are using one of our officially supported client libraries, they will keep working seamlessly when we release the field rename. However, when you upgrade to the latest version of your client library, you will have to modify your existing code that accesses this field to comply with the field rename, even if you are still using V21. If you are using the Google Ads API with the REST transport layer, make sure your code is handling the minimum_budget_amount_micros field by its correct name instead of the mistakenly released one. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Mattia Tommasone, Google Ads API Team

Google Mobile Ads Mediation adapters adopt Swift Package Manager

martes, 30 de septiembre de 2025

Today, we’re announcing you can start adding Google Mobile Ads mediation adapters to your iOS projects using Swift Package Manager (SPM). Swift Package Manager is Apple's first-party tool for managing project dependencies. By supporting SPM, we're making it easier for you to integrate and manage our mediation adapters, helping you streamline your development workflow and reduce setup complexity. Which adapters are supported? We're planning to roll out SPM support for all open source and versioned adapters. Each adapter will be in its own dedicated GitHub repository. Adapters currently available:

Ad source

Minimum version supported in SPM

AppLovin

13.3.1.0

DT Exchange

8.3.8.0

IronSource

8.10.0.0

Liftoff Monetize

7.5.3.0

i-mobile

2.3.4.2

inMobi

10.8.6.0

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

jueves, 25 de septiembre de 2025

Starting on November 17 2025, we are changing the account-default behavior of automatically created customer conversion goals. Current behavior Currently, when you create a new conversion action using the Google Ads API, customer conversion goals are created automatically, as needed. These newly created goals are automatically set as account-default, meaning this goal will automatically be biddable in any campaign that is optimizing to account-default goals. While convenient, this sometimes leads to bidding mechanisms targeting unnecessary goals, potentially resulting in suboptimal campaign performance. This change aims to optimize bidding performance by reducing the number of unnecessary goals included in the account-default set for a given account. What’s changing? With this change, a new automatically created goal will only be set as account-default if all other goals within the same category are also account-default goals. For example, if an account has an existing, non-account-default customer conversion goal associated with a conversion action with the category PURCHASE and a conversion origin of WEBSITE, then any new conversion actions with the category PURCHASE will result in goals that are also not account-default. This approach helps us better infer user intent, and it ensures that the account-default set remains lean and effective. Technical recommendation After this change is introduced, newly created account goals will not be considered account-default automatically. If you want to set an account goal to account-default manually, set the CustomerConversionGoal.biddable field to true. This update will enhance the efficiency and effectiveness of goal management within Google Ads. We encourage you to review your applications and client workflows in light of this upcoming change. For any questions or concerns, feel free to refer to our support page. You can also discuss this post in our “Google Advertising and Measurement Community” Discord server.

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

Introducing improved diagnostics for enhanced conversions for leads imports

martes, 23 de septiembre de 2025

Today in the Google Ads UI, you will see updated enhanced conversions for leads diagnostics that feature a number of improvements that offer better visibility into the state of your conversion import implementation. The goal of these changes is to help you identify common problems and address them quickly. Here are some of the changes you’ll see:

New "Importing limited user-provided data" Alert: A new, high-priority alert has been introduced to detect a common implementation error, where users fail to import incremental conversions that contain user-provided data (UPD) but not a GCLID. We recommend that you import all of your conversion data that has user-provided data, regardless of whether or not it has a GCLID. Doing so helps to find cross-device or Youtube EVC conversion touchpoints, driving performance uplift. You may not see these benefits if you omit UPD-only conversions.

Improved Status for "Tagless" Implementations: A new "Good" status has been added to validate setups where advertisers import conversions with both a GCLID and user-provided data, but do not have the Google tag implemented on their website. Previously, this valid configuration could trigger confusing "Urgent" alerts. If you have not implemented the Google tag on your website, it’s important to include GCLIDs in your conversion imports whenever possible in order to get performance benefits.

Reprioritized Alert Logic: Alert priorities have been updated to be more intelligent. For users sending GCLIDs with their offline data, import-related issues will be prioritized as more critical, while tag-related issues will be downgraded in severity.

Complete Alert Visibility: The diagnostics interface has been updated to show all alerts at once, regardless of their severity tier. This allows developers to see a complete picture of all required and recommended actions upfront, rather than fixing one issue only to uncover another.

Deprecation of CLICK_NOT_FOUND: The informational CLICK_NOT_FOUND error has been removed from the Diagnostics UI and API, and, correspondingly, the debug_mode parameter in the UploadClickConversions method that triggers it in API responses has also been removed. See this related blog post for reference.

Reach out to the Google Ads API support channel if you have any questions or need support. If you want to discuss this change with us, join our “Google Advertising and Measurement Community” Discord server.

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

Google Ads scripts documentation upgrade

lunes, 22 de septiembre de 2025

We’re excited to announce a refresh of the Google Ads scripts documentation! Like the Google Ads API documentation changes announced in a previous blog post, we have focused on making the Google Ads scripts documentation more intuitive and useful. Here’s a sneak peek at what’s new: 1. Logically grouped guides We’ve reorganized our guides into clear categories. Whether you're a beginner starting out with core concepts or an expert exploring all the different campaign types supported by scripts, you'll find what you need faster. These changes will help you write scripts more efficiently by smoothly navigating between related topics, building on previous guides and highlighting unique scripts features. 2. Dedicated reference tab You now have a dedicated reference tab to quickly explore all the scripts objects available to you. This creates a direct path to the resources you need and aligns our documentation more closely with the Google Ads API documentation, providing a more seamless experience across our products. 3. Combined solutions and examples We've merged the solutions and examples tabs into a single, comprehensive resource. Now you can find all our sample code in one place. This is a great launchpad for discovering what’s possible with scripts and for modifying examples to create your own powerful solutions. We have more exciting updates on the way, and we'll be incorporating more of the fantastic feedback from our Google Ads scripts community. If you have any questions, suggestions, or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server, where we have a dedicated #ads-scripts channel.

- Dora Sun - Google Ads API Team

Introducing the google-ads-bom to the Google Ads API client library for Java

jueves, 18 de septiembre de 2025

We are excited to announce the release of the google-ads-bom for the Google Ads API client library for Java, now available with v40.0.0 of the google-ads client library. This new Bill of Materials (BOM) is designed to significantly simplify your dependency management and enhance the stability of your Google Ads API integrations. What is a BOM? A BOM is a build-time tool that provides a centralized, authoritative "rulebook" for managing dependency versions. By importing our BOM, you ensure your project uses the exact set of compatible dependency versions that the Google Ads client was built and tested against. This significantly helps avoid dependency conflicts with libraries like Guava and GAX, which are also used by many other frameworks. How to incorporate the google-ads-bom into your code To leverage the benefits of the google-ads-bom, import it into the section of your build file (e.g., pom.xml for Maven or build.gradle for Gradle). You should then omit the version specification from the google-ads dependency in the section. How to include the BOM in your Maven project:  <dependencyManagement> <dependencies> <dependency> <groupId>com.google.api-ads</groupId> <artifactId>google-ads-bom</artifactId> <version>40.0.0</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>  <dependencies> <dependency> <groupId>com.google.api-ads</groupId> <artifactId>google-ads</artifactId> </dependency> </dependencies> How to include the BOM in your Gradle project: // Import the Bill of Materials (BOM). implementation platform('com.google.api-ads:google-ads-bom:40.0.0') // Add the google-ads dependency, without a version. The version is managed by the BOM. implementation 'com.google.api-ads:google-ads' Declaring dependencies covered by the google-ads-bom The BOM automatically manages the versions for several common libraries–such as Guava, Protobuf, GAX, and gRPC–to make them compatible. To avoid potential dependency conflicts, you should not specify a version when declaring these dependencies. For example, if you are using Guava, you would declare it without a version: In Maven: <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> </dependency> Or in Gradle: implementation 'com.google.guava:guava' // NO VERSION SPECIFIED. To retrieve a list of constrained dependencies that can be imported using the BOM without a declared version, use the listAllDependencyConstraints gradle task. To learn more about this new google-ads-bom offering and how to configure your Java client, check out our getting started guide.

- Sarah Pollack, Google Ads API Team

Launching Structured Data Files v9.1

miércoles, 17 de septiembre de 2025

Today we’re announcing the general availability of Structured Data Files v9.1. All users can now use SDF v9.1 to upload and download SDFs in the Display & Video 360 UI. SDF v9.1 makes a number of small changes to files supporting Insertion Order, Line Item, and Ad Group resources:

Added the ability to configure whether certain targeting is set at the Line Item or Ad Group resource-level for Demand Gen Line Items.

Added a Combined Audience Targeting column to Ad Group files.

Made the Io Objective column required in Insertion Order files.

Updated the options available in the Bid Strategy Unit and TrueView Video Ad Formats columns in Line Item files.

Removed the Bid Multipliers column from Line Item files and the Measure DAR and Measure DAR Channel columns from Insertion Order files.

Full details on the changes between v9 and v9.1 can be found in the Structured Data Files release notes. SDF v7 is deprecated and scheduled for sunset on November 4, 2025. SDF v7.1, v8, and v8.1 are deprecated and scheduled for sunset on March 3, 2026. If you are still using a deprecated SDF version, follow the instructions in our v9 migration guide to update your integration to use v9 or greater. If you run into issues or need help with this new version, please follow the instructions in our support guide, or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

More frequent releases coming for the Google Ads API

jueves, 4 de septiembre de 2025

We’ve heard your requests for faster API access to Ads features available in the Google Ads UI. We will accelerate our launch timeline to have Google Ads API monthly releases, except for during the end of year holiday period. We will increase the number of major releases from 3 per year to 4 per year. The remaining releases will be minor releases, only adding incremental new non-breaking features. We have also adjusted the sunset schedules to avoid extra version migrations that will burden the API developers. Each major release will now be available for one year after the release. Release schedule for 2026 With the new timeline, the tentative release schedule for 2026 will be as shown in the following table. Please keep in mind that these dates are only estimates and may be adjusted going forward. Additionally, releases may be added, removed, or switched between major and minor versions.

Version

Planned Release Type*

Projected launch*

Projected sunset*

V23

Major

January 2026

February 2027

V23_1

Minor

February 2026

February 2027

V23_2

Minor

March 25, 2026

February 2027

V24

Major

April 2026

May 2027

V24_1

Minor

May 2026

May 2027

V24_2

Minor

June 2026

May 2027

V25

Major

July 2026

August 2027

V25_1

Minor

August 2026

August 2027

V25_2

Minor

September 2026

August 2027

V26

Major

October 2026

November 2027

V26_1 **

Minor

November 2026

November 2027

* Estimated and subject to change. ** This is designated as an optional release due to overlap with the holiday season. Sunset schedule for 2026 The following is the tentative sunset schedule for 2026. As with releases, these dates are only estimates and may be adjusted going forward.

Version

Projected sunset*

V19

February 2026

V20

June 2026

V21

August 2026

V22

October 2026

* Estimated and subject to change. How to get help As always, you can find the details of individual releases at the following pages.

Release Notes

Deprecation Schedule

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Anash P. Oommen, Google Ads API Team

Announcing v5 release and changes for supporting European Union Political Ads Regulation in Campaign Manager 360 API

martes, 2 de septiembre de 2025

What’s changing? As announced last year, Google will stop serving political advertising in the European Union ahead of new regulation in October 2025. Today, we’re releasing updates to the Campaign Manager 360 API v4 to support this change. We’re also announcing the release of v5. For details on the changes related to euPoliticalAdsDeclaration, continue reading this post. For details on all other changes, and the v5 release, see the release notes. v4 Deprecation and sunset reminder In accordance with our deprecation schedule, the v5 release marks the beginning of the deprecation period for v4, which will sunset on Feb 26, 2026. After this date, any requests made against v4 will begin returning errors. See the migration guide for details. In most cases, you will just need to upgrade to the latest version of your preferred client library. We recommend that you review the release notes to learn about important changes you might need to be aware of. If you have questions about this or anything else Campaign Manager 360 API related, feel free to reach out to us on our support forum. Background Campaign Manager 360 will require self-declaration for EU political ads. You must declare whether or not a campaign contains EU political ads when creating it. You can also make this declaration for the advertiser as a whole. This declaration will state whether any campaigns under the advertiser will contain EU political ads. We recommend that you make the declaration at the advertiser level using the Campaign Manager 360 API or under the advertiser Properties settings in the Campaign Manager 360 UI. Campaign Manager 360 API v4 and v5 will support the ability to declare whether a campaign contains EU political ads. Campaign Manager 360 API Campaign Manager 360 will start requiring declarations for new campaigns and for existing campaigns when adding a new placement, ad, or creative. Campaign Manager 360 API v5 will require the field euPoliticalAdsDeclaration for new campaign resources and for existing campaign resources when adding a new placement, ad, or creative. The field euPoliticalAdsDeclaration will be added to the following API objects in v4 and v5 to surface self-declaration at different resource levels:

Campaign objects for getting and setting the declaration at the campaign level.

Advertiser for getting and setting the declaration at the advertiser level.

The following table lists the values that can be set for this field on Advertiser resources.

Value

ADVERTISER_PLANS_TO_SERVE_EU_POLITICAL_ADS

ADVERTISER_DOES_NOT_PLAN_TO_SERVE_EU_POLITICAL_ADS

The following table lists the values that can be set for this field on Campaign resources.

Value

CONTAINS_EU_POLITICAL_ADS

DOES_NOT_CONTAIN_EU_POLITICAL_ADS

If you set the euPoliticalAdsDeclaration field to ADVERTISER_DOES_NOT_PLAN_TO_SERVE_EU_POLITICAL_ADS for the parent advertiser, the field will be backfilled for existing campaigns to match and new campaigns will use that value if another is not set at creation. What do I need to do? We recommend that you make the declaration at the advertiser level. You can do this either by setting the euPoliticalAdsDeclaration field using the API when calling the advertisers.insert, advertisers.patch or advertisers.update methods, or in the Campaign Manager 360 UI under the advertiser Properties setting. If you can’t declare at the advertiser level or have declared that EU political ads may be served under your advertiser, you will need to provide declarations at the campaign level by updating your use of the following API methods:

Set the euPoliticalAdsDeclaration field in the new campaign resource when making a campaigns.insert request or in an existing campaign resource when making a campaigns.update or campaigns.patch request.

How will this affect my campaign serving? Refer to the Campaign Manager 360 Help center article to learn more about how this declaration affects your ad serving. Learn More As with every new version of the Campaign Manager 360 API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly. Give it a try and let us know if you have any questions!

- Kamlesh, Campaign Manager 360 API Team

Changes for supporting European Union Political Ads Regulation in Display & Video 360 API and Structured Data Files

jueves, 21 de agosto de 2025

What’s changing? As announced last year, Google will stop serving political advertising in the European Union (EU) ahead of new regulation in October 2025. Starting September 8, 2025, the Display & Video 360 API and Structured Data Files (SDFs) will roll out enforcements related to this change. If you use either of these products to create or manage line items, you may need to update your application to handle these enforcements before September 8, 2025 to avoid an interruption of service. Background Starting September 8, 2025, Display & Video 360 will require self-declaration for EU political ads. You must declare whether a line item will serve EU political ads when creating it. You can also make this declaration for the advertiser as a whole. This declaration will state whether any line items under the advertiser will serve EU political ads. Make the declaration at the advertiser level using the Display & Video 360 API or under the advertiser Basic details settings in the Display & Video 360 UI once it launches after September 8. If you declare that your advertiser won’t serve EU political ads, new line items under that advertiser will use that declaration if another isn’t provided, avoiding an interruption of service. Display & Video 360 API and Structured Data Files have added support for declaring whether a line item serves EU political ads. Similar support for self-declaration will launch in the Display & Video 360 UI starting September 8, 2025. Display & Video 360 API In the Display & Video 360 API, the field containsEuPoliticalAds has been added to the following API objects in v3 and v4 to surface self-declaration at different resource levels:

LineItem objects for getting and setting the declaration at the line item level.

Advertiser for getting and setting the declaration at the advertiser level.

The possible settable values for the field are shown in the table below, with a meaning relevant to the resource to which it is assigned.

Value

Meaning

CONTAINS_EU_POLITICAL_ADVERTISING

The resource will be used to serve EU political ads.

DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING

The resource will not be used to serve EU political ads.

Starting September 8, 2025, Display & Video 360 API will start requiring that the containsEuPoliticalAds field is set for new line item resources or for existing line item resources when updating geography targeting of existing line items. What do I need to do? Every new line item created will need a valid declaration using the field containsEuPoliticalAds. Set the containsEuPoliticalAds field in the Advertiser object using the advertisers.patch method, or set the declaration under the advertiser Basic details settings in the Display & Video 360 UI once it is available. If you set the containsEuPoliticalAds field to DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING for the parent advertiser, new line items will use that value unless another value is set at creation, and the field will be backfilled for existing line items within a day. This field can then be updated using either the UI, API, or Structured Data Files. If your advertiser is not serving EU political ads, declaring at the advertiser level will be a sufficient action to avoid errors. If you can’t declare at the advertiser level or have declared that EU political ads may be served under your advertiser, you must update your use of the following API methods:

Set the containsEuPoliticalAds field in the new line item resource when making an advertisers.lineItems.create request.

Set the containsEuPoliticalAds field in the request body when making advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests.

Set the containsEuPoliticalAds field in existing line item resources using an advertisers.lineItems.patch request before updating geography targeting for those line items. Geography targeting includes the following targeting types:

TARGETING_TYPE_GEO_REGION
TARGETING_TYPE_POI
TARGETING_TYPE_BUSINESS_CHAIN
TARGETING_TYPE_REGIONAL_LOCATION_LIST
TARGETING_TYPE_PROXIMITY_LOCATION_LIST

Structured Data Files In Structured Data Files, we have launched v9, which adds the column Contains EU Political Ads to the line item file. This allows for the retrieval and setting of EU political ads declaration at the line item level. This column uses the values YES and NO to represent the line item declaration. With this launch, we are also deprecating SDF v7.1, v8, and v8.1 and recommend that you migrate to v9 your earliest convenience. We will support these versions until we sunset them in March 2026. Starting September 8, 2025, Display & Video 360 will start requiring you to use v9 to upload Structured Data Files and set the Contains EU Political Ads column to YES or NO for new SDF line item entries. If your advertiser has declared that it will not serve EU political ads, you can continue to use previous versions to upload SDFs. What do I need to do? Every new line item created will need a valid declaration using the column Contains EU Political Ads. Set the containsEuPoliticalAds field in the advertiser using the Display & Video 360 API advertisers.patch method, or set the declaration under the advertiser Basic details settings in the Display & Video 360 UI once it is available. If you declare that the advertiser will not serve EU political ads, new line items will use the NO value for the Contains EU Political Ads column unless another value is set at creation, and the field will be backfilled for existing line items within a day. This enables you to use v7, v7.1, v8, or v8.1 for SDF upload. After line item creation, this field can be updated using the UI, API, or Structured Data Files. If you can’t declare at the advertiser level or have declared that EU political ads may be served under your advertiser, do the following before September 8, 2025:

Migrate to using SDF v9. See our migration guide for instructions.

Set the Contains EU Political Ads column to YES or NO in line item entries on SDF upload when:

Creating new line items.
Updating any of the following columns of the existing line item:

Geography Targeting - Include
Geography Targeting - Exclude
Geography Regional Location List Targeting - Include
Geography Regional Location List Targeting - Exclude
Proximity Targeting
Proximity Location List Targeting

Creating new ad groups with set Geography Targeting columns under the existing line item.
Updating the Geography Targeting columns of ad groups under the existing line item.

Also, if you use Structured Data Files at all, make sure to migrate to v9 before all previous versions are sunset in March 2026. How do I get help? Reach out to the Display & Video 360 API support channels if you have more questions about this change.

- Trevor Mulchay, Display & Video 360 API Team

Maximize the performance of your Google Ads conversion data

miércoles, 20 de agosto de 2025

In today's data-driven world, the performance of your ad campaigns increasingly depends on the richness of the conversion data you import. When it comes to machine learning, the more signals you provide, the better the models can understand user behavior, predict outcomes, and deliver value. For conversion imports specifically, richer data can mean increased observed conversions, and better modelled conversions. For this reason it’s important to make sure that your application is set up to gather, and import, as much conversion data as possible to the Google Ads API. To do that, you may need to make improvements to your existing conversion import pipeline. Why upgrade? We recommend that you upgrade your conversion import pipeline by gathering and importing more than just GCLIDs.

Durability:

Improve conversion attribution, especially when GCLIDs are missing, by incorporating new data points.
Adapt to evolving privacy regulations and the deprecation of traditional tracking identifiers.

Better modeling:

Provide more data to Google's AI for better campaign optimization.
Get a more complete picture of user behavior and improve model reliability.

Steps to upgrade your conversion import pipeline

Update your Google Ads API version:

Move to Google Ads API version v20 or later. See our release notes and migration guides.

Include user-provided data:

Include hashed user-provided data (email, phone number), when available, to unlock cross-device and engaged-view conversions. See our documentation on sending user-provided data.
Important: Set up your application to import all conversions, even if they only have user-provided data and don’t have a GCLID.

Send additional signals:

Capture and import session attributes by using our JavaScript helper function to generate an encoded token (setting session_attributes_encoded), or by capturing the sub-fields individually as key-value pairs (setting session_attributes_key_value_pairs). We recommend using the JavaScript helper function to provide an encoded token; use of key-value pairs is available for users who cannot generate an encoded token in the browser. User's IP address is also available as a new field, though reporting and bidding benefits will become available in the future.
Make sure you provide users with clear and comprehensive information about the data you collect on your sites, apps, and other properties and get consent where required by law or any applicable Google policies.

Adopt Braid (gbraid & wbraid):

Capture and import these URL parameters for privacy-safe conversion reporting when GCLID and user-provided data are unavailable.
Note: We recently announced that gclid and gbraid can be imported together for a single conversion starting on Oct. 3, 2025.

Implement order ID:

Set the order_id field with a unique identifier. This helps reference conversions when adjustments or retractions are needed.

Provide conversion environment:

Set the conversion_environment field to specify whether the conversion source is APP or WEB.
Note: We recently announced that conversion environment data will start informing bidding models for in-app conversions in late September.

Consent and data sharing responsibilities:

Advertisers are responsible for ensuring they have the right to share all data uploaded to Google. Make sure you set the consent field on all imported conversions.

Reach out to the Google Ads API support channel if you have any questions.

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

Google Ads API documentation gets a major upgrade!

jueves, 14 de agosto de 2025

We're thrilled to announce significant improvements to the Google Ads API documentation, designed to make your development experience smoother, faster, and more intuitive. These changes are a direct result of valuable feedback from our incredible API developer community. Our goal was simple: enhance discoverability and reduce the need to jump between pages, so you can spend less time searching and more time building. Let's dive into what's new: 1. Easier campaign type discovery and implementation One of the most requested features was clearer guidance on supported campaign types. You can now more easily identify which campaign types the API supports and, crucially, find all the resources you need to implement them directly within the documentation. This streamlines your workflow from discovery to deployment.

2. Unified reporting and reference documentation We've merged our Reporting and Reference documentation into a single location. This means all your essential references are now together, providing a more comprehensive and less fragmented experience when you're working with data and API specifics. 3. Seamless gRPC and REST integration For those who switch between gRPC and REST, we've introduced a highly anticipated feature: a one-button toggle!

This lets you effortlessly switch between the two protocols on the same page. If you haven't yet, we highly recommend trying out our Try-it feature directly from the developer site. With gRPC and REST now co-located, accessing Try-it is more efficient than ever, making it perfect for quickly testing new features and requests. 4. Reorganized and clustered guides All your familiar guides are still there, but we've given them a thoughtful re-ordering. Guides with similar features are now clustered together, creating a more logical flow and helping you navigate to related topics more quickly. This thoughtful reorganization aims to reduce friction and enhance your learning. We want your feedback! These changes are just the beginning, and your feedback is crucial as we continue to refine and improve. If you have any thoughts on these updates, or suggestions for future enhancements, please click the Send Feedback button at the bottom of any page in the documentation.

This direct line lets you provide valuable input that will help shape the future of the Google Ads API documentation. We're incredibly excited about these updates and believe they will significantly enhance your experience with the Google Ads API. Happy coding!

- Lois Patterson, Google Ads API Team

Changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

jueves, 7 de agosto de 2025

What’s changing? As announced last year, Google will stop serving political advertising in the European Union ahead of a new regulation taking effect in October 2025. On September 3, 2025, the Google Ads API and Google Ads scripts will roll out enforcements related to this change. If you use either of these products to create or manage campaigns, you may need to update your application to handle these enforcements before September 3, 2025. API support for self-declaration of EU political ads Google Ads API and Google Ads scripts have added support for self-declaration as to whether a campaign has EU political ads. Learn how an EU political ad is defined here. Versions v19.2, v20.1, and v21 of the API contain a new field named contains_eu_political_advertising in the Campaign object. The possible values and their meaning are shown in the table below.

Value

Meaning

CONTAINS_EU_POLITICAL_ADVERTISING

The campaign has EU political ads.

DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING

The campaign does not have EU political ads.

UNSPECIFIED

The campaign is missing self-declaration about EU political ads.

You can retrieve the self-declaration status of a campaign in Google Ads API by running the following query using either the Search or SearchStream methods of the GoogleAdsService. For Google Ads Scripts, use the AdsApp.search or AdsApp.report methods. select campaign.id, campaign.contains_eu_political_advertising from campaign If you use the Google Ads API client libraries, you may need to download the latest library version to use this functionality in versions v19 and v20 of the API. API validation & enforcement changes On September 3, 2025, Google Ads API and Google Ads scripts will start enforcing the following checks in versions v19 and v20 of the API.

All new campaigns created either through Google Ads API or Google Ads scripts should set the contains_eu_political_advertising field. The API call to create a new campaign using CampaignService.MutateCampaigns will fail with a FieldError.REQUIRED error if this field is not set. Google Ads Scripts will enforce these checks when creating campaigns using AdsApp.mutate or AdsApp.mutateAll methods.

All the existing campaigns should set the contains_eu_political_advertising field before attempting to change proximity, location, or location_group targeting either at the campaign or ad group levels. The API call to create or update these campaign criteria using CampaignCriterionService.MutateCampaignCriteria method for existing campaigns will fail with a CriterionError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION error if the campaign hasn’t completed the self-declaration. The API call to create or update these ad group criteria using AdGroupCriterionService.MutateAdGroupCriteria will also fail in a similar manner if the campaign hasn’t completed the self-declaration. Google Ads scripts will enforce these checks when attempting to change targeting using AdsApp.mutate, AdsApp.mutateAll, AdsApp.Campaign.addProximity, and AdsApp.Campaign.addLocation methods.

These enforcements also apply to other mechanisms that you can use to make campaigns, such as running Batch Jobs and using GoogleAdsService.Mutate method to create and update entities.

Attempting to schedule a new experiment using ExperimentService.ScheduleExperiment method will throw an ExperimentError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION error if the contains_eu_political_advertising declaration is missing on the treatment draft campaigns.

If you use the bulk upload feature in Google Ads scripts, check the product documentation to learn more about the spreadsheet template changes required as part of this change.

These checks are already enforced in version v21 of the Google Ads API. How will this affect my campaign serving? Any campaign that has declared EU political ads by setting contains_eu_political_advertising to true will stop serving ads in the EU on September 22, 2025. Refer to our Help Center to learn more. Existing campaigns without a declaration will remain unaffected for now. We recommend updating the existing campaigns in your accounts with an appropriate declaration as soon as possible. You can retrieve campaigns without a declaration using the following GAQL query using either the Search or SearchStream methods of the GoogleAdsService. select campaign.id, campaign.contains_eu_political_advertising from campaign where campaign.contains_eu_political_advertising NOT IN ( 'CONTAINS_EU_POLITICAL_ADVERTISING', 'DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING' ) What do I need to do? If your application uses either Google Ads API or Google Ads scripts to create or manage campaigns, make sure to update your application to handle these enforcements before September 3, 2025. How do I get help? Reach out to the Google Ads API support or Google Ads scripts support channels if you have more questions about this change.

- Anash P. Oommen, Google Ads API Team

Announcing v21 of the Google Ads API

miércoles, 6 de agosto de 2025

Today, we’re announcing the v21 release of the Google Ads API. To use some of the v21 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published. As previously announced, we are also releasing minor versions v20.1 and v19.2 of the Google Ads API. Here are some of the key features in this release:

We have added a new field named contains_eu_political_advertising for the Campaign object. Use this field to self-declare whether your campaign contains political advertising content targeted towards the European Union. If this field is set to true, the campaign will no longer serve in the EU starting September 23, 2025. This feature is also released in versions v20_1 and v19_2 of the API so you can start using this feature immediately without upgrading to the latest version of the API. See our blog post to learn more.

A new view campaign_search_term_view aggregates search term data at the campaign level and exposes search term data for Performance Max campaigns. We encourage you to migrate from search_term_view to campaign_search_term_view if you are interested in fetching search term data for Performance Max campaigns.

Brand guidelines will automatically be enabled on new campaigns.

You can now use the ai_max_setting.enable_ai_max field of the Campaign object to enable AI Max for Search campaigns. Google Ads AI Max is a suite of AI-powered features for standard Search campaigns designed to increase conversions and reach. It works by using machine learning to expand keyword targeting, dynamically generate ad creatives based on user intent, and send users to the most relevant landing pages on your website. Refer to our blog post to learn more. A new view ai_max_search_term_ad_combination_view exposes search term data for AI Max for Search campaigns. We plan to launch a consolidated version of this view including data from other campaign types in a future API version.

We are allowing Terms & Service, QR codes, and various other barcodes to be added to PromotionAssets.

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

Release Notes

Upgrade from a previous version

Guides

Reference

Diff between v21 and v20

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

- Anash P. Oommen, Google Ads API Team

Unlocking enhanced Performance Max targeting in the Google Ads API

lunes, 4 de agosto de 2025

This blog post was updated on August 12, 2025 to add clarification on how to attach a negative keyword list to your campaign. We're excited to announce the launch of three powerful new features for Performance Max campaigns within the Google Ads API. These updates will give you greater control and flexibility over your Performance Max campaigns, allowing for even more precise targeting and optimization. Available today across all supported versions of the Google Ads API, these features empower developers and advertisers to refine their Performance Max strategies. Introducing new targeting capabilities1. Device targeting With the introduction of device targeting, you now have the ability to specify at the campaign level where your Performance Max ads will appear. This feature provides a new layer of control, enabling you to optimize your campaign reach across various platforms. To set up device targeting, add a DeviceInfo criterion to your Performance Max campaign. 2. Negative keyword lists To help prevent your ads from showing for irrelevant searches, we're introducing support for negative keyword lists at the campaign level on Performance Max campaigns. This highly requested feature allows you to upload and apply lists of keywords that you want to exclude, ensuring your ads are displayed to the most relevant audience. You can attach a negative keyword list to your campaign by attaching a SharedSet with the type NEGATIVE_KEYWORDS using the CampaignSharedSetService. Refer to this page for an example on how to attach a negative keyword set to a campaign. 3. Age range exclusions We're also adding the capability to exclude specific age ranges from your Performance Max campaigns. This allows for more granular audience targeting, which helps you comply with age-related advertising regulations and focus your spend on the most appropriate demographics for your products or services. To set up an age range exclusion, add an AgeRangeInfo as a negative criterion on your PMax campaign. How to get started These new features are available starting today on all supported versions of the Google Ads API. For detailed documentation on how to implement these new targeting options in your Performance Max campaigns, refer to our developer guides. We're committed to continually enhancing the Google Ads API to provide you with the tools you need to succeed. We encourage you to explore these new features and incorporate them into your Performance Max strategies to achieve even better results.

- Sarah Pollack, Google Ads API Team

July 2025 update to Display & Video 360 API

jueves, 31 de julio de 2025

Today, we’re announcing the July 2025 update to the Display & Video 360 API. This update includes the following:

Support for campaign and insertion order targeting in v4, bringing it to parity with v3.

The ability to retrieve video ad inventory control settings for YouTube & Partners line items.

For more details, see the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version. Display & Video 360 API v3 will sunset on October 7, 2025. If you are still using v3, update your integration to use v4 as soon as possible. Follow the steps in our v4 migration guide to migrate. If you need help with these new features, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Version Support Changes for the Google Ads API Python Library

jueves, 24 de julio de 2025

In October, 2025, Python 3.9 will reach end-of-life in October 2025 and will no longer be supported by the Python Software Foundation. Once Python 3.9 officially reaches end-of-life status, it will also no longer be supported by the Google Ads client library for Python. That means we will not make updates to the library, or address any issues related to compatibility with Python 3.9, outside of critical security updates. In Q4 2025 we will release a new major version of the library that is incompatible with Python 3.9. This new version will include support for Python 3.14. Users of deprecated, or soon-to-be deprecated versions of Python, are at risk of losing access to the Google Ads API. Please note the below timelines:

Current: Python 3.7 users cannot currently access the Google Ads API

Q1 2026: Python 3.8 users will lose access to the API when version v19 of the Google Ads API is sunset in Q1 2026.

Late 2026: Python 3.9 users will lose access to the API when version v22 of the Google Ads API is sunset in late 2026

Follow the deprecation and sunset timetable for updates around the specific timing of Google Ads API version releases and sunsets. Any library users currently relying on Python 3.8 or 3.9 should upgrade their systems to Python 3.10 or higher as soon as possible. If you have any questions about this change, please file an issue on the client library repository.

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

Increased flexibility for Google Ads API conversion imports

martes, 22 de julio de 2025

Starting on October 3, 2025, you will be able to set both the gclid and gbraid fields on your ClickConversion messages when importing them to the Google Ads API, by using the UploadClickConversions method. Previously, setting both of these fields resulted in the following partial failure error:

error_code: FieldError.VALUE_MUST_BE_UNSET

location.field_path_elements.field.field_name: gclid

Once this change is released, this error will no longer be returned. Instead you will see successful import responses.

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

What you need to know about the business name and logo asset migration in PMax Campaigns

lunes, 14 de julio de 2025

What’s changed? Today, we're excited to announce that the brand guidelines rollout is now complete for all new Performance Max campaigns created through the Google Ads UI, with API-created accounts soon to follow. As was first announced in December, this means that new PMax campaigns initiated in the UI will have brand guidelines enabled by default, offering advertisers greater control over their brand's representation. With brand guidelines rolling out to more Performance Max campaigns, it is crucial to understand how this impacts campaigns you interact with via the API, and for you to update your code in advance to prepare for it. What do API Users need to update now? Previously, brand assets such as your business name and logo were associated with Asset Groups. Currently, for any PMax campaign with brand guidelines enabled, these brand assets are now stored at the campaign level. This means if your application queries or modifies brand assets for PMax campaigns, you must adjust your code to look for these assets in CampaignAsset instead of AssetGroupAsset for these campaigns. Accounting for both asset locations in your application is vital to ensure your integrations continue to function as expected. To determine if brand guidelines are enabled for a PMax Campaign, check the Campaign.brand_guidelines_enabled field. What do API Users need to plan for in the future? Brand guidelines will be enabled by default when creating PMax Campaigns using the API beginning in v21. You can optionally disable brand guidelines by setting the Campaign.brand_guidelines_enabled field to false on-creation. The default behavior for brand guidelines on new Performance Max campaigns created via the API remain disabled for all supported versions through v20. To manually turn on brand guidelines through the API, you have two options:

Starting in v19, all API users can choose to manually enable brand guidelines when creating a new PMax campaign. To do so, you need to set the Campaign.brand_guidelines_enabled field to true during campaign creation. You can refer to the “Add Performance Max Campaign” code sample for an example of how to create a campaign with brand guidelines enabled.

To manually enable brand guidelines for an existing campaign, use CampaignService.EnablePMaxBrandGuidelines. Set auto_populate_brand_assets to true to automatically populate the campaign with top-performing brand assets. Disabling brand guidelines for a campaign after its creation is not supported.

There is an in-progress automatic migration to enable brand guidelines for existing campaigns. As previously announced, this migration has already begun on a rolling basis by CID. Only campaigns that use the same logos and business name across all asset groups will be automatically migrated. We anticipate the migration to be completed for all applicable CIDs by October 30th. In the meantime, we encourage you to use the existing migration endpoint to manually update your campaigns to brand guidelines at your own pace.

- Sarah Pollack, Google Ads API Team

Ads Developer Blog

Explorer access is now available for Google Ads API developers

October 2025 update to Display & Video 360 API

Announcing v22 of the Google Ads API

Upgrade your Call-Only Ads to Responsive Search Ads with Call Assets in the Google Ads API

Bidding enforcement for conversion environment in in-app conversions no longer planned

Open Source Google Ads API MCP Server

Correction of an error in the BudgetPerDayMinimumErrorDetails message

Google Mobile Ads Mediation adapters adopt Swift Package Manager

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

Introducing improved diagnostics for enhanced conversions for leads imports

Google Ads scripts documentation upgrade

Introducing the google-ads-bom to the Google Ads API client library for Java

Launching Structured Data Files v9.1

More frequent releases coming for the Google Ads API

Announcing v5 release and changes for supporting European Union Political Ads Regulation in Campaign Manager 360 API

Changes for supporting European Union Political Ads Regulation in Display & Video 360 API and Structured Data Files

Maximize the performance of your Google Ads conversion data

Google Ads API documentation gets a major upgrade!

Changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

Announcing v21 of the Google Ads API

Unlocking enhanced Performance Max targeting in the Google Ads API

July 2025 update to Display & Video 360 API

Version Support Changes for the Google Ads API Python Library

Increased flexibility for Google Ads API conversion imports

What you need to know about the business name and logo asset migration in PMax Campaigns

Etiquetas

Archive