Query on product_group_view with filter on segments.conversion_action_name always yields INTERNAL_ERROR

60 views
Skip to first unread message

Konstantin Tarassow

unread,
Dec 4, 2023, 9:59:33 AM12/4/23
to Google Ads API and AdWords API Forum
Hello,

for exactly 1 account when we run a query on product_group_view and use an IN clause on segments.conversion_action_name we always run into an INTERNAL_ERROR, at least since weeks. This is only the case for 1 specific account, all other accounts from the same MCC and other customers are returning data just fine.

Here are the logs:

Method Name: /google.ads.googleads.v14.services.GoogleAdsService/SearchStream
Host: googleads.googleapis.com
Headers: {
    "x-goog-api-client": "gl-php\/8.0.30 gccl\/19.2.0 gapic\/19.2.0 gax\/1.18.2 grpc\/1.50.2 rest\/1.18.2 pb\/+n",
    "x-goog-request-params": "customer_id=8875125139",
    "developer-token": "REDACTED",
    "login-customer-id": "4554523147"
}
Request:
{"customerId":"8875125139","query":"\n                    SELECT segments.date,\ncampaign.id,\nad_group.id,\nad_group_criterion.criterion_id,\nsegments.conversion_action_category,\nsegments.conversion_action_name,\nmetrics.all_conversions,\nsegments.ad_network_type,\nsegments.device,\nmetrics.conversions_value,\nmetrics.view_through_conversions\n                    FROM product_group_view\n                    WHERE segments.date BETWEEN '2023-10-23' AND '2023-12-02'\n                    AND campaign.status IN(ENABLED, PAUSED, REMOVED)\n                    AND ad_group.status IN(ENABLED, PAUSED, REMOVED)\n                    AND ad_group_criterion.status IN(ENABLED, PAUSED, REMOVED)\n                    AND segments.conversion_action_name IN('store_visits', 'Ladenbesuche')\n                    AND metrics.all_conversions > 0.0\n                    AND ad_group_criterion.listing_group.type = 'UNIT'\n   AND segments.date = '2023-12-02' "}

Response
-------
Headers: {
    "request-id": "XcBQeB5fCVrDCJq7idXwNQ",
    "date": "Sun, 03 Dec 2023 05:54:20 GMT",
    "alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"
}

Fault
-------
Status code: 13
Details: Internal error encountered.
Failure: {"errors":[{"errorCode":{"internalError":"INTERNAL_ERROR"},"message":"An internal error has occurred."}],"requestId":"XcBQeB5fCVrDCJq7idXwNQ"}
Exception in retryDecider: {
    "message": "Internal error encountered.",
    "code": 13,
    "status": "INTERNAL",
    "details": [
        {
            "@type": "google.ads.googleads.v14.errors.googleadsfailure-bin",
            "data": "<Unknown Binary Data>"
        },
        {
            "@type": "grpc-status-details-bin",
            "data": "<Unknown Binary Data>"
        },
        {
            "@type": "request-id",
            "data": "XcBQeB5fCVrDCJq7idXwNQ"
        }
    ]
}

Google Ads API Forum Advisor

unread,
Dec 4, 2023, 2:28:02 PM12/4/23
to konstanti...@emarketing.com, adwor...@googlegroups.com
Hi,

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

After reviewing your concern, I understand that you are getting an Internal Error while trying to extract data from product_group_view. This error occurs when something unexpected happens while processing the request. You can refer to this help center article on how to handle the InternalError. When you retry requests, use an exponential backoff policy. For example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry. Exponential backoff helps ensure you are not calling the API too many times.

If the issue persists after trying the provided suggestion, then you may provide us with the complete request and response logs with request ID and request header generated on your end to better assist you further.

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.NetPHPPythonRuby 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.!5004Q02qWVKW:ref"

Thanks,
 
Google Logo Google Ads API Team


Konstantin Tarassow

unread,
Dec 5, 2023, 1:33:13 AM12/5/23
to Google Ads API and AdWords API Forum
Hello, this happens on every request for the given client, since at least several weeks, regardless of time of the day or number of requests.
We are already using a backoff retry mechanism.

Google Ads API Forum Advisor

unread,
Dec 5, 2023, 3:38:44 AM12/5/23
to konstanti...@emarketing.com, adwor...@googlegroups.com
Hi,

Thank you for getting back to us.

kindly provide us with the complete updated API logs  request and response logs with request ID and request header generated on your end to better assist you further.

Konstantin Tarassow

unread,
Dec 5, 2023, 6:36:21 AM12/5/23
to Google Ads API and AdWords API Forum
Hello, this are the corresponding logs as output by the officials GoogleAds API SDK, incl. headers and request-id:

Google Ads API Forum Advisor

unread,
Dec 5, 2023, 2:11:38 PM12/5/23
to konstanti...@emarketing.com, adwor...@googlegroups.com
Hi,

Thank you for getting back to us.

I will check with our team regarding your issue and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

Google Ads API Forum Advisor

unread,
Dec 5, 2023, 4:26:54 PM12/5/23
to konstanti...@emarketing.com, adwor...@googlegroups.com
Hi Konstantin, my name is Devin, and I've been looking into your issue.

This appears to be a bug on our end, and I am working with our engineers to resolve the issue. I'll be in touch as soon as I have an update.

All the best,
Devin

The Google Ads API Team

ref:!00D1U01174p.!5004Q02qWVKW:ref
Reply all
Reply to author
Forward
0 new messages