GBRAID & WBRAID click identifiers does not work on One Conversion setting?

[Angelo Garcia]

Hi Google Support,

Our organisation is sending Conversion Events to Google Ads via API. 

The GCLID click ids are working properly but when the ad link is using GBRAID and WBRAID parameters, they are causing errors with this error below:

The imported gclid could not be decoded. Make sure you have not modified the click IDs., at conversions[0].gclid

We have checked the click ID formatting and they are not modified in any way. 

Our Conversion Count setting is set to One Conversion based on what we need. 

Why are GBRAID and WBRAID only work properly when the Conversion setting is Every? and causes errors when it is set to One Conversion?

Thank you.

[Angelo]

Is there an update on this one or anyone got an update? We are still having this issue. Thank you

[Google Ads API and AdWords API Forum]

Hi,

Thank you for reaching out to the Google Ads API support team.

As per provided information, I understand that you are getting the "The imported gclid could not be decoded. Make sure you have not modified the click IDs." (UNPARSEABLE_GCLID) error while uploading the conversion events. 

The possible reason for this is that you are uploading GCLID that does not exist. With this, to help you determine the GCLIDs that you can upload as conversions, then I can recommend generating reports using the click_view report. I would suggest using different counting type. Additionally, you can use this conversion_action report to retrieve and check conversion action instances. For your reference, you may also refer to this help center article about conversion counting options.

If in the event that you are using GCLIDs that are generated from the said report but the error persists, kindly provide us with the complete updated API logs (request and response logs with request-id and request header) generated at your end to better assist you further. 

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.

Thanks,

The Google Ads API Team.