Hey Vamshi, How you're sending create and remove operations for OfflineUserDataJobs?
On Wednesday, February 16, 2022 at 8:51:06 PM UTC+5:30 vams...@sojern.com wrote: > Hi, > > Thank you for the response. Could you please clarify the follow-up > questions? > > *1. The Google Ads documentation says we might get an error if we try to > execute two Jobs at the same time for a particular audience. Would there be > a problem if we create a Job for the same audience that has a Job, add > users to that Job, and execute it only after the previous Job has finished? > Would the above approach work?* > > > > >> Yes, you would need to avoid executing two Jobs at the same time for a > particular audience. If you need to submit more than 100,000 identifiers > for a job, you need to send multiple requests with the same job > *resource_name* > <https://developers.google.com/google-ads/api/reference/rpc/v10/AddOfflineUserDataJobOperationsRequest#resource_name>. > > This will help you to send millions of userlist for the same > OfflineUserDataJob. > > >>>> I understood that we can create multiple jobs for the same resource. > But my question was something different. What happens if there is a job > already running (i.e it is in RUNNING status) for an audience and I create > a new job for the same audience, add operations > <https://developers.google.com/google-ads/api/rest/reference/rest/v8/customers.offlineUserDataJobs/addOperations> > > to the new job and only execute it after the previous job has finished. > Will this approach work seamlessly or would it cause any issues? > > > > * 2. For how long can a Job be in "PENDING > <https://developers.google.com/google-ads/api/rest/reference/rest/v9/customers.offlineUserDataJobs#offlineuserdatajobstatus>" > > state? I.e Can we create a Job, keep adding User Identifiers, and only run > it after a few hours? (for example after 24h or 48h)* > > >> PENDING status of an offline user data job is when the job has been > successfully created and is pending for uploading. In order to start > uploading and processing data further, you would need to run > RunOfflineUserDataJob(). > > >>>> For our use case, we want to add operations for the same job at > regular intervals and run the job once when we have a large number of > operations. So, we might execute it once every 24hrs or 48hrs. So, can the > job be kept in the *PENDING* state for as long as we want? > Thanks, > Vamshi > On Wednesday, February 16, 2022 at 3:46:14 PM UTC+5:30 adsapi wrote: > >> Hi Vamshi, >> >> Thanks for reaching out to the Google Ads API Support. >> >> Kindly see below responses to your queries: >> >> *The Google Ads documentation says we might get an error if we try to >> execute two Jobs at the same time for a particular audience. Would there be >> a problem if we create a Job for the same audience that has a Job, add >> users to that Job, and execute it only after the previous Job has >> finished?Would the above approach work?* >> >> >> Yes, you would need to avoid executing two Jobs at the same time for a >> particular audience. If you need to submit more than 100,000 identifiers >> for a job, you need to send multiple requests with the same job >> *resource_name* >> <https://developers.google.com/google-ads/api/reference/rpc/v10/AddOfflineUserDataJobOperationsRequest#resource_name>. >> >> This will help you to send millions of userlist for the same >> OfflineUserDataJob. >> >> >> >> *2. For how long can a Job be in "**PENDING* >> <https://developers.google.com/google-ads/api/rest/reference/rest/v9/customers.offlineUserDataJobs#offlineuserdatajobstatus>*" >> >> state? I.e Can we create a Job, keep adding User Identifiers, and only run >> it after a few hours? (for example after 24h or 48h)* >> >> >> PENDING status of an offline user data job is when the job has been >> successfully created and is pending for uploading. In order to start >> uploading and processing data further, you would need to run >> RunOfflineUserDataJob(). >> >> >> >> *3. The Google Ads documentation says we can add a maximum of 100K User >> Identifiers per add operation, but is there a total limit of User >> Identifiers per Job?* >> >> >> Note that the maximum number of user identifiers allowed per request >> is 100,000 and per operation is 20. >> >> Let us know if you have any further questions. >> >> Regards, >> [image: Google Logo] >> Yasar >> Google Ads API Team >> >> >> ref:_00D1U1174p._5004Q2Wvu9x: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/f0892ec3-6580-4c73-89d3-e0fbb9697fa7n%40googlegroups.com.
