Processing Time for OfflineUserDataJob

Hi team, We are using OfflineUserDataJob to upload user data. For different type, the processing time seems quite different, i.e. when the type is CONTACT_INFO, the status is updated to SUCCESS very quickly, for CRM_ID, a bit slower, but still less than 24 hours(google ads doc claimed it takes

Re: Data Format for AdwordsUserListService

tch rate? On Wednesday, June 17, 2020 at 9:12:56 AM UTC+8, Qian Huang wrote: > > Hi Xiaoming, > > Thanks for reply, about those fields which need not necessarily to be > hashed(especially `userId`), does it mean I can send hashed/unhashed data? > Or it is mandatory these data

Re: Data Format for AdwordsUserListService

Hi Xiaoming, Thanks for reply, about those fields which need not necessarily to be hashed(especially `userId`), does it mean I can send hashed/unhashed data? Or it is mandatory these data need to be unhashed? Best Regards, Qian On Wednesday, June 17, 2020 at 2:22:02 AM UTC+8,

Data Format for AdwordsUserListService

Hi team, We are uploading user list, and from https://developers.google.com/adwords/api/docs/reference/v201809/AdwordsUserListService.Member, there are several types are supported. I want to confirm with you which field could be hashed and which field must be unhashed. Best Regards, --

Re: Audience statistic api

I think the size field you mention is an estimated value, is it possible to get the accurate number? On Friday, May 22, 2020 at 2:33:28 AM UTC+8, adsapiforumadvisor wrote: > > Hi Qian, > > Thank you for reaching out. If you are referring to getting information > about UserLists >

Audience statistic api

Hi team, Is there any api to get some statistic of audience? e.g. size, match rate... Best Regards, Qian -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received

Re: DatabaseError.CONCURRENT_MODIFICATION error

Hi Nikisha, For one user list, we will add millions of users, so currently we chunk them into several requests, each request will contain 1000 user mutation, then we send these requests concurrently. If the concurrent modification error is happend on user list level, it means we can't send

Re: DatabaseError.CONCURRENT_MODIFICATION error

Hi Nikisha, I checked change history, looks like only one script is sending request. However, the history are quite general, it only says: "Remarketing list changed", "Members are uploaded to add to this list". Could you tell more details about that for this mutate member api, what's the

DatabaseError.CONCURRENT_MODIFICATION error

Hi, when I send mutateMembers requests, there are a lots DatabaseError.CONCURRENT_MODIFICATION error: soap:Client [DatabaseError.CONCURRENT_MODIFICATION @ com.google.ads.api.services.campaignmgmt.common.error.DatabaseError.init(Datab]