Google Ads Developer Blog: offline

[Update] Add Conversion Environment to Google Ads Conversion Imports

Monday, June 30, 2025

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

Upcoming Removal of debug_enabled in Google Ads API Offline Conversion Imports

Thursday, June 26, 2025

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

Add Conversion Environment to Google Ads Conversion Imports

Tuesday, May 27, 2025

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

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

Improvements to conversion adjustment uploads

Monday, August 12, 2024

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:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:

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:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:

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?

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.

Modify your application logic and business processes so that you are not tracking the two conversion adjustment errors that are being removed.

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

Changes to GCLID field length in AdWords API

Wednesday, February 12, 2014

In AdWords API v201309 we released a new Google Click ID field (GCLID) in the Click Performance report. Originally, this field value was limited to 26 characters. We will be extending the maximum length of this field in order to support improvements to our advertising system. Starting March 31st 2014, the value of GCLID can be up to 100 characters long.

Since this value is used in many client systems, we’re giving you advance warning of this change. Make sure your log, storage and redirecting systems can handle the extended size of the GCLID value.

Note: as a result of this change, the Click Performance report will only be available for dates up to 90 days before the time of a request. If you need the older click data, download and store these details before March 31st, 2014.

If you have any questions about the change, reach out to us on the forum or via the Google+ page.

- Danial Klimkin, AdWords API Team

Track your Offline Conversions using AdWords API

Friday, October 11, 2013

Recently we announced the ability to upload offline conversions back into AdWords. This conversion import feature allows you to see how clicks on your ads led to sales made in the offline world such as over the phone or via a sales rep. This feature is now available in v201309 of the AdWords API.

We have published a new guide that explains the API implementation of this feature in detail. We have also added support and code examples for this new feature in all our client libraries.

If you have any questions about this feature or the AdWords API in general, you can post them on our developer forum. You can also follow our Google+ page for updates about the AdWords API.

Anash P. Oommen, AdWords API Team

Ads Developer Blog

[Update] Add Conversion Environment to Google Ads Conversion Imports

Upcoming Removal of debug_enabled in Google Ads API Offline Conversion Imports

Add Conversion Environment to Google Ads Conversion Imports

Improvements to conversion adjustment uploads

Changes to GCLID field length in AdWords API

Track your Offline Conversions using AdWords API

Labels

Archive