Hi Danial, we're requesting KeywordEstimates for search campaigns only. So it shouldn't be affected by lower limits on the Placement reqeust type!? Please see example request below:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www. w3.org/2001/XMLSchema-instance">; <soapenv:Header> <ns1:RequestHeader xmlns:ns1="https://adwords.google.com/api/adwords/o/v201409"; soapenv:mustUnderstand="0"> <ns2:clientCustomerId xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201409";>XXXXX</ns2:clientCustomerId>; <ns3:developerToken xmlns:ns3="https://adwords.google.com/api/adwords/cm/v201409";>XXXXX</ns3:developerToken>; <ns4:userAgent xmlns:ns4="https://adwords.google.com/api/adwords/cm/v201409";>XXXXX</ns4:userAgent> <ns5:validateOnly xmlns:ns5="https://adwords.google.com/api/adwords/cm/v201409";>false</ns5:validateOnly>; <ns6:partialFailure xmlns:ns6="https://adwords.google.com/api/adwords/cm/v201409";>false</ns6:partialFailure>; </ns1:RequestHeader> </soapenv:Header> <soapenv:Body> <get xmlns="https://adwords.google.com/api/adwords/o/v201409";>; <selector> <campaignEstimateRequests> <campaignId>XXXXX</campaignId> <adGroupEstimateRequests> <adGroupId>XXXXX</adGroupId> <keywordEstimateRequests> <keyword> <ns7:id xmlns:ns7="https://adwords.google.com/api/adwords/cm/v201409";>XXXXX</ns7:id>; <ns8:text xmlns:ns8="https://adwords.google.com/api/adwords/cm/v201409";>XXXXX XXXXX</ns8:text> <ns9:matchType xmlns:ns9="https://adwords.google.com/api/adwords/cm/v201409";>BROAD</ns9:matchType>; </keyword> <maxCpc> <ns10:ComparableValue.Type xmlns:ns10="https://adwords.google.com/api/adwords/cm/v201409";>Money</ns10:ComparableValue.Type>; <ns11:microAmount xmlns:ns11="https://adwords.google.com/api/adwords/cm/v201409";>10000</ns11:microAmount>; </maxCpc> <isNegative>false</isNegative> </keywordEstimateRequests> </adGroupEstimateRequests> <criteria xmlns:ns12="https://adwords.google.com/api/adwords/cm/v201409"; xsi:type="ns12:Location"> <ns12:id>2276</ns12:id> </criteria> <criteria xmlns:ns13="https://adwords.google.com/api/adwords/cm/v201409"; xsi:type="ns13:Language"> <ns13:id>1001</ns13:id> </criteria> </campaignEstimateRequests> </selector> </get> </soapenv:Body> </soapenv:Envelope> Am Dienstag, 25. November 2014 13:55:58 UTC+1 schrieb Danial Klimkin: > > Hello Christian, > > > What kind of requests are those? We've set a lower limits on the PLACEMENT > ideas request type as it is deprecated but other types should not be > affected. > > > -Danial, AdWords API Team. > > > On Monday, November 24, 2014 6:37:34 PM UTC+3, Christian Borck wrote: >> >> Hi Ray, >> >> thank you for your response. We've implemented the suggested strategies >> to handle varying limits. >> But: Since 3 days we are experiencing a significant drop in QPS over all >> accounts we estimating traffic for: >> >> [RateExceededError <rateName=RATE_LIMIT, rateKey=null, rateScope=ACCOUNT, >> retryAfterSeconds=30>] >> >> We already throttled to 1 QPS and still get this error. Did you change >> something concerning the limits in general? >> In total we get less than 1/6th of the performance compared to the >> performance before. >> >> Thanks, Christian >> >> >> Am Dienstag, 16. September 2014 20:09:10 UTC+2 schrieb Ray Tsang (AdWords >> API Team): >>> >>> Christian, >>> >>> Please review the Rate Limit guide >>> <https://developers.google.com/adwords/api/docs/guides/rate-limits> - >>> freshly >>> created new AdWords account may have a significantly more restrictive rate >>> limit. The rate limit may be relaxed over time for freshly created >>> accounts. You may want to explore the different strategies in the guide to >>> deal w/ the rate limits. >>> >>> Thanks, >>> >>> Ray >>> >>> On Tuesday, September 16, 2014 11:53:53 AM UTC-4, Christian Borck wrote: >>>> >>>> In one of our applications we're using the traffic estimator service to >>>> get keyword estimates for different maxCPCs and get rate-limit errors >>>> (name=RateExceededError, rateName=RATE_LIMIT, rateScope=ACCOUNT) on the >>>> account level as soon as we do on average more than 3 requests per second. >>>> This significantly slows down our system since we have accounts with a >>>> large number of campaigns and we want to handle them in parallel (on the >>>> campaign-level). We'd like to know if there is any way to increase the >>>> number of permitted requests. Or can you suggest a different way to deal >>>> with this problem? >>>> >>>> Thanks, >>>> Christian >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/475d8e82-9565-420c-9f55-89d67542fca2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
