Problem with new aggregate views in v17

180 views
Skip to first unread message

Mike Sullivan

unread,
Jun 10, 2024, 4:51:25 PM6/10/24
to Google Ads API and AdWords API Forum
When I make a REST query to:

with content:
{"query":"SELECT asset.id,metrics.impressions FROM campaign_aggregate_asset_view WHERE segments.date DURING LAST_30_DAYS PARAMETERS omit_unselected_resource_names=true"}

It responds with 400 Bad Request with Content:
{
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.ads.googleads.v17.errors.GoogleAdsFailure",
        "errors": [
          {
            "errorCode": {
              "requestError": "UNKNOWN"
            },
            "message": "The error code is not in this version.",
            "trigger": {
              "stringValue": "A___Asset.asset_id"
            }
          }
        ],
        "requestId": "hHwTN9-DTOaF1U7jf6Sgog"
      }
    ]
  }
}

I get this error for any query that uses a field from the 'asset' resource or the 'campaign' resource, both of which should be ok.

Mike

Google Ads API Forum Advisor

unread,
Jun 11, 2024, 3:19:39 AM6/11/24
to mike.3....@gmail.com, adwor...@googlegroups.com
Hi Mike,

Thank you for reaching out to the Google Ads API support team.

Based on the information provided, I understand that you are encountering an UNKNOWN error while making the API request. I would recommend you to refer to this omit_unselected_resource_names guide while using the parameters in the GAQL queries. Kindly note that you have not provided the customer ID in order to check from our end. In order to investigate your issue further, kindly provide us with the complete API logs (request and response logs with request-id and request header) generated at your end and uncropped UI screenshot of the Google Ads account (with visible customer ID) by highlighting the fields and metrics from where you are trying to retrieve the data from the API.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJHBn:ref" (ADR-00239377)

Thanks,
 
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages