We're experiencing data inconsistency between the Google Ads UI / API and our BigQuery integration. Specifically, when querying metrics like impressions and clicks for a Performance Max (PMAX) campaign from the CampaignStats table in BigQuery, the values appear higher than those shown in the Google Ads Dashboard or returned by the API.
We’ve already enabled the PMAX-specific tables in the BQ integration.
Please advise:
Which data source (BQ or API/UI) is considered accurate for PMAX metrics?
Should we use a different table to retrieve PMAX data correctly?
Is there any known delay or duplication issue that might explain this discrepancy?
Let us know how we can ensure consistent and correct reporting of PMAX metrics across platforms.
Thank you.
Hi,
Thank you for reaching out to the Google Ads API support team.
By reviewing your query, I understand that you are experiencing the data discrepancy between the Google Ads UI, Google Ads API and BigQuery integration for the Performance Max campaign. Please note that concerns related to the BigQuery are out of scope for Google Ads API support team. Kindly note that we can only provide support for Google Ads API related concerns. If you are facing a discrepancy with BigQuery, I would recommend you to reach out to the GCP Product support team for further assistance.
To assist you further, regarding discrepancy between the Google Ads API and Google Ads UI, please provide us with the Google Ads customer ID, Performance Max campaign ID along with the uncropped UI screenshot of the data that you are trying to compare with the corresponding dates. Additionally, please provide us with the GAQL query that you have used to retrieve the data through the Google Ads API? Also, provide the 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.
![]() |
Google Ads API Team |
[2025-07-08 16:50:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhRUQ:ref" (ADR-00317944)