Re: quota/resource exhausted when switching from .net v14 to v15

[Mads Grout]

This is exactly the generic answer i sadly wasn't looking for

Assuming these are the Quotas the UploadUserDataAsync is a mutate request 
if i am not mistaken? Unless this also is limited like the 1 QPS?..
https://developers.google.com/google-ads/api/docs/best-practices/quotas

Everything is working just fine using V14. We only bumped the Client 
library. So something underlying must have changed...
torsdag den 22. februar 2024 kl. 14.00.04 UTC+1 skrev Google Ads API Forum 
Advisor:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> By reviewing your query, I understand that you are getting the "
> RESOURCE_EXHAUSTED 
> ",
>  
> which means that a system frequency limit has been exceeded. Kindly prevent 
> sending too many requests in a short period of time and also ensure to set 
> up short delays between requests or combine more operations in fewer 
> requests. Also, please check this sample code for how to Handle a Rate 
> Exceeded Error 
> 
>  for 
> more information.
>
> Additionally, we also have daily API operation limits where requests that 
> violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You 
> may check out API Limits and Quotas 
>  for 
> more information. 
>
> Also, provide us with the updated complete API logs (request 
> 
>  and response 
> 
>  with request-id 
> 
>  and request header 
> )
>  
> generated at your end to assist you better.
>
> Since you are using a client library and haven't enabled the logging yet, 
> I would request you to enable logging for the specific client library that 
> you are using. You can refer to the .Net 
> 
>  guide to 
> enable logging at your end. For REST interface requests, you can enable 
> logging via the curl command by using the -i flag.
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rzM0M:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/fd89602b-10d0-43f6-b055-56edffb7442an%40googlegroups.com.

Quota/Resource Exhausted when switching from .NET V14 to V15

[Mads Grout]

Hi

We are making the switch from .NET v14 library to v15 to accommodate the 
new consent status.

While doing this we encountered a problem.

Hour system uses the UserdataService.UploadUserDataAsync  to upload user 
data to customermatch lists.
Currently using the V14 library it is able to handle a lot of load. Like 
thousand UserIdentifiers a minute or more when we make concurrent calls.

When switching to the V15 library we suddenly just get the following error: 
"Status(StatusCode=\"ResourceExhausted\", Detail=\"Resource has been 
exhausted (e.g. check quota).\")"

I am quite familiar with all of the documentation and i don't need any of 
the basic answers pointing to what UserDataService was made for and what it 
can handle.
This solution has been working for well over a year now... And now when 
bumping to V15 i suddenly doesn't.

I'm trying to figure out why this happens... I can't seem to find anything 
regarding any Quota/Rate limiting changes in any release note, changelog or 
blog anywhere.

Is there any explanation for this??

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e222109c-1f76-42c4-ae88-b2dd52b6ac38n%40googlegroups.com.

Google AdWords MutateMembersAsync vs Google Ads UploadUserDataAsync

[Mads Grout]

Hi
As our company migrating an integration from the AdWords Api to the Google 
Ads api we have encountered a problem.

*Case:*
We have an integration which is using the old AdWords api to create, remove 
and update members in userlists.
The integration runs every 5 minutes to check whether new users should be 
added to the userlist or some old members should be removed.

*Problem:*
When a userlist is added there is a possibility that the list we are adding 
has 1million or more users which has to be added to the userlist in Google 
ads.

The old Adwords api call MutateUserMembersAsync was able to handle up to 
2000 userIds in 1 call. This made it fairly feasible to add alot of members 
at the start when creating the userlist.

The Google Ads api can only handle 100 userIds in 1 api call with the 
UploadUserDataAsync method.
As our system is working realtime and looking for updates every 5 minutes 
we cannot use the asynchronous OfflineUserDataJob.
So this is a significant slowdown in performance and is a very big problem 
as we have several customers actually using the integration.

Could you please elaborate on why it went from being able to handle 2000 
userIds down to only 100 userIds?
And is it possible to have the limit raised above 100 userIds?? Especially 
when BatchJobs aren't working with userlists yet.

Best Regards
Mads Grout

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/09e7e0c2-b886-4c3e-9ea7-3326162f8687n%40googlegroups.com.

Maximum UserIdentifiers in OfflineUserDataJobOperation

[Mads Grout]

Hi.

I am building a background service that automatically updates Userlists 
twice a day.
We are planning to completely replace the members of the list with the 
"remove_all" bool.

The documentation (see picture) that the maximum operations per job is 
100,000.

However 1 operation can many UserIdentifiers (emails in our case).
I cant seem to find a maximum limit for UserIdentifiers in the 
documentation? Is there a maximum number of UserIdentifiers 1 operation can 
hold?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b2b83b09-527f-4ae6-84c0-27a41f62d942n%40googlegroups.com.