Hi Toni,
Thank you for reaching out to the Google Ads API support team.
Upon checking your Google Ads account '897-148-6809', I could see that the given conversion actions '224574134' and ‘224811030’ status is showing as 'Needs attention' and the diagnostic tab is showing "Mismatched enhanced conversion configuration". If you implement enhanced conversions for the web using the Google Ads API, then make sure all of the prerequisites are satisfied before proceeding to implementation. I would recommend you to refer to this 'Implement Enhanced Conversions for Web' as it describes in detail on how to implement the enhanced conversions for the web using the Google Ads API. If you encounter any issues while implementing, then I would suggest you refer to the 'Troubleshoot Enhanced Conversions for Web' documentation as it helps to troubleshoot your issues related to the conversion uploads.
After running the diagnostic level query, you are getting the CONVERSION_ACTION_NOT_ELIGIBLE_FOR_ENHANCEMENT error. Also, we have observed that you did not normalize and hash the lead data, such as email address, phone number, and mailing address for the provided enhanced conversion action request, you can capture their first-party data, hash it, send it through the Google Ads API. I would recommend you to check this help center article About enhanced conversions for more information.
Kindly provide us 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 guide Python 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-03-24 12:42:39Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vHCA2:ref" (ADR-00296173)

Hi,
Please be informed that I have removed your response from the forums as it contained the PII information.
I understand that you are uploading data in hashed format. I noticed that you have selected the tag for both the conversion actions as ‘Google Tag Manager’. But, you have not configured those tags. Please note that as per the prerequisites of the enhanced conversions for web, configuring the tag is a mandatory step. Therefore, I would recommend you to configure the tags, ensure that you have followed the prerequisites and retry uploading the conversions.
If you are still facing any issues, kindly get back to us with the complete API logs (request and response with request-id and request header) generated at your end 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-03-24 18:34:50Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vHCA2:ref" (ADR-00296173)