Location view discrepancy with UI

[Johan Alpne]

Hello,

One of our customers is experiencing a discrepancy between the Locations view in the Google Ads UI and the location_view resource from the API.

In the UI we get 259734 impressions and from the API we get 349715 so the difference is quite large.

Are there any known issues with comparing these?

Appreciate any help, thank you!

Best regards,

Johan Alpne

Developer @ Funnel

[Google Ads API and AdWords API Forum]

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

Regards,
Google Ads API Team

[Google Ads API Forum Advisor]

Hi Johan,

Thank you for reaching out to us,

For our team to further check and provide appropriate recommendations for the discrepancies you are referring to, could you please provide us with the following information below:

• Entire UI screenshot without cropping, including its customer ID, where you can see the discrepancies
• Complete API logs (request, response and request-id) generated on your end
  • request : https://developers.google.com/google-ads/api/docs/concepts/field-service#request
  • response: https://developers.google.com/google-ads/api/docs/concepts/field-service#response
  • request-id : https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id

Note that logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here and click your client library for the specific guideline to enable it.

• here: https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging 

For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output. 

You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
 

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

Thanks,
 

Google Ads API Team