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 4863710790 ***
select ad_group.id, ad_group.name, ad_group.campaign, ad_group.type, 
ad_group.status
from ad_group
where campaign.id=11615336854
****************************************

*** RESPONSE ***
StatusCode.OK  (_Metadatum(key='content-disposition', value='attachment'), 
_Metadatum(key='date', value='Wed, 26 May 2021 13:45:09 GMT')) 
(_Metadatum(key='content-disposition', value='attachment'), 
_Metadatum(key='date', value='Wed, 26 May 2021 13:45:09 GMT'))
*** RETURNED VALUES ***
[]
***********************

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

From: [email protected] <[email protected]> On Behalf Of 
Google Ads API Forum Advisor Prod
Sent: Wednesday, May 26, 2021 3:42 AM
To: [email protected]
Subject: [EXTERNAL] RE: So many bugs & broken things

Hi,

Sorry to hear your frustration. Allow me to provide support to your concern.

As for the first 2 items, since the issue is more specific to client library, 
then I would suggest posting it to one of the support channels below based on 
the client library that you are using. You can get support from the author of 
the client library that is more equipped on this topic.

  *   
https://github.com/googleads/google-ads-java/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-java/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDG5zAKns$>
  *   
https://github.com/googleads/google-ads-dotnet/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-dotnet/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDIo9cDxg$>
  *   
https://github.com/googleads/google-ads-php/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-php/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDAYw-s2R$>
  *   
https://github.com/googleads/google-ads-python/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-python/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDOoh6tGN$>
  *   
https://github.com/googleads/google-ads-ruby/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-ruby/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDNhc7F2I$>
  *   
https://github.com/googleads/google-ads-perl/issues<https://urldefense.com/v3/__https:/github.com/googleads/google-ads-perl/issues__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDLk8pCsg$>

"3) When issuing search_stream and querying ad_group, ad_group_ad, etc., "where 
campaign.id = xxxxx" no longer works, bringing no results"
- Could you provide the complete 
request<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*request__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDDRmuM1U$>
 and 
response<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*response__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDFmfv2Et$>
 logs with request 
ID<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/call-structure*request-id__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDE76_VwO$>
 generated on your end to investigate this issue and to address it? Please 
provide it via Reply privately to author option.

"4) Things keep getting better and better as any column named "type" NEEDS TO 
BE QUERIED with the original name, but HAS TO BE READ as "type_". "
-To take a closer look at this issue, could you also provide the complete 
request<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*request__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDDRmuM1U$>
 and 
response<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*response__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDFmfv2Et$>
 logs with request 
ID<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/call-structure*request-id__;Iw!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDE76_VwO$>
 generated on your end where we can see it? Please provide it also through 
Reply privately to author option.

Regards,
[Google Logo]
Ernie John Blanca Tacata
Google Ads API Team



ref:_00D1U1174p._5004Q2HDaEA:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/<https://urldefense.com/v3/__https:/googleadsdeveloper.blogspot.com/__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDARCDm9V$>
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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]<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]<mailto:[email protected]>
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en<https://urldefense.com/v3/__http:/groups.google.com/group/adwords-api?hl=en__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDPeTXgy_$>
---
You received this message because you are subscribed to a topic in the Google 
Groups "AdWords API and Google Ads API Forum" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/adwords-api/-Ya6Bdad1bM/unsubscribe<https://urldefense.com/v3/__https:/groups.google.com/d/topic/adwords-api/-Ya6Bdad1bM/unsubscribe__;!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDCu5enEn$>.
To unsubscribe from this group and all its topics, send an email to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/bj3Wv000000000000000000000000000000000000000000000QTPBXW00ytQmQPtxQdWzGD8ny2fkOA%40sfdc.net<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/adwords-api/bj3Wv000000000000000000000000000000000000000000000QTPBXW00ytQmQPtxQdWzGD8ny2fkOA*40sfdc.net?utm_medium=email&utm_source=footer__;JQ!!N96JrnIq8IfO5w!wWsv5A7g3WCqEZ5B-TlWSMf0DR_nNNWoYQtbspnIEqzJSPP-gWML0v_zAJrPDN5qNOyY$>.

This message contains information which may be confidential and privileged. 
Unless you are the intended recipient (or authorized to receive this message 
for the intended recipient), you may not use, copy, disseminate or disclose to 
anyone the message or any information contained in the message.  If you have 
received the message in error, please advise the sender by reply e-mail, and 
delete the message.  Thank you very much.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/SA1PR06MB7958A33748F5F14EEF4EB7CFFD249%40SA1PR06MB7958.namprd06.prod.outlook.com.
  • So man... 'Deny Watanabe' via AdWords API and Google Ads API Forum
    • R... Google Ads API Forum Advisor Prod
      • ... 'Watanabe, Deny (SPL-MEW)' via AdWords API and Google Ads API Forum
        • ... Google Ads API Forum Advisor Prod
    • R... Mat
      • ... 'Deny Watanabe' via AdWords API and Google Ads API Forum

Reply via email to