The ClickConversion has a value set for gclid as well as at least one of gbraid or wbraid. Update the conversion to use only one click ID, and make sure you are not combining multiple clicks into the same conversion. Each click has only one click ID.
From the provided API logs, it seems that you're currently using version v18 of the Google Ads API. Note that 'v18' was deprecated in June 2025, and will sunset by the end of August 2025. After this date, all v18 API requests will fail.
If you face any other issues while uploading the conversions, please share the latest complete API logs (request and response with request-id and request header) generated at your end.![]() |
Google Ads API Team |
[2025-07-24 13:06:18Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swd17:ref" (ADR-00320034)
Hi,
As informed earlier, please note that Enhanced Conversions for Leads can't be used with either WBRAID or GBRAID identifiers. If you do you will get the VALUE_MUST_BE_UNSET error. Also, please note that click Ids are sent/ fired by the tag implemented for the conversion action. So, if you are uploading offline conversions using enhanced conversions for leads and you are receiving WBRAID or GBRAID instead of GCLID, I would recommend you to verify your tag setup. You can reach out to the Tag Manager support team for assistance required to set up the tag correctly.
In order to assist you further, please provide your Google Ads customer Id, conversion action Id and the complete API logs (request and response with request-id and request header) generated at your end for the conversion uploads without redacting any information. If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
You can send the details via Reply privately to the author option, or direct private reply to this email.
![]() |
Google Ads API Team |
[2025-09-18 23:20:10Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swd17:ref" (ADR-00320034)
Hi,
I understand that the API is returning a 200 response, but the conversions are still failing in your Google Ads account, and you're seeing the "The imported gclid could not be decoded" error when you try to upload them manually.
Based on the information you provided in your initial query, we observed that you are using user identifiers like email. As per the API implementation documentation for enhanced conversions for leads, this is a key component. This is why we initially provided information regarding enhanced conversions.
To investigate your concern further, we'll need a few more details. As you've mentioned you are uploading conversions manually, could you please confirm if you are also experiencing this same issue when uploading conversions via the Google Ads API? If so, please provide the complete API logs (request and response logs with request-id and request header) generated at your end for the failed conversions. Without these logs, it's difficult for us to analyze the issue thoroughly and pinpoint the root cause.
If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
Additionally, please provide an uncropped screenshot of your Google Ads UI, highlighting the conversion action name/ID and with your Google Ads customer ID visible. This would be very helpful for our further investigation.
You can send the details via Reply privately to the author option, or direct private reply to this email.
![]() |
Google Ads API Team |
[2025-09-19 05:36:20Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swd17:ref" (ADR-00320034)