Asset metrics queried via the API are different from those in the UI

[Tuo Ma]

Hi, I am using the following GAQL query the account level asset metrics:

SELECT asset.sitelink_asset.link_text, metrics.impressions, metrics.clicks, metrics.interactions, metrics.interaction_rate, metrics.average_cpc, metrics.average_cpm, metrics.average_cost, metrics.cost_micros, metrics.all_conversions, metrics.all_conversions_value, metrics.conversions, metrics.conversions_value FROM customer_asset WHERE segments.date BETWEEN '2024-11-24' AND '2024-12-20' AND asset.type = 'SITELINK' AND metrics.impressions > 0";

One of the results I got is :

results {
  metrics {
    clicks: 1215
    conversions_value: 2000.0
    conversions: 2.0
    cost_micros: 6646541866
    all_conversions_value: 3771.98831
    all_conversions: 68.498831
    average_cost: 1367038.6396544632
    average_cpc: 5470404.82798354
    average_cpm: 4.9794290275696737E8
    impressions: 13348
    interaction_rate: 0.36424932574168417
    interactions: 4862
  }
  asset {
    resource_name: "customers/8978024178/assets/44226261064"
    sitelink_asset {
      link_text: "Mattress Spring Pocket"
    }
  }
  customer_asset {
    resource_name: "customers/8978024178/customerAssets/44226261064~SITELINK"
  }
}

Then I check it in the Google Ads UI:

The results are different, the impressions, clicks from the API results are always lower than those in the UI.
Could you please tell me how to fetch the same reults shown in the UI?

Best Regards

Tuo

[Google Ads API Forum Advisor]

Hi,

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

I have raised your concern with the rest of our team and one of my teammates will reach out to you once we have an update.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqDE:ref" (ADR-00279602)

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[Google Ads API Forum Advisor]

Hello Tuo,

I appreciate how you have such an attention to detail. I decided to take your query and narrow it down to 1 day to reproduce it. So, I picked November 25, 2024. It's easier to compare when the date range is smaller.

This is what I got for the API when I ran your same request for only November 25, 2024.

[{
  "results": [
    {
      "metrics": {
        "clicks": "46",
        "conversionsValue": 0,
        "conversions": 0,
        "costMicros": "391927946",
        "allConversionsValue": 11.98831,
        "allConversions": 2.998831,
        "averageCost": 3266066.2166666668,
        "averageCpc": 8520172.7391304355,
        "averageCpm": 917864042.15456676,
        "impressions": "427",
        "interactionRate": 0.28103044496487117,
        "interactions": "120"
      },
      "asset": {
        "resourceName": "customers/8978024178/assets/44226261064",
        "sitelinkAsset": {
          "linkText": "Mattress Spring Pocket"
        }
      },
      "customerAsset": {
        "resourceName": "customers/8978024178/customerAssets/44226261064~SITELINK"
      }
    }
  ],

Then, I went to your Google Ads UI view, and I picked only November 25, 2024. I can confirm that the numbers don't line up, which is very weird.




Then, I went to the Predefined Reports in the Google Ads UI, and chose the Upgraded Assets report with November 25, 2024. I narrowed it down to clicks, impressions, and interactions so I could compare those three fields to the other interfaces. It's the same data as the API. So, the Google Ads UI doesn't now seem to be agreeing with itself. The Google Ads UI in predefined reports and the API both have the same numbers, but the Assets table does not. 



So, there's good news here. Due to the Google Ads UI having the same numbers in the predefined report as the Google Ads API, I believe that the Google Ads API numbers are correct. I'm not sure why the Assets table is different from the other two sources. I'm going to send a question to people who created the Assets table in the Google Ads UI to see if they have an explanation. Perhaps, they are including some additional data. I'm not sure when they will get back to me as it is the holidays now and many people are taking some well-deserved rest. I'll keep an eye open for their response.

All the best,
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqDE:ref" (ADR-00279602)

 

Nadine Wang Google Ads API Team

Feedback
How was our support today?
               
 

 

[Google Ads API Forum Advisor]

Hello Tuo,

I got an answer back on this about that one UI table having a different view from the API and the other report in the UI, and I wanted to follow up to keep you in the loop. You did indeed find an unexpected discrepancy. What the API is returning is fine. My colleagues are currently working on updating the code base and rolling it out in our systems. I'm told we should see all the data align across all the interfaces in a couple of weeks. Thank you for pointing this out.

Best,

[Google Ads API Forum Advisor]

Hello Tuo,

You may have already noticed, but there were updates made to our system to get the views to align. I'm just mentioning it here in case you didn't already see it.

All the best,