Hi Lakshmanan,
Thank you for reaching out to us.
Please note that the Google Ads API mirrors the Google Ads UI. Whatever data shows on the Ads UI report, the API should pull the same. If you are seeing any discrepancies in the data seen on Ads UI vs. Google Ads API, then you may provide us the Ads UI screenshot showing the discrepancies and the complete API logs (request and response with request-id) generated on your end, so that we can further check this on our end and provide appropriate recommendations to you.
Note that logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here and click your client library for the specific guideline to enable it.
For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.
You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
Best regards,
![]() |
Google Ads API Team |
Hi Tung,
Thank you for reaching out to us.
For our team to further check this and provide you with an appropriate recommendation, could you kindly provide us with the following information below:
Note that logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here and click your client library for the specific guideline to enable it.
For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.
You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.