Hi, Thank you for reaching out to the Google Ads API support team.
Based on the provided information, I understand that you are getting a discrepancy in conversion. Could you kindly confirm if you followed the setup prerequisites for working with an offline conversion setup? If not, I would request you to follow the prerequisites before uploading offline click conversions. I would suggest you refer to the Monitor offline data diagnostics documentation, as it helps to find the overall health of the conversion upload processes. The EXPIRED_EVENT error, which means that when uploading conversions, the click associated with the given identifier or ios url parameter is either too old to be imported or occurred outside of the click-through lookback window for the specified conversion action. For this error, you may double-check if the given identifier is not too old or occurred before the lookback window for the specified combination of conversion date and conversion action. You may use the click_view report resource to verify your GCLID. In addition, you can first verify the click_through_lookback_window_days specified in your conversion_action. From the value retrieved, then perform a request using the click_view report for each day (with date filter for one day) until the last valid date, in reference to the lookback window days. You can set the conversion window anywhere from 1 to 90 days, depending on the source of conversions. You can refer to this help center article About conversion windows for complete information. In order to assist you further, kindly share the complete API logs (request and response logs with request-id and request header) generated at your end while uploading the conversions via the Google Ads 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, .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 Ads API Team Feedback How was our support today? [2025-09-15 16:28:50Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u6d8g:ref" (ADR-00332795) -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/adwords-api/bMlc4000000000000000000000000000000000000000000000T2N1S2005M3m08HeSeenFGhWoxq-pw%40sfdc.net.
