Sorry, what is the true here? *Also, note that remove_all operations are executed hourly, and could run for up to 24 hours"* *OR"**In the removeAll operation, there are two pipelines that run when a remove_all is requested: -- a pipeline that runs a PURGE operation, and another that handles the ADD/REMOVE operations. The first pipeline runs as a daily job and can take up to 72 hours to complete"*
If the last one is correct, a 72 hours remove_all job cannot work. Not only because of the extremely large duration, but it also means we will have an empty list for 3-4 days (purge operation + ADD operations together). Would make the list unusable ! That means we have to create 2 jobs for each list, one for add new users, another one to remove the users which must be removed from the list. For 10 lists, we'd have to create 20 jobs. Since these jobs also run for up to 24h each and we cannot put them in a Queue to run automatically once the first one finished.. we'll have to run the ADD in one day and the REMOVE in the next day. And have these lists refreshed weekly, probably. The orchestration complicates, anyway.. even if we leave 24h between them, we see these jobs taking more than officially documented. If that's the only solution, I'll need to go to the Business stakeholders and explain them the limitations of this Google product and see if we can use it for our use cases Please give me a feedback on my above statements *Thanks!*Daniel On Thursday, February 8, 2024 at 9:33:11 PM UTC+2 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for getting back to us. > > Kindly find answers below for your queries. > > 1. So, how should we design an *append and remove* process ? What is > the impact of this on the processes that use the data from this list? Will > they find an empty or partially loaded user list while the job is > executing? > > > - You would be required to use the removeAll > > <https://developers.google.com/google-ads/api/rest/reference/rest/v15/customers.offlineUserDataJobs/addOperations#OfflineUserDataJobOperation:~:text=after%20being%20uploaded.-,removeAll,-boolean> > > operation to remove all your previously provided data and then add the > latest data by utilizing the create > > <https://developers.google.com/google-ads/api/rest/reference/rest/v15/customers.offlineUserDataJobs/addOperations#OfflineUserDataJobOperation.FIELDS.create> > > operation. > - In the removeAll operation, there are two pipelines that run when a > remove_all is requested: -- a pipeline that runs a PURGE operation, and > another that handles the ADD/REMOVE operations. The first pipeline runs as > a daily job and can take up to 72 hours to complete. > - If the remove operation was called first, then the newly added > operations should be uploaded after the remove operation has been > completed. > - Kindly note that Don't mix, create, and remove operations within the > same OfflineUserDataJob > > <https://developers.google.com/google-ads/api/reference/rpc/v15/OfflineUserDataJob>. > > Doing so can result in a CONFLICTING_OPERATION > > <https://developers.google.com/google-ads/api/reference/rpc/v15/OfflineUserDataJobErrorEnum.OfflineUserDataJobError#conflicting_operation> > > error. > - Enable partial_failure in an AddOfflineUserDataJobOperationsRequest > > <https://developers.google.com/google-ads/api/reference/rpc/v15/AddOfflineUserDataJobOperationsRequest> > > so as to detect any problematic operations before running the job. > Operations are validated when uploaded to an OfflineUserDataJob > > <https://developers.google.com/google-ads/api/reference/rpc/v15/OfflineUserDataJob> > . > > If you want to create and remove operations at the same time, you have to > create 2 jobs separately and pass these 2 operations to > AddOfflineUserDataJobOperationsRequest > <https://developers.google.com/google-ads/api/reference/rpc/v15/AddOfflineUserDataJobOperationsRequest> > . > > It takes 6 to 48 hours for a list to be populated with members, so you'll > most likely see an "In Progress" status > <https://support.google.com/google-ads/answer/7474166> (on the Google Ads > UI) if you upload to an audience list more frequently than once every 12 > hours. > This message is in relation to case "ref:!00D1U01174p.!5004Q02rytff: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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/9d95c543-1259-4b44-97c4-2cca6ef0753an%40googlegroups.com.
