Hi, Any update on this? I have tried to respond to this chain now twice, but my responses are not visible here, I am not sure if you have received them?
I have requested for you to provide an example of Enhanced Conversion (Conversion Adjustment) to Google Ads API where the Conversion Adjustment/Enhanced Conversion does not include GCLID but does include conversion timestamp, since this scenario is not covered in documentations. Br, Anni On Tuesday 18 June 2024 at 12:08:02 UTC+3 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > Upon checking the screenshot you provided, I could see that you are > getting the error message "your enhanced conversions API code is sending > data too late". This alert shows if you’re sending Ads API data more than > 24 hours after the conversion time. Edit your enhanced conversions Ads API > code to send data within 24 hours after the conversion event happens. > > This alert may also show if conversion occurrence time isn’t included in > your Ads API pings. Check the Google Ads API instructions > <https://developers.google.com/google-ads/api/docs/conversions/enhance-conversions> > to > learn how to include conversion time in your Ads API request. > I would suggest you to 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. To retrieve the latest offline data diagnostics > <https://support.google.com/google-ads/answer/13812240> for your account, > you can use the following query: > > > SELECT customer.id, offline_conversion_upload_client_summary.alerts, > offline_conversion_upload_client_summary.client, > offline_conversion_upload_client_summary.daily_summaries, > offline_conversion_upload_client_summary.job_summaries, > offline_conversion_upload_client_summary.last_upload_date_time, > offline_conversion_upload_client_summary.resource_name, > offline_conversion_upload_client_summary.status, > offline_conversion_upload_client_summary.success_rate, > offline_conversion_upload_client_summary.successful_event_count, > offline_conversion_upload_client_summary.total_event_count > FROM offline_conversion_upload_client_summary > > Additionally, you can utilize the Google Ads Query Builder > <https://developers.google.com/google-ads/api/fields/v16/overview_query_builder> > and Query Validator > <https://developers.google.com/google-ads/api/fields/v16/query_validator> to > build and validate the queries for retrieving the data from the Google Ads > API. > > If the issue persists even after trying with the provided suggestion, > kindly provide us with 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 to better assist you 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 > <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. > > > > > *This message is in relation to case "ref:!00D1U01174p.!5004Q02tJNSU:ref" > (ADR-00241967) Thanks,* > > [image: Google Logo] *Google Ads API Team* > *Register > <https://adsonair.withgoogle.com/events/performance-max-api-workshop> for > the upcoming workshop: Performance Max and the Google Ads API!* > > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/98cb3029-2173-4007-a834-bac97ad0205fn%40googlegroups.com.
