Tag Archives: google_ads

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

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

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

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

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