OfflineUserDataJobs Questions

[Vamshi TG]

Hi,

We are trying to upload users to User Lists using the OfflineUserDataJobs REST endpoint. Need help with the below questions we have.

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?

2. For how long can a Job be in "PENDING" 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)

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?

Thanks,

Vamshi

[Google Ads API Forum Advisor]

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. This will help you to send millions of userlist for the same OfflineUserDataJob.

2. For how long can a Job be in "PENDING" 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,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2Wvu9x:ref

[Vamshi TG]

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. 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 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" 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

[Subhranshu Mohanty]

Hey Vamshi, How you're sending create and remove operations for OfflineUserDataJobs?

[Google Ads API Forum Advisor]

Hi Mohanty,

Thank you for reaching out to the Google Ads API support team.

With regards to your concern, you may refer to this guide to create and remove operations for OfflineUserDataJobs. Let me know if you have any question.

Thanks,

Nirmita Google Ads API Team

ref:_00D1U1174p._5004Q2Wvu9x:ref

[Vamshi TG]

Hi,

It appears that my follow-up questions got lost in the thread. I have added them again below, could you please clarify them?

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. 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 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" 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

[Google Ads API Forum Advisor]

Hi Vamshi,

Thank you for the reply. I am also a member of the Google Ads API team and let me provide support to your concern.

For #1, according to this document, it says that you can add operations to an existing job which can be done at any time but before the job is started.

Moving forward to this question "So, can the job be kept in the PENDING state for as long as we want?", I can confirm that your understanding here is correct.

Let me know if you have further questions.

Regards,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2Wvu9x:ref