Thank you for your answer that unfortunately didn't help. Let me rephrase my question for you:
Since early September 2025 we are seeing a discrepancy in Google Ads reporting: under the same conversion action, the account shows *significantly more conversions and higher conversion value* than we actually uploaded via *Upload Offline Conversions* using this workflow: https://developers.google.com/google-ads/api/samples/upload-offline-conversion All uploaded conversions include a unique order_id. Until August 2025, the reported numbers never exceeded our uploads (they were equal or sometimes slightly lower due to “expired_event” rejections). Could you clarify why reporting now shows more conversions than were uploaded? Has modelling or another change recently been introduced for Offline Conversion Uploads? Google Ads API Forum Advisor schrieb am Montag, 15. September 2025 um 18:29:37 UTC+2: > 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 > <https://developers.google.com/google-ads/api/docs/conversions/upload-clicks#setup> > 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 > <https://developers.google.com/google-ads/api/docs/conversions/upload-summaries> > documentation, > as it helps to find the overall health of the conversion upload processes. > The EXPIRED_EVENT > <https://developers.google.com/google-ads/api/reference/rpc/v16/ConversionUploadErrorEnum.ConversionUploadError#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 > <https://developers.google.com/google-ads/api/fields/v13/click_view> report > resource to verify your GCLID. In addition, you can first verify the > click_through_lookback_window_days > <https://developers.google.com/google-ads/api/fields/v13/conversion_action#conversion_action.view_through_lookback_window_days> > specified > in your conversion_action > <https://developers.google.com/google-ads/api/fields/v13/conversion_action?hl=en>. > > 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 > <https://support.google.com/google-ads/answer/3123169?hl=en#zippy=%2Cabout-view-through-conversion-windows> > for > complete information. > > In order to assist you further, kindly share the complete API logs ( > request > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > logs > with request-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>) > > 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 > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging> > , .Net > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging> > , PHP > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging> > , Python > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging> > , Ruby > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or Perl > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > 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, > > [image: Google Logo] Google Ads API Team > Feedback > How was our support today? > > [image: rating1] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=500Ht00001u6d8gIAA> > > [image: rating2] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=500Ht00001u6d8gIAA> > > [image: rating3] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=500Ht00001u6d8gIAA> > > [image: rating4] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=4&entry.295079254=500Ht00001u6d8gIAA> > > [image: rating5] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=5&entry.295079254=500Ht00001u6d8gIAA> > [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/41aa5a96-c779-406b-a7b5-88c34fa8acfen%40googlegroups.com.
