unexpected error TOO_MANY_USER_IDENTIFIERS when add_offline_user_data_job_operations

399 views
Skip to first unread message

Keisuke Motoda

unread,
Jan 24, 2022, 4:52:52 AM1/24/22
to Google Ads API and AdWords API Forum
---- environment ----
python==3.9.6
google-ads==13.0.0
---------------------

I met an error TOO_MANY_USER_IDENTIFIERS when doing "add_offline_user_data_job_operations" with python library.

Our python system that append user id to an audience with python handles with up to 20M userId list.

the system divides list of userId into 100K if the list size over 100K, then calls "add_offline_user_data_job_operations".

This system works well (w/o TOO_MANY_USER_IDENTIFIERS error) at least until Jan 21st 2022.

Then when did at Jan 24th 2022, We came to get an error below.

```
Maximum number of user identifiers allowed per request is 100,000 and per operation is 20.
offline_user_data_job_error: TOO_MANY_USER_IDENTIFIERS
```

So, We did with 20 userId list as trial, there was no error.
and when 21 userId list, the error occurs.

and also, the error message of "TOO_MANY_USER_IDENTIFIERS" is not same as this
https://developers.google.com/google-ads/api/reference/rpc/v8/OfflineUserDataJobErrorEnum.OfflineUserDataJobError


Our questions are
1. Has the spec of this api changed recently?
2. Concretely, what is "request", "operation" in the error message?
3. How handle the process when 20M userId list?

Thank you for advance.

Dave Milsom

unread,
Jan 24, 2022, 12:30:41 PM1/24/22
to Google Ads API and AdWords API Forum
We started seeing the same about two days ago using the customers.uploadUserData REST API endpoint. We are batching to 100 operations records, which is in the spec.

Google Ads API Forum Advisor

unread,
Jan 24, 2022, 8:39:48 PM1/24/22
to dave....@tealium.com, adwor...@googlegroups.com
Hi Dave,

Thank you for posting your concern. Allow me to provide support to your concern.


1. Has the spec of this api changed recently?
2. Concretely, what is "request", "operation" in the error message?

For these 2 questions, it appears that the behavior that you encountered is related to this blog post that the maximum number of user_identifers set in a UserData object will be reduced from 100,000 to 20. This is to clarify that each set should represent a single user.


3. How handle the process when 20M userId list?
As for this question, you will need to create multiple operations for each unique or single user to upload it in a user list.

Also, allow me to raise a feature request to my team so that the update mentioned in the blog post will be reflected in our document, subject for review. For now, please follow our blog to get updated with news and releases about Google Ads API.

Regards,
Google Logo
Ernie John Blanca Tacata
Google Ads API Team
 


ref:_00D1U1174p._5004Q2VOr8G:ref
Message has been deleted

Google Ads API Forum Advisor

unread,
Jan 25, 2022, 1:15:01 AM1/25/22
to dave....@tealium.com, lauren...@google.com, adwor...@googlegroups.com

Hello Dave,

Thanks for getting back to us.

I'm afraid that our team can't check on your request given your request ID. Can you share with us the complete API logs (request and response with request-id) instead?

Please send the requested details via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Regards,

Google Logo
Mark Kevin Albios
Google Ads API Team
 

 

ref:_00D1U1174p._5004Q2VOr8G:ref

Google Ads API Forum Advisor

unread,
Jan 30, 2022, 8:28:48 PM1/30/22
to adwor...@googlegroups.com, dave....@tealium.com, lauren...@google.com
Hi All,

I received an update from the team and let me share it to you.

Please apply the changes on this blog post on uploading customers to customer list / segments. Our team is already working to reflect this update in Google Ads API document as well and it will be updated soon.

Regards,
Google Logo
Ernie John Blanca Tacata
Google Ads API Team
 


ref:_00D1U1174p._5004Q2VOr8G:ref
Reply all
Reply to author
Forward
Message has been deleted
0 new messages