Enhaced Conversion for Leads.

45 views
Skip to first unread message

Rafael Machado

unread,
Mar 13, 2025, 9:15:40 AM3/13/25
to Google Ads API and AdWords API Forum
When I upload a click conversion to Google Ads with the payload containing a Click ID (GCLID) and user identifiers, the following error appears in the Google Ads UI:

Em 2025-03-13 às 09-46-36.png

I created two other conversions to test. In one conversion I added the Click ID and user identifiers to the payload and in another conversion, I added only the user identifiers to the payload. I uploaded both conversions using the API. In the conversion with only the user identifiers in the payload, no error appeared in the Google Ads UI.

So, what is the problem here? Can't I send a conversion with the GCLID and user identifier in the payload? I didn't find anything in the REST Interface documentation mentioning anything about this. What am I doing wrong?

The conversion action that sends user provided data to Google Ads when the user fills out a form on my landing page is configured correctly. Being able to send a Converted Lead conversion with only user identifiers in the payload without any error with debug enabled being set to true and also no error appearing in the Google Ads UI is proof that this is configured correctly.

Google Ads API Forum Advisor

unread,
Mar 13, 2025, 2:27:52 PM3/13/25
to eumacha...@gmail.com, adwor...@googlegroups.com

Hi,

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

I understand that the specified conversion action is showing status “Needs attention” indicates that your enhanced conversion setup is active, but there are errors that require your attention. For example, your enhanced conversion setup may have missing information.

Also, I have noticed that you are having the alert “No user-provided data matches” which indicates that your Google tag is correctly implemented on your website form, but there have been no matches with the user-provided data you imported. Please check that the user data you’ve imported is:

  • Standardized (e.g., names, emails).
  • Properly hashed (if applicable).
  • Consistent with the data captured by your website forms.

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 Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-03-13 18:26:53Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH9P4:ref" (ADR-00294022)



Reply all
Reply to author
Forward
0 new messages