Conversion Upload Errors

43 views
Skip to first unread message

Erica Fairchild

unread,
Sep 19, 2024, 12:04:41 PM9/19/24
to Google Ads API and AdWords API Forum
Hello,

We are receiving several errors consistently in our offline conversion uploads each day. One error that comes through often is "this click is too old". We run a lead gen account, so it's really hard for us to imagine a lead submission happened 90 days+ after the original click. Is there a way for us to validate this in some way?

These are the account IDs in question:
185-222-0229
931-913-1897
993-226-8305
659-297-4284
978-623-7860

Here are a few of the click IDs from 9/16 that registered this error:
Account 993-226-8305 - EAIaIQobChMI0biI9tCwhwMVhUxHAR3d7Qa6EAAYAiAAEgLWnPD_BwE
Account 659-297-4284 - Cj0KCQjw7ZO0BhDYARIsAFttkCga0Jn9cGtqKAb8wjASPc9R-uCXMbfGeksi9XnA0E6EKESEUDlfmoUaAu4dEALw_wcB
Account 659-297-4284 - Cj0KCQjwsPCyBhD4ARIsAPaaRf0I7VmAvxKy5ZM82YF_R0mEihLVGcFsauyvuqXmsLhj5z5wTuBAEPsaAuEQEALw_wcB

We also noticed that a lot of our click-through conversion windows were only set to 30 days, not the max of 90 days. If we were to extend this click-through conversion window back to 90 days, would that give us more time to let Google match these click IDs with clicks?

Another error we see is "this click's gclid can't be found". We've looked at these click IDs and can confirm they are valid leads on our backend. Can you help us figure out why the gclid can't be found by Google? Here is an example from 9/16:
Account 978-623-7860 - Cj0KCQjwrp-3BhDgARIsAEWJ6SxpT5xxS10fdNtNVggWB3KcMNrPg9mq8DeREfTpJB66gdQqnLeojyEaAjvREALw_wcB

Any help or guidance you can provide on this would be greatly appreciated!

Google Ads API Forum Advisor

unread,
Sep 19, 2024, 3:32:21 PM9/19/24
to erica.f...@homesolutions.com, adwor...@googlegroups.com
Hi,

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

I understand your issue and to assist you further, could you please provide us with the complete API logs (request and response with request-id and request header) generated at your end while uploading conversions via 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 Java.NetPHPPythonRuby 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.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02vGMIU:ref" (ADR-00268792)

Thanks,
 
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages