Hi,
Thank you for your reply.
Currently, 20 user_identifiers is the limit that you can include in a single
UserData object. This can then be passed to a single
OfflineUserDataJobOperation. As per the
guide I earlier provided, a single
AddOfflineUserDataJobOperationsRequest can contain at most 100,000 identifiers across all of the UserData objects in the operations.
That being said, you may refer to my responses to the below items :
1. So my question is what's the upper limit of the job?
2. Will it be able to handle the several Billions of user identifiers and operations in a single job?
For the above items and as mentioned, a single
AddOfflineUserDataJobOperationsRequest can contain at most 100,000 identifiers across all of the UserData objects in the operations. Also, as you have already mentioned, you can indeed send multiple requests with the same job resource name, if you need to submit more than 100,000 identifiers in a single job.
The number of requests that you can then perform using your developer token would then depend on the
access level that has been granted. You may refer to this
guide, and to this
section for more information on the limits.
3. And how will it impact the completion time of the job?
4. Will it be able to complete within the SLA of 24 hours?
The period for the jobs to complete would depend on the size of the request. We currently do not have specific figures as to how long. However, and also from the
guide I earlier provided, it takes 6 to 12 hours for a list to be populated with members, so you'll most likely
see an "In Progress" status (on the Google Ads UI) if you upload to an audience list more frequently than once every 12 hours.
In addition, you may also refer to this Product
article for any issues you may encounter with size, and that Customer Match uploads can also take up to 48 hours to process.