Hello,
Hope you are doing fine. Thank you for reaching out to the Google Ads API team.
Moving forward, in order for our team to have a better view and can provide
accurate recommendations to you, could you provide the complete request and
response logs with request ID and request header
Follow up question sent in one more private email. Thanks!
On Tuesday, February 8, 2022 at 12:21:11 PM UTC+2 Oksana Sulyma wrote:
> Hi Aryeh,
> I appreciate your help very much. The answer makes a lot of sense to me. I
> can confirm that I got data match.
> Is it possible to edit your previous
Hi Oksana,
I ran your Ads API report with modification and summary row returned like
AdWords:
curl -v
"https://googleads.googleapis.com/v9/customers/1329679017/googleAds:search; \
--header "Content-Type: application/json" \
--header "developer-token:{}" \
--header "Authorization: Bearer
Also if I remove
geographic_view.country_criterion_id,
segments.geo_target_region,
segments.geo_target_metro,
from my report definition For Google Ads API call, I still get the same
numbers (smaller than expected).
(Actually I need these fields, just trying to guess what could be wrong
with
Hi Aryeh,
"Could you try taking out segments.geo_target_region,
segments.geo_target_metro and replacing them
with segments.geo_target_most_specific_location? " - just tried this, no
change in summaries.
Sent you complete request and response info in private message.
Will appreciate any other
Hi Aryeh,
"Could you try taking out segments.geo_target_region,
segments.geo_target_metro and replacing them
with segments.geo_target_most_specific_location? " - just tried this, no
change in summaries.
Any other ideas?
On Thursday, February 3, 2022 at 10:58:15 PM UTC+2 adsapi wrote:
> Hi
Hi Oksana,
Could you try taking out segments.geo_target_region, segments.geo_target_metro
and replacing them with segments.geo_target_most_specific_location? I am asking
this because you are filtering out all metrics that aren't from a region and a
metro area.
If this still doesn't fix the
