RateExceededError for Standard Accounts

[Charles Michael]

Hello,

We're hitting RateExceededErrors (Reason: RATE_EXCEEDED, Scope: ACCOUNT, Retry: 30) while performing TargetingIdeaService lookups. I already have setup a 45 second sleeper between requests which seems very long already, especially given we have standard access. With such a long pause between requests, we can't do more than 2000 requests per day, well below the basic access even though we have standard access. Why are we hitting rate limits with such a long sleeper between requests? I'm already batching requests and queuing just 1 request at a time, so it doesn't appear to be a programmatic issue of making requests too quickly. 

Thank you.

[Anthony Madrigal]

Hello Charles,

The rate exceeded error you are running into is ACCOUNT scope. This happens regardless of whether you have Standard access. The guide I provided gives some solutions to remedy this error.

Please let me know if you have any other issues.

Regards,

Anthony

AdWords API Team

[Charles Michael]

Hello, I read thru the guide and it seems that TargetingIdeaService only costs 1 operation regardless of the number of keywords being submitted (I'm doing batches of 600 keys/request). I've already implemented a 45 second throttle between requests and everything is being run sequentially (no parallel requests). It seems I've implemented most of the strategies in this guide and 45 seconds per request seems to be the ideal number where I don't trigger a rate limit issue. I understand the rates vary by account, but the account I'm using is a large spender, so it should be much better than 45 seconds per request for the rate limit. Is there any other suggestions that we could implement to reduce this time as we can only do <2000 requests/day at this rate limit. 

Thank you.

[Anthony Madrigal]

Hi Charles,

ACCOUNT scope errors do not relate to the number of the operations. Having said that, here is a list of Best Practices that may help you optimize your code.