Hello Deny, Thanks for getting back to us.
We completely understand on the inconvenience you've encountered and we're here to help you on this. For us to help you address on your question 3, please enable logging and retry your request to generate these logs (request and response with request-id). You can then send those logs via this email ([email protected]). In addition, you mentioned that if you omit the “where campaign.id=11615336854” clause, it returns one adgroup row for that campaign. I've checked on the provided customer ID and I can see that the campaign ID only contains a single adgroup. Could you further elaborate on this? As an aside, I need to remove your post as it might contain data that isn't intended to shared publicly. Below is a copy of your post with the masked data. "Hello Ernie, Thank you for your reply and sorry about venting so bluntly but I am very upset about the whole thing. Sorry to reply publicly but the “Reply to Author” button appears disabled to me. I don’t care about items 1, 2 and 4 as I’ve fixed those myself on my end. But concering item 3, we have almost 10 million rows of dimension data for adgroup criterion for one client, another 3 million rows for another one and so on. We query those 4 times a day and it’s taking over 5 hours to get all data without the incremental logic we were using before the Google Ads query engine broke. We’re using the Python client libraries, all updated to the latest version, so I don’t really have access to the actual raw request and results (the later would solve many of my issues that I’ve had to build workarounds to fix btw). The only thing I can provide is the query and response metadata, we’re using the SearchGoogleAdsStreamRequest method: *** QUERY for customer ID *** <> *** RESPONSE *** <> Please note that if I omit the “where campaign.id=11615336854” clause, it returns one adgroup row for that campaign. Also, we use the same function for querying with and without the “where” clause, and it works perfectly without it for all entities. Cheers, Deny" Regards, Mark Kevin Albios Google Ads API Team ref:_00D1U1174p._5004Q2HDaEA:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 "AdWords API and Google Ads 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/5Kyzu000000000000000000000000000000000000000000000QTR2P200enwP5Ss7RKGcKP2yk3D_QA%40sfdc.net.
