All accounts seem to have been rate limited

[Sanjay Hallan]

Hi,

I suspect a blanket rate limit has applied against our developer token.

Our system has been developed inline with all the recommendations, being:

- Single operation batches

- Exponential Back off inline with the seconds returned in the Rate Limit

Could you please advise?

Thanks

Sanjay

[Sanjay Hallan]

Hi,

From reading this link https://developers.google.com/adwords/api/docs/guides/rate-limits 

and

looking at the Rate Limit in more detail (RateExceededError <rateName=RequestsPerMinute, rateKey=developer_service_qps, rateScope=DEVELOPER, retryAfterSeconds=30>])

I believe our developer token has hit the limits of the basic access, we will be applying for the standard access via this link - https://services.google.com/fb/forms/standardaccess/

But in the mean time we are completely blocked, is there anything that can be done so we can resume in the mean time while we apply for standard access?

Thanks

Sanjay

[Sanjay Hallan]

Update - I have reset the developer token as it seems like the rate limit has been in force since Friday night.

I would be good understand what went on here still.

Thanks

Sanjay

[Google Ads API Forum Advisor Prod]

Hi Sanjay,

My apologies for the delay. The RateExceededError with rateScope=DEVELOPER should refresh itself within 24 hours since it was first encountered. Seeing that you mentioned that it was since Friday and was only now when you reset the developerToken that the issue was fixed, could you send to me any SOAP logs that were created so I can investigate further?

You may reply to me via the Reply privately to author option.

Thanks and regards,
Peter
Google Ads API Team

ref:_00D1U1174p._5001UAqoV4:ref

[Sanjay Hallan]

Hi,

I replied privately but then it went off into the abyss and I don't know how to view my sent private messages on google groups.

Anyway, our developer token was a standard access one and refreshing the token seemed to have done the trick.

We are wondering if splitting our clients across multiple MCC's would aid the situation regarding rate limits as we can then use the corresponding developer tokens for those clients.

Thanks

Sanjay

[Google Ads API Forum Advisor Prod]

Hi Sanjay,

I sent my response directly to your email, could you check? If you are unable to find it, you may refer below for the contents of my response :

"Thank you for providing more details about the issue. It seems that the client who pushed the 250k bid updates may have caused the RateExceededError. You may note that the rateScope=DEVELOPER indicates that the basic access limit for operations have been met which is around 10,000 operations as mentioned in the AdWords API's rate sheet.

Also upon checking, I could see that your application for standard access for your (943-XXX-XX4) MCC's developerToken has already been approved. You should no longer encounter the issue at the rateScope=DEVELOPER as your developerToken may now make unlimited operations. Let me know if this helps."

As for splitting the clients across multiple MCCs and getting a developerToken for each, I'm afraid that this would not be possible as only one developerToken is granted for an entity or company. Having the standard access level should already allow you to make unlimited operations and avoid the rate error at the rateScope=DEVELOPER level.

I would also recommend that you take note of our rate limits guide to learn more about the errors and how they can be managed.

[Sanjay Hallan]

Hi Peter,

Thanks for the reply.

I later found out that the developer token was always of "standard access" from looking at the API Center on the MCC, but we still got rate limited for 3 days..?

Thanks

Sanjay

[Google Ads API Forum Advisor Prod]

Hi Sanjay,

Having standard access level should already allow users to avoid the same issue you encountered. So I can further investigate, could you provide to me the requestIds that were generated when the errors occurred?

If those information are currently unavailable, you may for now, monitor your requests and send to me the SOAP logs or the requestIds so I can look into the issue closer. You may then send those to me using the Reply privately to author option.

Thanks and regards,
Peter
Google Ads API Team

ref:_00D1U1174p._5001UAqoV4:ref

[Sanjay Hallan]

Hi Peter,

Ok we will aim to implement the logging best practices and get logs to you shortly.

I do wonder if there is some anomaly detection software that detected the major jump in operations on Friday night which triggered the RateLimit on a standard access developer token?

Also we enabled the Google Ads API on the Google API / API & Services console so we could view the traffic that is being sent from our apps - but so far we cannot see any data/metrics for the Google Ads API on that console (https://console.developers.google.com/apis/api/), we enabled it yesterday, could you advise on this too please?

Thanks again for all your help so far.

Sanjay

[Google Ads API Forum Advisor Prod]

Hi Sanjay,

We currently have no way of tracking the number of operations made by developerTokens. The monitoring is done by the system. As for the Google Ads API console, my apologies as this is already outside of our expertise. If you wish to learn more about the console you may reach out to their support team via this link.