OfflineUserDataJob rate limits question

163 views
Skip to first unread message

foo-bar

unread,
May 24, 2023, 4:09:40 PM5/24/23
to Google Ads API and AdWords API Forum
We have standard developer token access.

According to this documentation: https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-matchAddOfflineUserDataJobOperationsRequest jobs can contain at most 100,000 operations per request. It's not listed publicly, but if you have standard access can you send more than 100,000 operations in a single request?
Regardless of # of operations in a request, is there a max payload size quota per request? Assume we have millions of email (only) identifiers that need to be apart of the offline job.

If we need to publish to multiple (separate) audience lists, can we make multiple API requests simultaneously or will we encounter RESOURCE_TEMPORARILY_EXHAUSTED? The documentation doesn't specify a Requests Per Second limit anywhere. Given that we are on the standard plan, using the same developer token, and Google ads customer id, could you mention any limits that we may hit if we need to produce to multiple customer lists at the same time, where we need to submit multiple operations to the offline job that we create?

Thanks!

Google Ads API Forum Advisor

unread,
May 26, 2023, 2:35:05 PM5/26/23
to adwor...@googlegroups.com

Hi,

Thank you for reaching out to us.

With regard to your concern, as per the access levels documentation, the standard access has unlimited daily operations. So you can send more than 100,000 operations in a single request. As per the customer match consideration, there are no limits on the number of operations you can add to a single job. However, for optimal processing, we recommend adding up to 10,000 identifiers in a single call to the OfflineUserDataJobService.AddOfflineUserDataJobOperations method and up to 1,000,000 identifiers to a single job.

Then, for the multiple request, if you need to submit more than 100,000 identifiers for a job, send multiple requests with the same job resource_name. Just kindly note that, even though you have standard access there is a chance of facing RESOURCE_TEMPORARILY_EXHAUSTED error when you make too many API calls to the same resource in a small amount of time. When you face these errors you have to retry the request after the amount of time specified in the error log. We recommend using exponential back-off policy to reduce these errors.

Reference links:

This message is in relation to case "ref:_00D1U1174p._5004Q2lt0So:ref"

Thanks,
 
Google Logo Google Ads API Team

 

Reply all
Reply to author
Forward
0 new messages