[Inquiry] Regarding Discrepancy in Total Cost Data Between Google Ads API and Dashboard
Center HABIG
I would like to inquire about a discrepancy between the campaign total cost data returned by the Google Ads API and the data shown in the Google Ads dashboard.
Our system ingests campaign cost data through the API during the early morning hours. Normally, the values retrieved from the API at that time are very close to the values available for download from the dashboard later in the morning.
However, on August 19, when retrieving the previous day’s (August 18) data via the API, we observed a discrepancy of about 5 million KRW compared to the dashboard. When we queried the API again in the afternoon, the values aligned more closely with the dashboard data.
This is the first time we have encountered such a large difference between the API response and the dashboard, and we would like to understand the possible cause of this behavior.
Thank you for your assistance.
Google Ads API Forum Advisor
Hi,
Thank you for reaching out to the Google Ads API support team.
I understand that you are observing a discrepancy between campaign total cost data returned by the Google Ads API and the data shown in the Google Ads dashboard.
To assist you further, could you please provide us with below details?
- Customer ID (CID) of the Google Ads account
- Date range which you are facing discrepancy.
- Uncropped UI screenshot for the issue.
- Complete API logs (request and response with request-id and request header) generated at your end.
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-08-20 05:52:15Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u4ilq:ref" (ADR-00330448)
