Region View

[Raquel Munari]

Hello,

I'm making a query from "geographic_view". Whenever I add the segment field "geo_target_state" the number of clicks, impressions and cost gets smaller (and, therefore, wrong), to the point where it gets 5% different accounting all of our customer's ids for a period of a month.
I want to know, first of all, why this happens, if there's a way I can fix it and last of all, I realize the resource field "region_criterion_id" (wich would be the correspondent to the attribute field "RegionCriteriaId" in the Google Adwords API) is not available. Why is that and is there another resource field I could use in replace (that will fit me better then geo_target_state)?

Thanks for the attention. Regards,

Raquel

[Google Ads API Forum Advisor]

Hi Raquel,

Thank you for raising this concern to Google Ads API forum.

To simply explain why the metrics get smaller when adding a segment field, I can refer to this document, ("When adding some segments, the metrics in the summary row may decrease" section). To further explain the provided document, when geo_target_state is added to a query with FROM geographic_view, that segment is telling the query to only get the rows of data that have target state, and remove any row that is not associated with a target state. In this case, the metrics would be lower because it would exclude any non-target state metrics.

As for this concern, "and last of all, I realize the resource field "region_criterion_id" (wich would be the correspondent to the attribute field"RegionCriteriaId" in the Google Adwords API) is not available. Why is that and is there another resource field I could use in replace (that will fit me better then geo_target_state)?" could you please provide more context, so that we can address it accordingly? 

Best regards,

Jinky Google Ads API Team

ref:_00D1U1174p._5004Q2a32G2:ref

[Raquel Munari]

Hi, thank you for answering me.

I well understood that any row that is not associated with a target state was removed, thank you for clarifying that. For feedback, in the future, maybe correct that by just returning the field "geo_target_state" as null, since it doesn't make sense to take a incomplete report just because it's wanted to know the target state. It just doesn't make any sense in what is concerned to data report.

For the second subject, what I meant was:

On the AdWords API, in the "Geo Perfomance Report" (equivalent, accourding to google itself documentation, to the resource "geographic_view"), there was a field for the ID of the country and a field for the ID of the region (CountryCriteriaId and RegionCriteriaId). In the "geographic_view" only the field for the ID of the country is now available (country_criterion_id). Will it be fixed in the future? Because it's a really important vision for our company (and, I believe, many others).

[Google Ads API Forum Advisor]

Hi Raquel,

Thank you for your reply and for your feedback on the segments fields.

However, the behavior discussed in the document that our colleague Jinky has provided is now the current implementation. For any changes that may be applied to the reporting feature of the Google Ads API, you may follow our blog for updates and announcements.

As for your other concern "there was a field for the ID of the country and a field for the ID of the region (CountryCriteriaId and RegionCriteriaId)", and as per this guide, you can use the geographic_view.country_criterion_id and segments.geo_target_region respectively to acquire their values.

You can also refer to the rest of our report mapping guide as well as the query migration tool, for more information on migrating your reports to the Google Ads API. 

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2a32G2:ref