Hello team, Can you please let us know if you have update regarding Kevin's questions? Thank you.
On Thursday, March 2, 2023 at 11:23:57 AM UTC-8 Kevin wrote: > One more thing - it looks like to get the location data, I need to talk to > the Places API which is a paid service. > Previously we could get this data for free from the Ads API - any way we > can continue to get this data the same way? > > On Thursday, March 2, 2023 at 10:51:58 AM UTC-8 Kevin wrote: > >> Hi Bob, >> >> Thanks for the response - it helps! >> From the previous posts, I was under the impression that asset-based >> Image and Location extensions are *not supported* because of this quote: >> "I am afraid that asset based Image / location extensions are *not >> supported*." >> From your reply, it looks like they *are supported* and the way they are >> supported can be found in these two links: >> >> https://developers.google.com/google-ads/api/docs/location-extensions/location-assets >> https://developers.google.com/google-ads/api/samples/upload-image-asset >> >> For asset-based location extensions, it looks like it's preferred to use >> a location sync asset set, which automatically generates the corresponding >> assets. >> It looks like it is preferred to deal only in asset sets: >> "First, create a location sync asset set and attach it to the customer. >> Then, if you need to select a subset of the location assets in the asset >> set for a campaign or ad group, create a location group asset set and >> attach it to the campaign or ad group." >> >> It is not clear to me whether you have the option to directly generate >> and associate single assets. >> The asset set association >> <https://developers.google.com/google-ads/api/fields/v13/campaign_asset_set> >> does not specify type and is explained in the document. >> The asset association >> <https://developers.google.com/google-ads/api/fields/v13/asset_group_asset#asset_group_asset.field_type> >> does >> have a specific type, but there does not look like there is one that >> corresponds to a location. >> >> For asset-based image extensions, it looks like there are no asset sets >> for them based on the allowed types in the asset set: >> >> https://developers.google.com/google-ads/api/reference/rpc/v13/AssetSetTypeEnum.AssetSetType >> so I should create individual assets for each image extension and >> associate it to the customer/campaign/adgroup with an association >> (customer_asset/campaign_asset/ad_group_asset). >> >> *Question* - For image extensions that are migrated to asset-based >> extensions, what is the asset association type? >> The list here in the documentation has something clearly labeled for >> other extension types: >> >> https://developers.google.com/google-ads/api/reference/rpc/v13/AssetFieldTypeEnum.AssetFieldType >> For example: "The asset is linked for use as a Sitelink extension." >> I venture to guess that the only one that makes sense is "AD_IMAGE", but >> I would like confirmation since it isn't in the document that Bob sent and >> it says: >> "The asset is linked for use to select an ad image." rather than anything >> about extensions. >> >> For what it's worth, I think it'd be helpful if more documentation was >> linked in the blog post announcing the auto-migration. >> I think guides and examples on how to migrate each of the extension types >> manually and retrieve the data back would be helpful. >> >> Thanks, >> Kevin >> >> >> On Wednesday, March 1, 2023 at 5:26:26 PM UTC-8 Google Ads API Forum >> Advisor wrote: >> >>> I'm attempting to understand your concerns from the multiple >>> interactions. So that we are clear on terminology, extension refers to the >>> feed based model and assets refers to the new model. >>> >>> Starting 3 April 2023, accounts will be eligible to be automigrated for >>> image and location extensions. Once an account is selected for >>> auto-migration, the account is prevented from mutating extension during >>> which time the extensions continue to serve, the automigration takes place >>> (a couple of minutes), assets start to serve and extension mutation is >>> permanently disallowed on this account. >>> >>> Currently, you can create location and image assets in test accounts. >>> >>> >>> https://developers.google.com/google-ads/api/docs/location-extensions/location-assets >>> https://developers.google.com/google-ads/api/samples/upload-image-asset >>> >>> As of 3 April you will be able to do this in production accounts. >>> >>> As to your question as to why we decided to do it this way: >>> >>> Location assets are are extremely complex to migrate and there is no >>> good user path for this. We can do it efficiently on the back end and >>> guarantee that the locations are efficiently and safely migrated. Image >>> assets are more numerous that locations assets, so we decided to >>> auto-migrate them also. Because the image assets are a new entity there is >>> no mapping to the extension. If you want to keep a link then you need to >>> create the map yourself. >>> >>> Reporting for image and location assets are just like any other asset. >>> You can see the list of reports with metrics at >>> https://developers.google.com/google-ads/api/fields/v13/metrics This >>> asset data will be available as soon as your account is migrated and the >>> extension data will be available until sometime in 2024. >>> >>> It is possible to move the images yourself by creating an image asset, >>> linking it to campaign or adgroup via CampaignAsset or AdGroupAsset and >>> then remove the original feeditem link so that the image asset will be used >>> for serving instead of feeditem extension. We can't provide support for >>> this if you decide to do it yourself. >>> >>> We strongly recommend that you use the automigration. blog post: >>> https://ads-developers.googleblog.com/2023/02/image-and-location-auto-migrations-in.html >>> >>> Image and location automigrations will run in parallel but are not >>> synchronized. So, an account can be migrated for each type at different >>> times. The order of accounts chosen is non-deterministic, so even though >>> the migration starts on 3 April 2023, you account could be migrated at any >>> time between then and 15 September 2023. Check the blog post to see how to >>> tell if your account has been migrated. >>> >>> Once the image and location automigration is complete, extensions will >>> not longer be able to be mutated and all of the Google Ads API will be >>> asset based. >>> >>> -- Bob Hancock >>> >>> >>> ref:_00D1U1174p._5004Q2j1cSB:ref >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2206824c-15de-4877-8703-decba426620en%40googlegroups.com.
