Asset_group_asset vs Asset_group Metrics Discrepancy in API

[Dani Buchsbaum]

I'm pulling asset_group_asset metrics from the API and seeing something strange.

For a given date range, the asset-level data shows:

• Impressions: 12,469,025

• Cost: 929K (after dividing cost_micros)

For the same asset groups and dates, the asset group–level data (which matches the Google Ads UI) shows:

• Impressions: 14,460,243

• Cost: 333K

I understand that asset-level metrics aren't perfectly attributed and are often inflated, which explains why cost and other metrics are 2–3x higher at the asset level.

But it feels inconsistent (and potentially incorrect) that impressions are actually lower at the asset level.

Why would impressions be lower when all other metrics are inflated? Is this expected behavior, or a possible issue with the API?

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

As you have observed discrepancies between the metric values displayed in the Google Ads UI and the data retrieved through the Google Ads API. We would like to specify first the following when comparing the value of the Google Ads UI and the Google Ads API.

• The segments and fields of the API and UI should be the same.
• The date range should also be the same. 
• Comparing the API and UI at the same level as possible. 

With this, to analyse the issue further, please share the below details :

• CID of the Google Ads account 
• Date range for which you are seeing discrepancy 
• Uncropped screenshot of the Google Ads UI by highlighting the metrics you are referring  
• 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-10-22 11:14:00Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vRTKT:ref" (ADR-00336187)