Re: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi, Our Customer Match considerations guidance states that the operations collection for each AddOfflineUserDataJobOperationsRequest can contain at most 100,000 identifiers across all of the UserData objects in the operations. If you need to submit more than 100,000 identifiers for a job, send

Re: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi, Thank you for the response. This info helps but sorry I am still looking for a response to my last query where we submitted two asynchronous jobs one with remove_all as first operation to remove users from an audience and immediately fire a second asynchronous job to add a list of users to

Re: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi, I have tried to explain our use case below. The reason to create separate async jobs is due to the limit on UserIdentifiers in a single API call. [image: async jobs.jpg] On Monday, February 7, 2022 at 6:56:02 AM UTC+5:30 adsapi wrote: > Hi Paid Media Team, > > Thanks for getting back to

Re: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi Paid Media Team, Thanks for getting back to us. Note that when a remove_all operation is included, it must be the first operation in a job. If not, then running the job will return an INVALID_OPERATION_ORDER error. If you encounter API errors, you may provide us with the complete request

Re: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi, In simple our use case is to remove all users and add new set of users. As we can't fit all adds in one job due to limitation of 10 identifies, we need to split add jobs. So let us consider a simple scenario where we need to achieve this in two jobs. The first asynchronous job will be

RE: Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi there, I am interpreting what you are asking as you have no way of designating the first AddOfflineUserDataJobOperationsRequest to be the one that has it's first operation set to remove_all. If that's the case you will have multiple remove_all operations in the job. Note that when a

Does AddOfflineUserDataJobOperationsRequest ensure the request with removeAll operation is executed first?

Hi, As per the Google Ads API documentation - *https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-match *it says *To completely replace the members of a user list