Hello, Unfortunately, the 4MB limit is based on the underlying gRPC protocol, so there's nothing we can do to increase that overall byte limit.
However, we are working on a feature that will allow downloading of search query results as a whole, either streaming or by some other mechanism, which should alleviate both the paging issue and the overhead of multiple round trips once it is ready. I cannot speak for all client libraries, but I do have intimate knowledge of the Ruby library and I do know that paging is currently abstracted away to such a point that you actually cannot manually adjust page size between requests. We are aware of this issue as well and are planning some improvements that would allow more fine-grained control if desired. I will pass along this feedback as well to the other client library teams. Regards, Mike, Google Ads API Team ref:_00D1U1174p._5001UAqPlE: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]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/49Yy7000000000000000000000000000000000000000000000PS0B8I00cyTrkXYkRzKMn4f_yny1Og%40sfdc.net. For more options, visit https://groups.google.com/d/optout.
