Tag Archives: google_ads_api

Add Conversion Environment to Google Ads Conversion Imports

Starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. See this article for more details.

For developers importing in-app conversions, please observe these considerations:

  1. In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.
  2. For existing campaigns, if you do not include the conversion_environment field when importing conversions, that will negatively impact bidding, resulting in fewer conversions and worse overall performance.
  3. For new campaigns, if you upload conversion_environment data, that will directly improve campaign performance by driving additional app conversions.
  4. 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

Add Conversion Environment to Google Ads Conversion Imports

Starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. See this article for more details.

For developers importing in-app conversions, please observe these considerations:

  1. In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.
  2. For existing campaigns, if you do not include the conversion_environment field when importing conversions, that will negatively impact bidding, resulting in fewer conversions and worse overall performance.
  3. For new campaigns, if you upload conversion_environment data, that will directly improve campaign performance by driving additional app conversions.
  4. 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

New UI-Only Image Optimization Features for Performance Max Campaigns

We're providing an important update regarding new image optimization features rolling out in the Google Ads user interface, specifically impacting Performance Max campaigns.

What are these new UI features?

  • Landing Page Images: This setting allows Google AI to automatically source relevant images directly from your ad's landing page. The aim is to dynamically incorporate these visuals into your ads, potentially improving relevance and extending your reach across more placements.
  • Image Enhancements: With this feature, Google AI can automatically make improvements to your uploaded image assets. This can include smart cropping to create different versions of your images, helping to unlock more ad inventory and boost performance. Future enhancements may also include capabilities like uncropping or animating images.

You can find more information about these features in the Google Ads Help Center.

Automatic Opt-In:

Please be aware that image enhancements will be on by default for all Performance Max users. Landing Page Images will be on by default if the user has account level dynamic image settings turned on.

Key Information for API Users:

At this time these new UI features for Performance Max campaigns can only be managed with the Google Ads user interface.

  • These features will not be viewable through the Google Ads API.
  • At this time, you will not be able to opt-in or opt-out of these new settings (Landing Page Images and Image Enhancements) using the Google Ads API. To change the status of these settings you must use the Google Ads UI.

API Integration Impact:

Your existing API integrations will continue to function for the features and settings currently supported by the API. However, these new additional Performance Max settings will need to be managed by your users directly in the Google Ads interface.

We encourage you to familiarize yourselves with the details provided in the Google Ads Help Center to understand the scope of these UI changes for Performance Max campaigns. This will enable you to effectively support your users and clarify what can and cannot be controlled via the API.

We are committed to keeping our developer community informed. Stay tuned to this blog for further updates on control of these image optimization settings in the Google Ads API.

 - Sarah Pollack, Google Ads API Team

Google Ads AI Max for Search campaigns Open Beta

The open beta launch of AI Max for Search campaigns in the Google Ads UI will begin on 27 May 2025.

While full AI Max for Search campaigns support in the Google Ads API is planned for v21 in August 2025, we want to ensure you're prepared for the open beta rollout and understand its potential impact on your API interactions.

What is AI Max for Search campaigns?
What is Changing?
During the open beta period, before full API support arrives in v21, there will be a transitional phase. Here's what API users need to know:
  1. Feature Grouping in the UI: When a user enables AI Max for Search campaigns for a campaign in the Google Ads UI, several legacy features will be grouped into the new AI Max for Search campaigns settings:
    • Text customization (formerly known as Automatically created assets (ACA))
    • Campaign-level broad match (the setting itself)
    • Brand inclusions (previously tied to campaign-level broad match)
    • Campaign-level brand exclusions
  2. Potential API Conflicts During Transition: Once AI Max for Search campaigns has been enabled and then disabled for a campaign via the UI, managing its associated features (ACA, brand list inclusions/exclusions) using any API version is subject to feature grouping and may cause errors. Starting with v21, AI Max for Search campaigns can be activated through the API.
    • Why? Disabling AI Max for Search campaigns in the UI during this interim period doesn't fully revert the underlying settings configuration back to the pre-AI Max for Search campaigns state compatible with older API versions for these specific features.
    • Campaign-Level Broad Match: Attempts to toggle the campaign-level broad match setting via the API will be allowed but may function differently depending on the AI Max for Search campaigns state. Keywords will still be converted to Broad Match if the setting is enabled via the API, but the primary control mechanism moves to AI Max for Search campaign.
    • Text customization: Attempts to deactivate text customization via API requests will raise an error if Final URL expansion is enabled in the UI.
  3. Mitigation - UI Warnings: To prevent accidental disruption, the Google Ads UI will display warning messages when enabling or disabling AI Max in Search campaigns for campaigns that use these legacy features, explicitly mentioning the potential impact on API workflows during this beta period.
  4. Recommendation: We strongly advise coordinating within your teams. If your organization relies heavily on API workflows for managing ACA or Brand Lists, be cautious about enabling and then disabling AI Max in Search campaigns in the UI for those campaigns until full API support lands in v21 in August 2025.
What Stays the Same:
  • You can continue to manage existing Search campaigns using ACA, campaign-level broad match, and brand exclusions via the current API version (v19) as long as AI Max in Search Campaigns has not been enabled and then disabled for those specific campaigns in the UI.
  • Ad Group level Brand Inclusions and Locations of Interest (LOI) pilots (outside of AI Max for Search campaigns) are ending. Functionality for these will only be available within AI Max for Search campaigns going forward.
Preparing for the Future - v21 and beyond:
  • Full Support Coming: API v21 (planned for August 2025) will introduce dedicated fields and services to fully manage all AI Max for Search campaigns features, including the new consolidated controls.
  • Legacy Field Deprecation: Following the launch and adoption of v21, older API versions will sunset. At that point, the legacy fields for ACA, campaign-level broad match, and standalone brand exclusions/inclusions will be fully deprecated and removed from the API.
If you have any questions, please contact us on the forum.
Bob Hancock, Google Ads API Team

Update to the 2025 Google Ads API release schedule

We previously announced our 2025 Google Ads API release plans. We are introducing a few changes to this schedule as a part of our ongoing efforts to evolve our release process. The new schedule lets us make various product features available earlier in the Google Ads API. As usual, additional details on new features will follow as part of the release notes for individual versions.

  1. V20_1 will be upgraded to a major version and named V21.
  2. V21 will be renamed to V22.
  3. We will add two minor releases (v19_2, v20_1) alongside V21 to add these features in existing Google Ads API versions.
  4. The projected launch dates will remain unchanged.

Here’s our updated schedule.

Version Planned Release

Type

Projected launch Projected sunset
V20 Major June/July 2025 June 2026
V21 Major August/September 2025 August 2026
v19_2 Minor August/September 2025 February 2026
v20_1 Minor August/September 2025 June 2026
V22 Major October/November 2025 October 2026

Please take a look at your future plans to make sure they still align with the upcoming Google Ads API release schedule.

How to get help

If you have any questions or need help, check out the Google Ads API support page for options.

 - , Google Ads API Team

Google Ads API v17 sunset reminder

Google Ads API v17 will sunset on June 4, 2025. After this date, all v17 API requests will begin to fail. Migrate to a newer version prior to June 4, 2025 to ensure your API access is unaffected.

Here are some resources to help you with the migration: You can view a list of methods and services your project has recently called using the Google Cloud Console:
  1. In the Google Cloud Console, open the APIs & Services tab.
  2. In the table, click Google Ads API.
  3. 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.v17.services.GoogleAdsService.Mutate.
  4. (Optional) Choose the timeframe you want to view for your requests.
If you have questions while you’re upgrading, reach out to us on the forum or at [email protected].
Benji Rothman, Google Ads API Team

Announcing v19.1 of the Google Ads API

Today, we’re announcing the v19.1 release of the Google Ads API. To use any of the v19.1 features, you must upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This release includes no breaking changes and maintains backwards compatibility for those who have already upgraded to v19.

Here are the highlights:

Where can I learn more?

The following resources can help you get started:

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

 - , Google Ads API Team

Google Ads API Introducing New Error Codes for Invalid Developer Tokens Starting April 28, 2025

Previously, if any Google Ads API request had an invalid developer token, the API returned an OAUTH_TOKEN_HEADER_INVALID error, which is also used for other invalid request header values. To make it clear when the authentication error is specifically caused by an invalid developer token, we are changing the API to return a new error code, DEVELOPER_TOKEN_INVALID, for version v19.1 of the Google Ads API. All API versions before v19 will handle invalid developer tokens by throwing a DEVELOPER_TOKEN_NOT_APPROVED error instead. If you are using version v19 of the API with our client libraries, you will need to update to the latest version of the client libraries after the v19.1 release. These changes will be effective starting April 28, 2025.

Anyone who has already set up the Google Ads API to make successful calls are highly unlikely to be affected by this change. It is mainly meant to improve the experience of new developers onboarding to the API.

If you have any questions, please ask them in the Google Ads API forum. We're here to help!

 - Dora Sun - Google Ads API Team

Upcoming Performance Max campaign migration to enable brand guidelines

Starting on May 1, 2025, we will begin to automatically enable brand guidelines for Performance Max campaigns that use the same brand assets (BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO) across all asset groups.

Please note the rollout timelines:
  • For Google Ads UI users: The process will begin on May 1, 2025 for customer IDs that exclusively manage their campaigns using the UI.
  • For API users: This process will begin on June 1, 2025.
The overall process across all campaigns is expected to be complete by July 31, 2025.

Important Notes:
  • Only campaigns using consistent business names and logo assets across all asset groups will be automatically migrated. Campaigns with variations in these assets will not be migrated.
  • All eligible Performance Max campaigns under a customer ID will be migrated simultaneously.
  • After migration, each migrated campaign will have its own set of brand assets stored at the campaign level using CampaignAsset.
  • You can tell if a campaign has been migrated by checking its Campaign.brand_guidelines_enabled field.
Actions Required
If your application creates asset groups, update your code to check the campaign’s Campaign.brand_guidelines_enabled field. This will tell you whether to include brand assets in the new asset group.

If your application modifies brand assets, update your code to check the campaign’s Campaign.brand_guidelines_enabled field. This will tell you where to save the brand asset; either on a campaign using a CampaignAsset or on an asset group using an AssetGroupAsset.

To avoid extra steps later, we strongly recommend migrating all of your campaigns now using CampaignService.EnablePMaxBrandGuidelines. If you migrate your campaigns manually, each CampaignService.EnablePMaxBrandGuidelines request can only include 10 EnableOperations.

If you have any questions or need help, check out the Google Ads API support page for options.
 - Sarah Pollack, Google Ads API Team

Upcoming change to LowerTargetRoas recommendations in the Google Ads API and Google Ads scripts

As of v17 of the Google Ads API, recommendations of type LOWER_TARGET_ROAS have included a current_average_target_micros as a whole currency value instead of a micros value (where one million is equivalent to one currency unit) as indicated by the field name. On April 23, 2025, we are rolling out a fix to populate current_average_target_micros with the micros value.

Note that as a result of the incorrect unit, the currently returned current_average_target_micros value is truncated and is therefore less precise than the micros equivalent. If you were converting the existing value to micros by multiplying by 1,000,000, the resulting value wouldn't necessarily be correct because any digits past the first position are dropped. For example, a current_average_target_micros value of 5 might have been converted to 5,000,000 in micros before the change, but could be returned as 5,750,000 (more precise) after the change.

What do I need to do?

If you use the Google Ads API or Google Ads scripts to query the recommendation resource for recommendations of type LOWER_TARGET_ROAS, and your application logic uses the current_average_target_micros field, you must update your application to treat the value as micros instead of a whole budget value for when the change takes effect on April 23, 2025.

If you have any questions or need help, check out the Google Ads API support page for options.

 - Laura Chevalier, Google Ads API Team