Targeting Service - Rate limit

96 views
Skip to first unread message

Ian Broadhead

unread,
Jul 7, 2016, 4:39:17 AM7/7/16
to AdWords API Forum
Hi,

For the last few days, we got more RATE_EXCEEDED errors than before calling the Targeting service through the v201605 API.
It does seem we are calling the service at the same rate as before using the v201509 api, were there any changes on the targeting service ?
Does the rate limit has been changed in the version of the API?
If it is the case, is there any recommandations?


Best regards

Peter Oliquino

unread,
Jul 7, 2016, 6:09:57 AM7/7/16
to AdWords API Forum
Hi Ian,

The rate limits for the AdWords API Services depends primarily on the access level granted to the user's developer token. For basic access, the operational limit is at 10,000 operations per day for all services and about 1,000 report downloads per day. You can refer to our rate sheet for the cost per operation when using the API. You may also refer to this link on methods on how to mitigate rate limit issues. Another recommendation would be to upgrade your access level to standard access to execute unlimited operations per day by filling up this form.

If the issue persists, could you provide your SOAP request and response? Also, please do so using Reply privately to author.

Thanks,
Peter
AdWords API Team

Peter Oliquino

unread,
Jul 8, 2016, 1:07:05 AM7/8/16
to AdWords API Forum
Hi Ian,

Thanks for the information. I could see that your account is linked to a single manager account, however, upon checking the MCC account through Account Setttings > AdWords API Center, it seems that the account's access has been rejected. Please see our Required Minimum Functionality and you may also write to the Compliance Team to see if you meet the requirements and then reapply.

I hope this helps, and in the event that the new standard access has been approved for the MCCs developer token and the issue still persists, please let us know.

Thanks and regards,
Peter
AdWords API Team

Peter Oliquino

unread,
Jul 8, 2016, 6:27:24 AM7/8/16
to AdWords API Forum
Hi Ian,

Thanks for the added information. Yes, I confirm that the MCC account in the screenshot has standard access. However, I was referring to the MCC in which the client account mentioned in your SOAP logs is linked to (Kindly go Account Settings > Account Access of the client account). This MCC account is the one with the rejected access and also the one that appears to be managing your client account.

I also looked into the MCC account with the standard access and I could not see the client account that you are using in the list of accounts being managed by that MCC. Kindly make sure that the developer token and OAuth 2 credentials that you are using are that of the manager account in your screenshot. Additionally, I recommend that you link your client account to the MCC with the standard access through this guide and use the credentials of that MCC to manage your client account in order to avoid getting the RateExceedError.

Also, I am unable to email you privately as I am receiving an error when I do. I am posting here in the forum instead and that is why I am unable to disclose the customer ids of the accounts I am referring to. If it is still unclear, please reply using Reply privately to author and include a separate email that I can use to contact you with.

Peter Oliquino

unread,
Jul 12, 2016, 12:46:48 AM7/12/16
to AdWords API Forum
Hi Ian,

Can you confirm if you have also used the developer token, and the other OAuth 2 credentials (clientId, clientSecret) associated with the MCC with standard access? 

If you already have and the issue still persists, can you send me once more using Reply privately to author your SOAP request and response to help me investigate further?

Anthony Madrigal

unread,
Jul 12, 2016, 10:43:49 AM7/12/16
to AdWords API Forum
Hi Ian,

The error you are getting has a scope of ACCOUNT. This means that you are making too many requests at the same time on a single account. You can find a detailed explanation on this error in this guide.

Regards,
Anthony
AdWords API Team
Reply all
Reply to author
Forward
0 new messages