Running OfflineUserDataJob

[Ilya Karpov]

Hi,

I'm looking forward to implement user list upload for Customer Match and was investigating provided example and very similar one for uploading sales transactions, both use offlineUserDataJobServiceClient. I see that in the example for customer match there is no offlineUserDataJobServiceClient.runOfflineUserDataJobAsync(offlineUserDataJobResourceName) call. 

Is it ok not to call runOfflineUserDataJobAsync for customer match?

What is the difference between calling and not calling runOfflineUserDataJob method?

[Google Ads API Forum Advisor Prod]

Hi Ilya,

Thank you for reaching out. In the code example uploading the store sales data, the asynchronous API requests were issued by calling offlineUserDataJobServiceClient.runOfflineUserDataJobAsync(offlineUserDataJobResourceName) to improve the performance and responsiveness as the data set might be larger in this case. However, in the code example uploading the customer match data, the synchronous API calls were issued as typically the customer info is smaller in size.

Thanks and regards,
Xiaoming, Google Ads API Team
 

Xiaoming Google Ads API Team

ref:_00D1U1174p._5004Q2B1PgQ:ref

[Ilya Karpov]

Thanks for reply!

Am I right that uploaded dataset (in both examples) will be processed asynchronously on the Google Ads backends side (and I can poll for job status by issuing a search query)?

вторник, 19 января 2021 г. в 21:19:14 UTC+3, adsapiforumadvisor:

[Google Ads API Forum Advisor Prod]

Hi Ilya,

Thank you for reaching out. My assumption is that the uploading of the store sales data is processed asynchronously but the uploading of the customer match data isn’t as the store sales example explicitly uses the runOfflineUserDataJobAsync method. Yes, you could query the offline_user_data_job.status from offline_user_data_job resource to check the job status.

Thanks and regards,
Xiaoming, Google Ads API Team