Hi, Thank you for reaching out to the Google Ads API support team.
Upon checking, I understand that you are getting an "INVALID_CONVERSION_ACTION_TYPE" error while uploading conversions using the Google Ads API. Kindly note that this error indicates that the specified conversion action has a type that is not valid for uploading click conversions. Make sure the ConversionAction specified in your upload request has the type UPLOAD_CLICKS. I would recommend you to kindly refer to this help center article "Conversion Tracking: Troubleshooting conversion tracking status" to troubleshoot your conversions based on your conversion action ID status. Could you kindly confirm if you followed the setup prerequisites for working with an offline conversion setup? If not, I would request you to follow the prerequisites before uploading offline click conversions. Also, I would suggest you refer to this "Debug common errors" documentation for more information. Further, I would suggest you refer to the Monitor offline data diagnostics documentation as it helps to find the overall health of the conversion upload processes. Regarding uploading a duplicate conversion (that is, a ClickConversion with a gclid, conversion_date_time, and conversion_action that was previously uploaded), a CLICK_CONVERSION_ALREADY_EXISTS error is returned regardless of whether you have uploaded it short period of time. Try using a different timestamp to see if the error still persists. To resolve this error, you may refer to this document for more information. Also note that duplicate conversions are allowed. However, only the first instance will be recorded and the succeeding duplicates will be ignored in the Google Ads conversions. If possible, please share uncropped UI screenshots related to the specified conversion actions for which you are encountering the issue, as they would be helpful for our investigation. Additionally, If the issue persists even after trying with the provided suggestions, please provide us with the complete 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, Google Ads API Team Feedback How was our support today? [2025-02-18 06:36:47Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2KC:ref" (ADR-00288637) -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/lA3Ke000000000000000000000000000000000000000000000SRV91B00AJ8HX0eiTIGJZPfzQE2lMw%40sfdc.net.
