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:

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. 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.
3. If you do include conversion_environment data for your imported conversions, it ensures attribution accuracy and campaign effectiveness.
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

In v21 of the Google Ads API, the UploadClickConversion method’s debug_enabled setting will be removed. Starting on August 6, 2025, all the previous versions (v18, v19, and v20) will ignore this setting if it’s set as part of a request.

As a result of this change, Google Ads API will no longer return ConversionUploadError.CLICK_NOT_FOUND errors, because setting the debug_enabled field to true is the only way to retrieve it. This error code will be removed from the Google Ads API in a future version.

Here’s a breakdown of how this change will materialize in each Google Ads API version:

• v21:
  • The debug_enabled field will be removed from the UploadClickConversionsRequest message.
  • ConversionUploadError.CLICK_NOT_FOUND errors will not be returned.
• v18, v19, and v20:
  • The debug_enabled field will be present on the UploadClickConversionsRequest message, but it will not be functional.
  • ConversionUploadError.CLICK_NOT_FOUND errors will not be returned.

If your application uses this field or error code, make sure you update your application to handle the new API behavior.

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

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

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

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

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

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

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

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

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

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