How to find out all valid gclids in a date

[Vinay Surya]

I am having some trouble getting EVENT_NOT_FOUND and EXPIRED_EVENT errors. I want to invalidate them before I push using the conversion api. 

The trouble is that when I use this query: 
SELECT click_view.gclid, segments.date FROM click_view WHERE segments.date = '2024-06-19'

I am not exactly getting the conversions/clicks that happened on 2024-06-19.

Sometimes for a click that happened on a later date, I am getting the gclids ids if I use an earlier date which seems contradictory.

Any help here would be appreciated. Thanks in advance.

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

As per the information provided, I understand that you are encountering EVENT_NOT_FOUND and EXPIRED_EVENT errors for the conversions uploaded via the API. The EVENT_NOT_FOUND error occurs due to the fact that the fact that the click associated with the given identifier or iOS URL parameter could not be found in the system. This can happen if the identifier or iOS URL parameter is collected for non Google Ads clicks. I would suggest that, when storing the GCLID, you'll need to double-check to see where the GCLID came from. Having said that, would you be able to confirm if the identifier used in the request was actually generated from a Google Ads click?

The EXPIRED_EVENT error means that if the conversion action was created recently, then the click-through window for that conversion action will also be recent. This means that any imported events that occurred more than 21 days ago will not be recorded for that conversion action. Make sure you import the most recent data.

In order to assist you further, please provide the complete API logs (request, response,  request-id and request header) generated at your end while uploading conversions.

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.!5004Q02tJOt1:ref" (ADR-00242568)

Thanks,
 

Google Ads API Team

Register for the upcoming workshop: Performance Max and the Google Ads API!