Is the data in the Geo Performance API report different from the Google Ads Geo report?

[Cristiano Costa Santos (he)]

Hey guys,
I want to understand the reason for the difference in existing data from an API v13 extract of the geographic view report compared to the custom report by region generated in Google Ads.

The extract query was as follows, using the dimensions and metrics below:

"SELECT segments.geo_target_region, segments.geo_target_city, campaign.name, metrics.clicks, metrics.conversions, metrics.cost_micros, metrics.impressions FROM geographic_view"

In Google Ads custom reporting, the dimensions and metrics are: Campaign name, Region(User location), Cost, Impr., Clicks and Conversions.

API extraction data is always below what is seen in the personalized Google Ads report, which in turn is slightly below the data when viewed at the campaign level, also in Google Ads.

Why is there a difference in values in the data via API and in the custom report and the custom report at the region level with the report at the Google Ads campaign level?

Does the API's segments_geo_target_region dimension really match the Google Ads Region(User location) dimension?

Can you help me with these doubts?

Thanks,

Cristiano

[Cristiano Costa Santos (he)]

Complementing my questions, which API dimension corresponds to the Region(Matched) dimension of the Google Ads custom report?

Thanks,

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/I_xAM3rIhcE) from the forum as it wasn't routed to our support queue.

Regards,

Google Ads API Team

[Cristiano Costa Santos (he)]

Up.

[Google Ads API and AdWords API Forum]

Hi, 

Thanks for reaching out to the Google Ads API Forum. I hope you are doing well today.

With regards to your concern, “Geographic View” includes all metrics aggregated at the country level, one row per country. It reports metrics at either actual physical location of the user or an area of interest. If other segment fields are used, you may get more than one row per country. While, a “Location view” summarizes the performance of campaigns by Location criteria.

However, please note that the Google Ads API mirrors the Google Ads UI. That said, for us to further investigate the issue or your concern, could you please provide us with the uncropped screenshots from the Google Ads UI? This will help us to provide accurate information and recommendations.

You can provide these via the Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Reference links:

• Geographic_view report - https://developers.google.com/google-ads/api/fields/v13/geographic_view

• Location_view report - https://developers.google.com/google-ads/api/fields/v13/location_view

Have a great day.

Regards,

Google Ads API Team

On Friday, June 2, 2023 at 4:01:06 AM UTC+8 cris...@raccoon.ag wrote:

[Cristiano Costa Santos (he)]

Hey guys.

Attached is the Google Ads screenshots

Note that to compare the results with the API query (SELECT segments.geo_target_region, segments.geo_target_city, campaign.name, metrics.clicks, metrics.conversions, metrics.cost_micros, metrics.impressions FROM geographic_view") I used the dimension Region( User location) in the Google Ads custom report. And as I mentioned that way the extract values are lower than what you see in the UI.

Why is there a difference in values in the data via API and in the custom report and the custom report at the region level with the report at the Google Ads campaign level?

Does the API's segments_geo_target_region dimension really match the Google Ads Region(User location) dimension?

Complementing my questions, which API dimension corresponds to the Region(Matched) dimension of the Google Ads custom report?

Thanks,

Cristiano

[Google Ads API Forum Advisor]

Hi Cristiano,

Thank you for responding back.

I truly understand that the values are lower than what you see in the UI when comparing results using the query. However, for us to compare also these values you are referring to, we will need a full visibility of what you are seeing in the UI. With this, could you share a non-redacted UI screenshot for these values and the CID where you are seeing the discrepancy? This is so we could provide more appropriate recommendations on its corresponding API report and query based on the UI screenshot. 

You may send the full non-redacted screenshot via Reply privately to the author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Additionally, please also note that in comparing UI and API data, make sure to consider the following items below:

• Comparing the API and UI on the same level as much as possible
• The segments and fields of the API and UI should be the same
• The date range is also the same

With regards to your questions, the segment field in API which corresponds to the Region segment in UI is the segments.geo_target_region (https://developers.google.com/google-ads/api/fields/v14/segments#segments.geo_target_region). You may also check this guide (https://developers.google.com/google-ads/api/docs/reporting/uireports) which maps the concepts and naming conventions for reports in the Google Ads UI to the reports that you can generate using Google Ads Query Language (GAQL) and the Google Ads API.

This message is in relation to case "ref:_00D1U1174p._5004Q2mByuK:ref"

Thanks,
 

Google Ads API Team