OfflineUserDataJob populating takes a lot of tie for some Audiences

[Andrii Veretko]

Hi,

Sometimes I'm facing an issue with OfflineUserDataJob. From time to time it takes a lot of time to proceed. It doesn't happens everytime. There is OfflineDataJobs which I'm referring to:

• customers/3646965316/operations/CjRjdXN0b21lcnMvMzY0Njk2NTMxNi9vZmZsaW5lVXNlckRhdGFKb2JzLzMxNTU5Mjc1NDU0EA0= 
• customers/3646965316/operations/CjRjdXN0b21lcnMvMzY0Njk2NTMxNi9vZmZsaW5lVXNlckRhdGFKb2JzLzMxNTU3NTgyMDMzEA0=

These two were populating ~19 hours. Can it be related to account settings or some rate limits?
Is there a way to increase populating speed on my side?
Do you have a chance to check what happened to these OfflineUserDataJobs?

[Google Ads API Forum Advisor]

Hi, 

Thank you for reaching out to Google Ads API Forum.

Moving forward with your concern, can you provide us more context on what you mean by “were populating ~19 hours” ? Additionally, in order for us to investigate further, can you provide us with the complete API logs (request and response with request-id and request header) generated on your end? This is so we can check on our end as well and investigate further. 

For the client libraries, logging can be enabled by navigating to the Client libraries > Your client library (ex Java) > Logging documentation, which you can access from this link (https://developers.google.com/google-ads/api/docs/client-libs). You can provide it via the Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Reference links included in this email:

• request: https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#request
• response: https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#response
• request-id: https://developers.google.com/google-ads/api/docs/concepts/call-structure?hl=en#request-id
• request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers

 

This message is in relation to case "ref:_00D1U1174p._5004Q2mWOI0:ref"

Thanks,
 

Google Ads API Team

[Andrii Veretko]

"Populating" means the process on Google Ads side since client does OfflineUserDataJob:run API call.

> request and response with request-id and request header

Request: POST https://googleads.googleapis.com/v13/customers/3646965316/offlineUserDataJobs/31559275454:run
Body: { "validateOnly": false }
Headers: { developer-token: <hidden>, login-customer-id: <hidden> }

I provided OfflineUserDataJob ID, you can use it to check an exact Job. 

[Google Ads API Forum Advisor]

Hi, 

Thanks for getting back to us.

I can see currently the OfflineUserDataJob current status is already SUCCESS. Can you confirm if it is also showing the same on your end?
 

[Andrii Veretko]

Yes, it is SUCCESS. But it wasn't an original question. I need to know why it takes so much time and can I somehow decrease an execution time?

[Google Ads API Forum Advisor]

Hello Andrii,

Thank you for getting back to us.

Please note that, since it can take up to 24 hours for a list to be populated with members, you might see an In Progress status in the Google Ads UI if you upload to an audience list more frequently than once every 12 hours. Please refer here(https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-match/get-started#compare) for more information. 

[Andrii Veretko]

Thank you for an update