RE: api fail in "website" conversion google ads

[Google Ads API Forum Advisor]

 Hi,

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

Note that I have removed your response from the forums as it contains the PII information.

The INVALID_CONVERSION_ACTION_TYPE error indicates that the specified conversion action has a type that is not valid for uploading click conversions. Make sure the conversion_action specified in your upload request has the type upload_clicks.

• Enhanced conversions for web are relevant for advertisers who want to track sales and events that happen on a website.
• Enhanced conversions for leads are relevant for advertisers who want to track sales that happen off a website (for example, phone or email) from website leads. They improve measurement of offline transactions that came from a website lead or visitor.

From the logs provided, it appears that you are using the UploadClickConversions method of the ConversionUploadService. But for the Enhanced conversion for web implementation, you should use the UploadConversionAdjustments method of the ConversionAdjustmentUploadService. 

You have followed the Enhanced conversions for leads implementation, but the conversion action (TTT | FORM CONTACTO) '6474193587' is a WEBPAGE conversion type. In order to avoid this error while making the request using the conversion action:(TTT | FORM CONTACTO)'6474193587', please follow the Prerequisites and API Implementation for Enhanced conversions for Web.

 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-10-31 23:21:33Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSOTq:ref" (ADR-00338153)

[Google Ads API Forum Advisor]

Hi,

Based on the provided information, I understand that you are encountering a CONVERSION_ACTION_NOT_ELIGIBLE_FOR_ENHANCEMENT error which indicates that enhanced conversions cannot be used for the specified conversion action. I would recommend you to check this help center article About enhanced conversions for more information.

Upon checking the logs you provided, I could see that these adjustments are uploaded with the type ENHANCEMENT, which tells our systems that you are adding user identifiers to existing conversions. The value restatements are being ignored. If you want to adjust the value of these conversions, you will need to set them with the type RESTATEMENT instead. Can you try re-uploading these with that change and let me know if you get the expected behavior?

If not, please share the updated complete API logs (request and response with request-id and request header) generated at your end while uploading the conversions via the API.

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 for 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.

Also, I could see that you are still using the 'v19' of the Google Ads API, which is already deprecated. I would recommend migrating to the latest version v22, please follow this guide to upgrade to the latest version. 

 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-11-11 16:28:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSOTq:ref" (ADR-00338153)

[Google Ads API Forum Advisor]

Hi,

Please ignore my previous response.

Based on the provided information, I understand that you are encountering a CONVERSION_ACTION_NOT_ELIGIBLE_FOR_ENHANCEMENT error which indicates that enhanced conversions cannot be used for the specified conversion action. I would recommend you to check this help center article About enhanced conversions for more information.

Upon checking the logs you provided, I could see that these adjustments are uploaded with the type ENHANCEMENT, which tells our systems that you are adding user identifiers to existing conversions. The value restatements are being ignored. If you want to adjust the value of these conversions, you will need to set them with the type RESTATEMENT instead. Can you try re-uploading these with that change and let me know if you get the expected behavior?

If not, please share the updated complete API logs (request and response with request-id and request header) generated at your end while uploading the conversions via the API.

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 for 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.

Also, I could see that you are still using the 'v19' of the Google Ads API, which is already deprecated. I would recommend migrating to the latest version v22, please follow this guide to upgrade to the latest version. 

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-11-11 16:30:14Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSOTq:ref" (ADR-00338153)

[Google Ads API Forum Advisor]

Hi,

 

Please be informed that I have removed your response from the forums as it contains the PII information.

 

Kindly note that we observe your Enhanced Conversions settings are currently configured for Google Tag Manager. To ensure your uploads function correctly, please navigate to Goals > Settings > Enhanced Conversions and select "Google Ads API" as the method for managing user-provided data, rather than Google Tag Manager. Could you confirm if it is Working from your end ?

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-11-13 17:44:05Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSOTq:ref" (ADR-00338153)