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 September 9, 2024, Google Ads API users will no longer need to wait 24 hours before uploading conversion adjustments - they can be uploaded immediately after the original conversion has been uploaded or recorded by Google tags.

This means that you will no longer need to keep track of the 24-hour window before uploading conversion adjustments, and can stop checking for certain error codes and retrying those upload requests.

Specifically, the following changes will take effect:

1. The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
   • ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION_ACTION
   • ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION
2. Conversion adjustments that would previously be rejected with these error codes will count towards the pending_count in diagnostics until they’re processed, at which point they’ll be counted towards either the successful_count or failed_count fields. This might take up to 24 hours.

Here is how these changes will affect older Google Ads API versions v15 and v16:

1. The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
   • ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION_ACTION
   • ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION
2. Any conversion that would have triggered these codes will, in diagnostic reports, count towards the total_event_count metric while being processed. Once processing is completed they will be counted towards either the successful_count or failed_count. This might take up to 24 hours.

What do I need to do?

1. Remove any logic from your application that waits before uploading adjustments, and begin uploading conversion adjustments at any time after the original conversion has been uploaded.
2. Modify your application logic and business processes so that you are not tracking the two conversion adjustment errors that are being removed.
3. If you rely on the successful or failed event count metrics, revisit your application logic with the understanding that some uploaded events may, at times, when using v17, be represented as pending.

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