Discrepancy in Impressions Sum When Using geo_target_postal_code Segment in user_location_view

[Pawan Rai]

Hi everyone,

   I've encountered a discrepancy in impression counts when using the `geo_target_postal_code` segment in the Google Ads API (user_location_view). Here are the details:

   1. When querying for impressions with the segment:
 
      Select
        metrics.impressions,
        segments.geo_target_postal_code
      FROM
        user_location_view

      The impressions sum is reported as 3036.

   2. However, when I run a query without the segment:

      Select
        metrics.impressions
      FROM
        user_location_view

      The impressions sum is reported as 6734.

I have already checked for null or empty values in the geo_target_postal_code segment, and there are none.

Can anyone help me understand why there is a drop in impressions when using the `geo_target_postal_code` segment? Are there specific considerations or behaviors related to this segment that could explain the difference?

   Any insights or guidance would be greatly appreciated. Thanks!

[Google Ads API Forum Advisor]

Hi,

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

After reviewing your concern, I understand that you are encountering a discrepancy in impression counts when using the "geo_target_postal_code" segment in the Google Ads API.

Kindly note that, when adding some segments, the metrics in the summary row may decrease. For example: when segments.keyword.info.match_type is added to a query with FROM ad_group_ad, that segment is telling the query to only get the rows of data that have keywords, and remove any row that is not associated with a keyword. In this case, the metrics would be lower because it would exclude any non-keyword metrics.

So, in order to investigate further, kindly provide us with the complete API logs (request and response with request-id and request header) generated at your end along with the uncropped UI screenshot of the report that you are trying to fetch via the Google Ads API.

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.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02r4Kqe:ref"

Thanks,
 

Google Ads API Team