Re: Why are the query conditions of the old and new interfaces consistent, but the results are different

Hi, I think the query object I used is correct, because I use other customer IDs to query separately and get the same result. If *KEYWORD_VIEW* should not be used, which query object should I use. 在2022年3月15日星期二 UTC+8 18:58:38 写道： > Hi, > > Thank you for raising your concern to my team. >

Why are the query conditions of the old and new interfaces consistent, but the results are different

Hi, I use Adwords API interface and Google ads API interface to query the advertising series report on the same date, but the results are inconsistent *Adwords API:* ["awqlString":"Google\AdsApi\AdWords\Query\v201809\ReportQuery":private]=> string(334) "SELECT CampaignStatus, CampaignName, S

为什么新旧接口查询条件一致，但结果不同 为什么新旧接口查询条件一致，但结果不同 Why are the query conditions of the old and new interfaces consistent, but the results are different

Hi， I use Adwords API interface and Google ads API interface to query the advertising series report on the same date, but the results are inconsistent *Adwords API:* ["awqlString":"Google\AdsApi\AdWords\Query\v201809\ReportQuery":private]=> string(334) "SELECT CampaignStatus, CampaignName, S

How to get the correct query in the campaign location target report

Hi， According to the query result of Adwords API to Google ads API field mapping introduced by campaign location target, I failed. Method Name: /google.ads.googleads.v9.services.GoogleAdsService/SearchStream Host: googleads.googleapis.com Headers: { "x-goog-api-client": "gl-php\/7.4.5 gccl\/12.

How should the results of campaign performance report in Google ads API be consistent with Adwords API

Hi， the query: SELECT campaign.status, campaign.name, campaign.serving_status, metrics.clicks, metrics.impressions, metrics.interaction_rate, metrics.average_cpc, metrics.cost_micros, metrics.conversions, metrics.conversions_from_interactions_rate, metrics.cost_per_conversion, metrics.bounce_

Re: RE：Most Google ads API interface call results return segmentation fault

Thanks， I finally solved the problem because my grpc and protobuf versions are too low. After upgrading, I can call the interface normally 在2022年2月17日星期四 UTC+8 05:47:40 写道： > Hello, > > Thanks for reaching out. Can you please detail what the issue is that is > related to the logs? I see that no

Re: Most Google ads API interface call results return segmentation fault

According to the example( https://developers.google.com/google-ads/api/docs/account-management/get-account-hierarchy), I called the getaccounthierarchy interface and successfully obtained $accessiblecustomers, but the result of segmentation fault still appeared. [image: 85FC0128-A77C-43af-B868-D

Most Google ads API interface call results return segmentation fault

Hi, I understood that I can still use stored refresh tokens when migrating from Google Adwords to Google Ads as per https://developers.google.com/google-ads/api/docs/migration/carryover . so I used the authorization credentials of the AdWords API, and the call to the google.ads.googleads.