Hi Thank you for your response. Regarding your response to the first question. The statement in the referenced article is in the context where remove_all is set to true. That means you want to remove all customers from the audience. But my question is specific to a scenario, where we are removing only a couple of customers from the audience. Consider below the sequence of events: 1. Make an API call at 7:00 AM to remove 10 customers from the audience list which is having 10K customers in it. 2. Make another API call at 7:05 AM to add those 10 customers back to the same audience list
Can u please confirm whether these jobs will be executed in a sequential manner one after another or there is no guarantee of the execution order? I have attached a file where its visible from Google Ads UI that jobs are not executed in a sequential manner. Regarding the 2nd question. As per the referenced article, it seems that I can hit with CONCURRENT_MODIFICATION exception. On Monday, January 24, 2022 at 1:52:12 PM UTC+5:30 adsapi wrote: > Hi, > > Thank you for posting your concern. Allow me to provide support here. > > For your 1st question, I can confirm that the order of the execution would > also be same based on the statement below that discussed here > <https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-match#customer_match_considerations> > : > *When you run your job, the Google Ads API will first mark all current > members of the list for removal, and then apply the create operations.* > > As for the second question, I don't see any issues here as you followed > the below statement which is also described in the link I provided earlier: > *Avoid simultaneously running multiple OfflineUserDataJob > <https://developers.google.com/google-ads/api/reference/rpc/v9/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/v9/CustomerMatchUserListMetadata> > point > to the same resource name). Doing so can result in > a CONCURRENT_MODIFICATION > <https://developers.google.com/google-ads/api/reference/rpc/v9/DatabaseErrorEnum.DatabaseError#concurrent_modification> > error > since multiple jobs are not permitted to operate on the same list at the > same time. This error can also occur if attempting to simultaneously modify > a list through the Google Ads UI and the Google Ads API. Note that this > does not apply to adding operations > <https://developers.google.com/google-ads/api/reference/rpc/v9/AddOfflineUserDataJobOperationsRequest> > to > an existing job, which can be done at any time before the job is started.* > > Let me know if you have further questions. > > Regards, > [image: Google Logo] > Ernie John Blanca Tacata > Google Ads API Team > > > ref:_00D1U1174p._5004Q2VOF6X:ref > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/261e716b-cb22-417b-baa2-12820745b3ban%40googlegroups.com.
