Less than 6 hours ago error

[Jon]

Hello,

After a recent change that allows us to send import click conversions without click ids, we've been seeing this error. I'm trying to understand why this is happening? Should conversions regardless of whether they have a click id, or an email/phone not be acceptable immediately?

{"partialFailureError":

{"code":3, "message": "The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago. Retry after 6 hours have passed., at

conversions[0].gclid","details":

[{"@type":"type.googleapis.com/go

ogle.ads.googleads.v15.errors.Googl

eAdsFailure", "errors":[{"errorCode":

{"conversionUploadError":"TOO_RE

CENT_EVENT"', "message":"The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago.

Retry after 6 hours have passed.", "trigger":

{"stringValue":"CMaw4bCW4YQDFf

fihAAdJekByQ"}, "location":

{"fieldPathElements":

[{"fieldName": "conversions", "index"

:O},

{"fieldName":"gclid" }]}}],"requestld"

:"kyBp-

haiMPsLfHhCtpOL8g"}l},"results":

K71,"jobld":"4292188515568245968

Learn more and Register today

This message and any attachments contain information, which may be confidential and/or privileged, and is intended for use only by the intended recipient, any review; copying, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please (i) notify the sender immediately and (ii) destroy all copies of this message.

[Google Ads API Forum Advisor]

Hi,

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

From the provided information, I understand that you're getting a TOO_RECENT_EVENT error. This error indicates the click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago. Could you please confirm if you are able to upload successfully after 6 hrs. Also, I could see that you have provided only the response body. Please provide us with the complete API logs (request and response with request-id and request header) to investigate this issue 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.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02rzo0A:ref"

Thanks,
 

Google Ads API Team