Different responses between Google Ads API and AdWords API

[Kate Orlova]

Hi!

I'm sending 2 requests for different APIs and receive different responses:

for AdWords API:

curl --request POST --http1.1 --header "Authorization: Bearer ${AUTH_TOKEN}" --header "developerToken: ${DEV_TOKEN}" --header "clientCustomerId: ${CUSTOMER_ID}" --data "__rdquery=SELECT Id, Cost, CriterionId from AD_PERFORMANCE_REPORT where Cost > 0 DURING 20220214,20220214&__fmt=CSV" https://adwords.google.com/api/adwords/reportdownload/v201809

I'm receiving 22 rows with all filled CriterionId

for Google Ads API:

curl --http1.1 --header "Authorization: Bearer ${AUTH_TOKEN}" --header "Content-Type: application/json" --header "developer-token: ${DEV_TOKEN}" --header "login-customer-id: ${LOGIN_CUSTOMER_ID}" --data-raw '{"query": "SELECT ad_group_ad.ad.id, metrics.cost_micros, segments.keyword.ad_group_criterion FROM ad_group_ad where segments.date='20220214' and metrics.cost_micros > 0"}' "https://googleads.googleapis.com/v9/customers/${CUSTOMER_ID}/googleAds:searchStream"

And I'm receiving 0 rows. 

If I remove segments.keyword.ad_group_criterion I receive same values as in AdWords API.

I know that Google Ads API ignores rows where segment is null, but here we have criterions for ads.

[Google Ads API Forum Advisor]

Hello Kate,

Thank you for reaching out to us.

So our team can better check on those discrepancies that you've mentioned, can you share to us the following details below?

• Using the AdWords API
  • Customer ID
  • complete report definition in XML or AWQL form
• If using the Google Ads API
  • Customer ID
  • login-customer-id
  • complete GAQL
  • complete logs (request and response with request-id)

Please send the requested details 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.

Regards,

Mark Kevin Google Ads API Team

ref:_00D1U1174p._5004Q2WwbpK:ref