Flaky behavior in getting the LocationAsset Association with LocationSync AssetSet

[Ahmed Nasser Omran]

Hi Google Ads Team, 

Referring to this doc :

Location Assets  |  Google Ads API  |  Google for Developers

I'm trying to get the automatically created Asset Associated with the LocationSync AssetSet as mentioned here 

sometimes I can get it but most of the time I can't, it has flaky behavior. 

my question is that is a normal behavior? when does the automatically generated asset is created? 

I'm using this example query to get the location asset linked to the locationSync AssetSet 

SELECT asset_set_asset.asset FROM asset_set_asset WHERE asset_set_asset.asset_set IN ('customers/xxxxxx/assetSets/xxxxxx')

I will appreciate your help on this.

Thanks, 

[Google Ads API Forum Advisor]

Hi Ahmed,

 

Thank you for reaching out to the Google Ads API Support Team.

 

Could you please provide the complete API logs (request and response with request-id and request header) generated on your end as well as the complete Google Ads UI screenshot of the information you're aiming to retrieve? This is so we can further check the behaviour you've observed and investigate this further:

• 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

 

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. For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.

 

You may send the requested information via the Reply privately to author option. Note that you may need to join the Google Group for you to use this option. If this option is not available on your end still, you may send the details directly to our alias `googleadsa...@google.com` instead.

 

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

Thanks,
 

Google Ads API Team

[Ahmed Nasser Omran]

Please can you ask the dev team to tell us what is the delay between creating LocationSync AssetSet and automatically the corresponding LocationAsset ?

Thanks,
Ahmed

[Google Ads API Forum Advisor]

Hi Ahmed,

Thanks for getting back to us.

Please can you ask the dev team to tell us what is the delay between creating LocationSync AssetSet and automatically the corresponding LocationAsset?

>> I can see that you are trying to access Location Assets. However, as per this blog post posted last July 6 regarding Image and Location Auto-migration August 2023, beginning on August 2, 2023, auto-migration of image and location extensions to assets will be started.

Please note the migrations occur at an account level. During the migration of an account, which will take several minutes, you won’t be able to execute any image or location mutations of either extensions or assets. When the migration is complete, you will have access to the assets. That said, during this time of migration, this may be the reason for the flaky behavior you noticed on your end.