Tag Archives: offline_conversions

Improvements to conversion adjustment uploads

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:
  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:
  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

Changes to GCLID field length in AdWords API

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