Hi, Thank you for reaching out to the Google Ads API support team.
Please find answers to your queries: Is there a way to proactively detect pending or recent API deprecations that affect reporting endpoints? I suggest you follow our Blog Post and Release Notes to get information on the latest version releases and changes that happen in the Google Ads API. You can also follow our Deprecation and sunset guide. Are there any webhook notifications, changelog subscriptions, or version deprecation calendars that can be integrated into our monitoring systems? I would like to inform you that you will receive notification about the version deprecation when your developer token was used to make requests to the Google Ads API. Also, another way is to follow our Blog Post and Release Notes to get information on the latest version releases and changes that happen in the Google Ads API. Are "zeroed" reports a known symptom of deprecation for specific services? Regarding the Zeroed reports, when you execute a query, you may encounter metrics for entities that are zero. This could be because: The entities are ineligible for display. They could have been paused within the report's date range. I would recommend you refer to the Zero metrics for more information. If you still need further assistance on this, please provide Customer ID of your Google Ads account. Additionally, provide us with the complete API logs (request and response logs with request-id and request header) generated at your end, so that we can investigate this issue further on our end and assist you accordingly. If you are using a client library and haven't enabled logging yet, I would request that you 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-07-02 04:35:34Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rgxe7:ref" (ADR-00316701) -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/BC0ys000000000000000000000000000000000000000000000SYR8RA00PdyEC6APTEiUFT1i_OEogw%40sfdc.net.
