Auto-Migration of Feed-Based Extensions

97 views
Skip to first unread message

Malcolm Taylor

unread,
Feb 22, 2022, 11:41:52 AM2/22/22
to Google Ads API and AdWords API Forum
Hey Team,

I have a few question around the migration from feed-based to asset based extensions, specifically around call extensions going to asset-based extensions. I have seen a couple docs that seem to be unclear as to timings.

This doc "https://ads-developers.googleblog.com/2021/05/feed-based-extensions-sunset-in-google.html" states that feed-based extensions for callout, sitelink, structured snippet, promotion, and leadform will be sunset on that date and the the auto migration of app, call, hotel callout, image, and price will happen on February 15th.

Where as this doc "https://developers.google.com/google-ads/api/docs/extensions/assets/migrating-extensions#migration_schedule" states that the auto migration of app, call, hotel callout, and price will happen on April 8th. Are you all able to clarify these docs timings?

1) Are you all able to tell me exactly what extensions types were to be migrated on the 15th of February?

2) I see call assets are available in v9, if the auto-migration for those has not taken place yet are we still able to create them? I am trying to create call assets with the Asset Service function MutateAssets in golang.  This doc "https://developers.google.com/google-ads/api/reference/rpc/v9/AssetService?hl=en#mutateassets" states that "Asset types can be created with AssetService are YoutubeVideoAsset, MediaBundleAsset and ImageAsset. TextAsset should be created with Ad inline." Is that all I can create with this service. If so what service should i be using to create a call asset and is that service able to be used now?

3) Is April 8th a true date of auto migrations for call extensions to call asset based extensions?

4) I have been trying to use the Asset service to create a call asset using the MutateAssets function and getting an rpc response back stating "rpc error: code = InvalidArgument desc = Request contains an invalid argument." If this is the right service to use to create a call asset do you know how i could get to the root of what the issue is or a more descriptive response. I've been setting the validate only field to true just so that i can make sure my request is valid but that error is the only response I get back. Again if this service is not the correct service to create call assets then I will refer back to question 2.

Google Ads API Forum Advisor

unread,
Feb 23, 2022, 3:13:57 AM2/23/22
to mata...@redventures.com, adwor...@googlegroups.com
Hi Malcolm,

Thank you for your questions. You may refer below for my responses :


1) Are you all able to tell me exactly what extensions types were to be migrated on the 15th of February?

We do not have an exact date for when migration of specific extensions would be completed. I would recommend that you refer to this blog post, for updates on the asset extensions migration. You can also refer to this guide, to check whether your account has been migrated.


2) I see call assets are available in v9, if the auto-migration for those has not taken place yet are we still able to create them? I am trying to create call assets with the Asset Service function MutateAssets in golang.  This doc "https://developers.google.com/google-ads/api/reference/rpc/v9/AssetService?hl=en#mutateassets" states that "Asset types can be created with AssetService are YoutubeVideoAsset, MediaBundleAsset and ImageAsset. TextAsset should be created with Ad inline." Is that all I can create with this service. If so what service should i be using to create a call asset and is that service able to be used now?

As per the blog I provided above, Call assets extension sub type's auto migration is due to start on April 8, 2022, and that developers can start migrating on 25 January 2022. That said, you may opt to migrate manually as well, by referring to this guide. In the v10 of the AssetService, the call_asset is supported.


3) Is April 8th a true date of auto migrations for call extensions to call asset based extensions?

As per the recent update from the blog I provided, April 8, 2022 should be the start of the auto migration of call asset extensions.


4) I have been trying to use the Asset service to create a call asset using the MutateAssets function and getting an rpc response back stating "rpc error: code = InvalidArgument desc = Request contains an invalid argument." If this is the right service to use to create a call asset do you know how i could get to the root of what the issue is or a more descriptive response. I've been setting the validate only field to true just so that i can make sure my request is valid but that error is the only response I get back. Again if this service is not the correct service to create call assets then I will refer back to question 2.

Could you share your complete request and response logs, and request-id, so our team can take a look at the error you are encountering? You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Best regards,

Google Logo
Peter Laurence
Google Ads API Team
 


ref:_00D1U1174p._5004Q2Wy0H1:ref

Malcolm Taylor

unread,
Feb 23, 2022, 10:58:31 AM2/23/22
to Google Ads API and AdWords API Forum
Thanks for you response. One follow-up question.

In the response to question #2 you stated that AssetService and the call asset is supported in v10 but in the question I stated I was in v9. The docs look the same for v9 and v10 for those. Are creating call assets not supported in v9 of AssetService and only in v10?

Google Ads API Forum Advisor

unread,
Feb 24, 2022, 1:54:30 AM2/24/22
to mata...@redventures.com, adwor...@googlegroups.com
Hi Malcolm,

Thank you for the reply. I am also a member of the Google Ads API team and let me provide support to your concern.

Upon trying the 2 versions for creating call assets, the API requests are both successful. With this, creating of call asset using v9 and v10 is possible; however, we recommend using the v10 as it is the latest API version.

Regards,
Google Logo
Ernie John
Google Ads API Team
 


ref:_00D1U1174p._5004Q2Wy0H1:ref
Reply all
Reply to author
Forward
0 new messages