Re: RateExceededError - TrafficEstimatorService with New Accounts created under MCC

2013-11-05 Thread John Slegers
I'm having the same problem with an account I created the normal way. I created both my test and production account earlier today. I've focused mostly on the TargetingIdeaService, but I can't even get the examples from the PHP client library to work. No matter how I adjust my search criteria,

Re: RateExceededError - TrafficEstimatorService with New Accounts created under MCC

2013-11-05 Thread Anash P. Oommen (AdWords API Team)
Hi John, Mark, You are seeing the issue because it is a fresh account. If you give it a while, or you setup some ads in this account and allow it to serve, the account should move out of the new account status and higher rate limits will apply to the accounts. Cheers, Anash P. Oommen, AdWords

Re: RateExceededError - TrafficEstimatorService with New Accounts created under MCC

2013-11-05 Thread moleary
Hi Anesh, Thanks for the feedback. I guess the problem is it takes about 4 hours for the account to move out of this state. With our UI design we allow the user to view traffic estimates for keywords after creating the first Ad. I have got around the problem by creating a few backup accounts,

Re: RateExceededError - TrafficEstimatorService with New Accounts created under MCC

2013-10-31 Thread David Torres (AdWords API Team)
Hi Mark, Do you mind giving me a requestId of the failure? I'd be glad to follow up with my team about this issue. Best, - David Torres - AdWords API Team On Thursday, October 24, 2013 11:49:49 AM UTC-4, mol...@knowme.net wrote: Coming across a RateExceededError with a single call to the

RateExceededError - TrafficEstimatorService with New Accounts created under MCC

2013-10-24 Thread moleary
Coming across a RateExceededError with a single call to the TrafficEstimatorService after creating a new Adwords Account via the API under the master MCC Account using v201306. Steps to reproduce: 1) Create a new Adwords account via the API. 2) Configure Developer Token and clientCustomerId in