Hi everyone, Thank you for raising this concern to the Google Ads API support team. Please excuse us for only getting back now as your message failed to be routed to our support queue.
In order for our team to have a better understanding about this behavior and can provide precise recommendations, can you please provide the complete API logs below? - 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 - request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers You may then send the requested logs via the *Reply privately to author* option. If this option is not available, you may send the details directly to our [email protected] alias instead. Note that these 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 (https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging) for the specific guideline to enable it. For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include HTTP response headers in the output. Regards, Google Ads API Team On Thursday, August 3, 2023 at 4:00:50 PM UTC+8 [email protected] wrote: > Hello, we started receiving this error for a few of our clients. I was > trying to setup request logging as per the docs, but nothing was logged. We > do have a request ID: bNklNVkIz392VhtbuDfLzg > API version: v14 > > Query: "SELECT expanded_landing_page_view.expanded_final_url, > metrics.clicks, metrics.impressions FROM landing_page_view WHERE > segments.date BETWEEN '2023-07-04' AND '2023-08-02' AND metrics.impressions > > 0 ORDER BY metrics.impressions DESC". > > Error: > array:1 [ 0 => array:1 [ "error" => array:4 [ "code" => 400 "message" => > "Request > contains an invalid argument." "status" => "INVALID_ARGUMENT" "details" > => array:1 [ 0 => array:3 [ "@type" => " > type.googleapis.com/google.ads.googleads.v14.errors.GoogleAdsFailure" " > errors" => array:1 [ 0 => array:2 [ "errorCode" => array:1 [ "requestError" > => "UNKNOWN" ] "message" => "The error code is not in this version." ] ] " > requestId" => "bNklNVkIz392VhtbuDfLzg" ] ] ] ] ] While writing this, I > figured out that this request succeeds if I remove SummaryRowSetting. > Usually if our query includes metrics, we also set SummaryRowSetting as > SUMMARY_ROW_WITH_RESULTS. Why would this start failing now? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/a8c89875-1e80-4745-9658-0a8ddb8bb777n%40googlegroups.com.
