Google Ads Developer Blog: google

Changes to Offline Click Conversion Import Support in the Google Ads API

2026 m. gegužės 15 d., penktadienis

Starting on June 15, 2026, the Google Ads API will no longer accept new adopters of offline conversion imports, including enhanced conversions for leads. As with our previous announcements for session attributes and IP address, and Customer Match, Data Manager API is now the primary API for importing offline conversions. Developers who have not adopted offline conversion imports or Enhanced conversion for leads, or have not imported offline conversions between December 2025 and May 2026, will receive an error if they attempt to import offline conversions. Developers who have already adopted offline conversions or Enhanced conversions for leads can continue importing using the Google Ads API while they integrate with the Data Manager API. See our migration guide for Google Ads API users to start integrating with the Data Manager API. Technical details

Developers will be allowlisted by their developer token.

Once this change is rolled out, new adopters will receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting to use the ConversionUploadService.UploadClickConversions method.

See the documentation for integrating with the Data Manager API for offline conversion imports for Google Ads API users.

Reach out to the Google Ads API support or Data Manager API support channels if you have any questions. 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.

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

Announcing expanded experiment functionality in Google Ads API v24.1

2026 m. gegužės 14 d., ketvirtadienis

We are excited to announce a significant expansion of the Google Ads A/B experiments feature set in the v24.1 release, launched yesterday, May 13, 2026. We know API functionality is critical for advertisers who manage large sophisticated accounts, and we want to give these advertisers the capability to better create and manage their A/B experiments at scale. This update broadens the platform's current scope, enabling advertisers to leverage the power of experiments for a broader range of testing scenarios to drive campaign performance. Direct experiment reporting One of the most requested enhancements is the ability to query experiment statistics directly through the API. Previously, you had to manually calculate statistics by querying campaign resources. With v24.1, we are exposing experiment arm-level and significance stats, including:

Control arm stats: The average value of metrics in the control arm.

Point estimates: The mean value of the difference between the control and treatment arms, calculated via the jackknife method.

Margin of error: The radius of the confidence interval.

P-values: Represents the calculated probability that the difference could have occurred by chance.

New experiment types We are expanding support for a variety of experiment types to help you find the best configurations for your business:

Feature-specific tests (AI Max and broad match): Test the impact of enabling AI Max or broad match keywords. These use an intra-campaign workflow, where the feature is tested within the original campaign shared by both the control and treatment arms.

Custom video experiments: Run custom experiments consisting of Video campaigns.

Performance Max replacement: Test how your Shopping campaigns perform compared to Performance Max.

Performance Max asset optimization: Specifically for Performance Max, you can test different variations of assets including text, images, and videos. This asset optimization workflow helps determine which creative combinations drive the best results.

While these updates cover a significant number of use cases, we are continuing to work on the platform and plan to introduce even more experiment types in future releases. Where can I learn more? Updated documentation and code examples are available on the Google Ads API Developer site. We also encourage you to join the discussion and share your feedback on our Ads and Measurement Community Discord server.

- Laura Chevalier, Google Ads API Team

Google Ads API v20 sunset reminder

2026 m. balandžio 29 d., trečiadienis

Google Ads API v20 will sunset on June 10, 2026. Starting on this date, all v20 API requests will begin to fail. Migrate to a newer version prior to June 10, 2026 to ensure your API access is unaffected. Here are some resources to help you with the migration:

Upgrade to the newest version

Release notes

You can view a list of methods and services your project has recently called using the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.

Click Google Ads API in the table.

On the Metrics subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as

google.ads.googleads.v20.services.GoogleAdsService.Mutate.

(Optional) Choose the timeframe you want to view for your requests.

If you have any questions or want to discuss this post, please reach out to Google Ads API support or start a discussion on our “Google Advertising and Measurement Community” Discord server.

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

Simplifying Keyword Forecast Metrics in Google Ads API v24

2026 m. balandžio 23 d., ketvirtadienis

To provide a more streamlined and reliable experience, we have unified our forecasting infrastructure. Google Ads API v24 introduces an updated GenerateKeywordForecastMetrics method that simplifies the planning process by focusing on the metrics that most directly impact your performance. What's changing? To streamline our systems and focus on the primary data that drives successful Search planning, Google Ads API v24 introduces the following refinements: 1. Alignment with Bidding Strategies To provide a more consistent experience across Google Ads tools, forecasts now focus exclusively on the primary metrics that your chosen bidding strategy directly impacts. This alignment ensures that the data you use for planning is synchronized with the high-impact performance indicators for your actual campaigns:

Manual CPC and Maximize Clicks: Forecasts provide clicks, average CPC, and cost.

Maximize Conversions: Forecasts provide conversions, average CPA, and cost.

Metric Focus: To maintain consistency across the platform, forecasts no longer include cross-metric data (such as conversion estimates for click-oriented strategies) or secondary metrics like impressions and conversion value.

2. Streamlined Request Parameters We have made the following updates to simplify forecasting requests, improve system reliability, and remove inputs which have a minimal effect on overall forecast accuracy:

CampaignToForecast.geo_modifiers[] is replaced by CampaignToForecast.geo_target_constants[]

ForecastAdGroup.biddable_keywords[] is replaced by ForecastAdGroup.keywords[].

The following fields are removed:

CampaignToForecast.keyword_plan_network
CampaignToForecast.negative_keywords
ForecastAdGroup.max_cpc_bid_micros
ForecastAdGroup.negative_keywords
CriterionBidModifier

Timeline The transition follows our standard release and sunset cycle:

April 2026: Google Ads API v24 is available with the updated GenerateKeywordForecastMetrics functionality.

February 2027: Google Ads API v23 is scheduled for sunset. At this time, all versions of the Google Ads API will utilize this unified forecasting infrastructure.

Next Steps Developers that use GenerateKeywordForecastMetrics should review their integrations to ensure compatibility with the updated parameter set in v24. Review the Generate Forecast Metrics guide and the GenerateKeywordForecastMetrics v24 reference for the latest usage details. If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our Ads and Measurement Community Discord server.

- Laura Chevalier, Google Ads API Team

New Data Manager API channels on Discord

2026 m. balandžio 7 d., antradienis

We're excited to announce the addition of new channels for the Data Manager API on our “Google Advertising and Measurement Community” Discord server. To join, just click this invite link and follow the onboarding guide. Our team will be on this server regularly to interact with the Data Manager API community, answering questions and gathering feedback in the #data-manager-api channel. We’ll also keep you up to date on the latest Data Manager API news in the #announce-data-manager-api channel. If you have any questions or want to discuss this post, please reach out to us on the “Google Advertising and Measurement Community” Discord server. We look forward to seeing you there and hearing your thoughts on how we can continue to improve the Data Manager API!

- Josh Radcliff, Data Manager API Team

Changes to Customer Match Support in the Google Ads API

2026 m. kovo 4 d., trečiadienis

Starting on April 1, 2026, the Google Ads API will no longer accept new adopters of Customer Match. As with our recent announcement for the use of session attributes and IP address in click conversions in the Google Ads API, we’re recommending that new adopters of Customer Match integrate with the Data Manager API as their primary user data import API. Developers who have not adopted Customer Match, or have not uploaded data to a Customer Match list between October 2025 and March 2026, will receive an error if they attempt to upload to a Customer Match list. Developers who have already adopted Customer Match can continue importing user data using the Google Ads API while they integrate with the Data Manager API. Technical details

Developers will be allowlisted by their developer token.

Once this change is rolled out, users who are not on the allowlist will receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting to upload user data to a Customer Match list using either the OfflineUserDataJobService or UserDataService.

See the documentation for integrating with the Data Manager API for Customer Match imports for Google Ads.

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

Introducing Channel-Level Reporting for Performance Max campaigns

2026 m. sausio 29 d., ketvirtadienis

Following yesterday's launch of Google Ads API v23, we are excited to share more details about one of the most highly requested features: Channel-level reporting for Performance Max campaigns. This update provides developers and advertisers with unprecedented transparency into where their Performance Max ads are serving, allowing for deeper optimization and more granular performance insights. Greater transparency with channel breakdowns Starting with v23, you can now retrieve performance data broken down by channel—such as Google Search, Search Partners, GMail, YouTube, Display, Discover, and Maps. This functionality is available at the campaign, asset group and asset level, allowing you to see how specific creative assets are performing across different environments. In previous versions of the API, using the ad_network_type segment for Performance Max campaigns typically returned a MIXED enum value. With the release of v23, the API will now return the specific channel breakdowns. Note for developers: This is a significant change in behavior. When you upgrade your queries to v23, you will begin to see more detailed results than in previous versions. Please ensure your reporting systems are prepared to handle these specific enum values instead of the generic MIXED result. Additional segments to consider While the channel breakdown is new to v23, it works in tandem with powerful segmentation fields introduced in v22: ad_using_product_data and ad_using_video.

ad_using_product_data: Use this segment to distinguish performance between ads that utilize your Merchant Center product feed versus those that do not.

ad_using_video: This segment allows you to isolate performance data for ad impressions that included a video component.

By combining these segments with the new v23 channel reporting, you can now gain highly specific insights, such as understanding the conversion value of video-based ads specifically on the YouTube channel versus the Display Network. Or if you’re a retailer, use the ad_using_product_data segment to see data for Shopping ads for Search, Dynamic Remarketing ads for Display and video ads that showcase your products on YouTube. Implementation details To get started with these new reporting capabilities, you should update your client libraries to v23. You can find detailed technical documentation and example queries in our PMax reporting guides. Important notes:

Performance reports will only return channel-level data for dates on or after June 1, 2025.

While channel reporting is available at the campaign, asset group, and asset levels via the API, reporting at the asset group level is exclusive to the API and will not be available in the Google Ads web interface.

If you have any questions or want to discuss this post, please reach out to Google Ads API support or start a discussion on our “Google Advertising and Measurement Community” Discord server.

- Sarah Pollack, Google Ads API Team

Changes to IP Address and Session Attribute Support in the Google Ads API

2026 m. sausio 7 d., trečiadienis

Starting on February 2, 2026, the Google Ads API will no longer accept new adopters of session attributes or IP address data as part of conversion imports. To ensure a more robust and scalable experience for handling complex data, we recommend that Google Ads API developers transition to the Data Manager API - where session attributes and IP address are accepted - as their primary conversion and user data import API. Developers who have already adopted session attributes or IP addresses in their click conversion imports can continue importing that data using the Google Ads API until they’ve moved their conversion imports over to the Data Manager API. Technical details

Developers will be allowlisted by their developer token.

Once this change is rolled out, you may notice the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in the partial_failure responses of your conversion import requests. This error indicates that the associated conversion was rejected due to the presence of session attributes and/or IP address.

Resolve this error with these steps:

Temporarily remove session attributes and IP address from conversion import requests and continue importing conversions to the Google Ads API.
Update your code to use the Data Manager API with session attributes and IP address.
Discontinue conversion imports to the Google Ads API once you’re successfully making imports to the Data Manager API.

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

Google Ads API v19 sunset reminder

2025 m. gruodžio 15 d., pirmadienis

Google Ads API v19 will sunset on February 11, 2026. Starting on this date, all v19 API requests will begin to fail. Migrate to a newer version prior to February 11, 2026 to ensure your API access is unaffected.Here are some resources to help you with the migration:

Upgrade to the newest version

Release notes

You can view a list of methods and services your project has recently called using the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.

Click Google Ads API in the table.


  google.ads.googleads.v19.services.GoogleAdsService.Mutate

(Optional) Choose the timeframe you want to view for your requests.

If you have questions while you're upgrading, reach out to us at googleadsapi-support@google.com. 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

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

2025 m. spalio 8 d., trečiadienis

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

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

2025 m. rugsėjo 25 d., ketvirtadienis

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

2025 m. rugsėjo 23 d., antradienis

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

Maximize the performance of your Google Ads conversion data

2025 m. rugpjūčio 20 d., trečiadienis

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!

2025 m. rugpjūčio 14 d., ketvirtadienis

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

Unlocking enhanced Performance Max targeting in the Google Ads API

2025 m. rugpjūčio 4 d., pirmadienis

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

Version Support Changes for the Google Ads API Python Library

2025 m. liepos 24 d., ketvirtadienis

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

2025 m. liepos 22 d., antradienis

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

2025 m. liepos 14 d., pirmadienis

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

Join our “Google Advertising and Measurement Community” Discord Server

2025 m. liepos 8 d., antradienis

We’re launching our new “Google Advertising and Measurement Community” Discord server! To join, just click this invite link and follow the onboarding guide. The current products available on this server are Analytics, Google Ads, Google AdMob, and Google Ad Manager. The Ads Developer Relations team will be on this server regularly to discuss your feedback or questions using Google’s Advertising and Analytics APIs/SDKs, as well as to let you know what’s new with our products. We’ll be hosting a “Meet the Team” in August, where we’ll go over who we are, and how you can expect to engage with us in Discord. Stay tuned as we add other events, and more channels. Looking forward to chatting with you on Discord!

- Cory Liseno, on behalf of the Ads Developer Relations Team

[Update] Add Conversion Environment to Google Ads Conversion Imports

2025 m. birželio 30 d., pirmadienis

The previously announced September 30, 2025 deadline to include the ClickConversion.conversion_environment parameter has been removed. The changes described in this blog post will not be released and no further action is required for this specific update. For more details see our Help Center article. Previously we announced that, starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. The timing and details for this rollout have changed. Now, starting September 30, 2025, we will begin gradually rolling out a change to our bidding models so that they will start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions to ensure accurate attribution for smarter bidding and optimal campaign performance. This means that if you are using the Google Ads API to measure in-app conversions, your campaign performance may degrade if the ClickConversion.conversion_environment field is not set. For developers importing in-app conversions, the following considerations still apply:

In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.

Once this bidding model change is launched to a campaign, if you do not include the conversion_environment field when importing conversions, you may observe fewer in-app conversions and worse overall campaign performance.

If you do include conversion_environment data for your imported conversions, it ensures attribution accuracy and campaign effectiveness.

The presence or absence of the conversion_environment parameter does not impact conversion uploads. These conversions will still be consumed and reported, with no error messages.

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

Ads Developer Blog

Changes to Offline Click Conversion Import Support in the Google Ads API

Announcing expanded experiment functionality in Google Ads API v24.1

Google Ads API v20 sunset reminder

Simplifying Keyword Forecast Metrics in Google Ads API v24

New Data Manager API channels on Discord

Changes to Customer Match Support in the Google Ads API

Introducing Channel-Level Reporting for Performance Max campaigns

Changes to IP Address and Session Attribute Support in the Google Ads API

Google Ads API v19 sunset reminder

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

Streamlined Account-Default CustomerConversionGoal Behavior in Google Ads

Introducing improved diagnostics for enhanced conversions for leads imports

Maximize the performance of your Google Ads conversion data

Google Ads API documentation gets a major upgrade!

Unlocking enhanced Performance Max targeting in the Google Ads 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

Join our “Google Advertising and Measurement Community” Discord Server

[Update] Add Conversion Environment to Google Ads Conversion Imports

Etiketės

Archive