Thanks for your reply. It doesn't answer my questions, so I'll try to restructure them
1. Based on your answer, I understand the usage of *remove_all *is the only way to achieve what we want (refresh of a user list). If that's not correct, please let me know 2. We want to understand what happens with an existing User List from the moment we start running an offline job containing remove_all + create operations on it. I assume the remove_all operation will run first, so the user list will be empty as soon as this operation completes. Then, the create operations will add the accounts to the list and match them. As we know, the full process can take many hours (days, too - based on our tests). *Our question is: * What is the impact of this on the processes that uses the data from this list? Will they find an empty or partially loaded user list while the job is executing? We want to asses the risks and implications, before moving on with this solution Thanks for the links for the documentation. We went through them many times, but we didn't find answers for the above questions. Thanks, Daniel On Wednesday, February 7, 2024 at 4:04:39 PM UTC+2 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > Please find the below responses for your queries: > > *1) Will the remove_all happen, list will be empty and then matched in > several hours? * > > Note that removeAll > <https://developers.google.com/google-ads/api/rest/reference/rest/v15/customers.offlineUserDataJobs/addOperations#OfflineUserDataJobOperation:~:text=after%20being%20uploaded.-,removeAll,-boolean> > > operation removes all previously provided data. This is only supported for > Customer Match. > > *2) Will the Ads processes consuming data from these list be impacted for > the full duration of the job execution?* > > Kindly note that the processing time for offline user data jobs can vary > depending on the size and complexity of the data, the availability of > system resources, and any unexpected errors. > > Also, avoid simultaneously running multiple OfflineUserDataJob > <https://developers.google.com/google-ads/api/reference/rpc/v15/OfflineUserDataJob> > > processes that modify the same user list (that is, multiple jobs whose > CustomerMatchUserListMetadata.user_list > <https://developers.google.com/google-ads/api/reference/rpc/v15/CustomerMatchUserListMetadata> > > point to the same resource name). You may refer to the Best practices > <https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-match/get-started#best-practices> > guide > when designing your Customer Match integration. Also, you may follow > Troubleshoot > customer list issues > <https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/troubleshoot> > which will > help you troubleshoot low match rates and common errors that might come up > in your Customer Match integration. Hope this helps. Let us know if you > have any further queries. > > 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/34bcb499-1f0c-4b98-b917-8a07a396a054n%40googlegroups.com.
