im getting this same issue. my clickids are not being malformed or modifie,d they are the exact clickid sent to me from google when the click originated. it seems the wbraid gbraid ones do not get accepted as API/Offline conversions, why? What am I doing wrong here?
On Thursday, July 24, 2025 at 9:07:01 AM UTC-4 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > The UNPARSEABLE_GCLID > <https://developers.google.com/google-ads/api/reference/rpc/v16/ConversionUploadErrorEnum.ConversionUploadError#unparseable_gclid> > error > means that the imported gclid could not be decoded. Make sure you have not > modified the click IDs. The possible reason for this is that you are > uploading GCLID that does not exist. Your GCLID shouldn’t be > altered/modified when importing via Google Ads API > <https://developers.google.com/google-ads/api/docs/start>. > > Note that Enhanced Conversions for Leads > <https://developers.google.com/google-ads/api/docs/conversions/upload-offline#what_is_enhanced_conversions_for_leads> > can't > be used with either WBRAID or GBRAID identifiers. If you do you will > encounter the VALUE_MUST_BE_UNSET > <https://developers.google.com/google-ads/api/reference/rpc/v20/FieldErrorEnum.FieldError#value_must_be_unset> > error. > You can determine which of the following issues led to the error. > > - > > 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. > - The ClickConversion has a value set for either gbraid or wbraid and > has a value for custom_variables. Google Ads does not support custom > variables for a conversion with a gbraid or wbraid click ID. Unset the > custom_variables field of the conversion. > > From the provided API logs, it seems that you're currently using version > v18 > <https://developers.google.com/google-ads/api/reference/rpc/v18/overview> > of the Google Ads API. Note that 'v18' was deprecated in June 2025, and > will sunset > <https://developers.google.com/google-ads/api/docs/sunset-dates#timetable> > 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 > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > with request-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>) > > generated at your end. > > 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 > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging> > , .Net > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging> > , PHP > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging> > , Python > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging> > , Ruby > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or Perl > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > 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, > > [image: Google Logo] Google Ads API Team > Feedback > How was our support today? > > [image: rating1] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=500Ht00001swd17IAA> > > [image: rating2] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=500Ht00001swd17IAA> > > [image: rating3] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=500Ht00001swd17IAA> > > [image: rating4] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=4&entry.295079254=500Ht00001swd17IAA> > > [image: rating5] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=5&entry.295079254=500Ht00001swd17IAA> > [2025-07-24 13:06:18Z GMT] This message is in relation to case > "ref:!00D1U01174p.!500Ht01swd17:ref" (ADR-00320034) > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/adwords-api/e8814d88-ba79-418e-a981-96dbfb3d15c1n%40googlegroups.com.
