Asset-Based Extension Migration : Deletion and Post-Migration Correlation

[Kevin]

Hi,

I have two questions regarding the Asset-Based Extension Migration:

Migrate to Asset-based Extensions  |  Google Ads API  |  Google Developers

First, in the Migration Schedule, it is mentioned that:

"Reporting for Feed-based extensions will be available until August 2022."

Does that mean that the Ad Extension data will still be available from the Feed-Base services until August 2022 or just things like performance statistics?

I am not sure because the Migration Procedure says that Feed-based extensions should be removed.

Second, would it be possible to query the API for a mapping between the old Feed Items and the new Assets? I know that the Migration Details says:

"We recommend performing the migration process yourself through the Google Ads API as outlined in this guide, as there will be no connection between Assets created during the automatic migration and the original Feeds."

However, this is a bit of a nightmare for anyone managing or analyzing data on Customers behalf.

Thanks,

Kevin

[Google Ads API Forum Advisor]

Hi Kevin,

Thanks for reaching out. Regarding your first inquiry, the extended reporting would include both the entity's data and performance statistics, as it would normally for an item with status, REMOVED.

Regarding a connection between the old feed item and new asset, the API currently does not support any such link. However, can you please provide us with a more detailed description of how you would prefer the implementation of this link? I can make a feature request on your behalf with this description.

Thanks,
Matt
Google Ads API Team

Matt Google Ads API Team

 

ref:_00D1U1174p._5004Q2OStYl:ref

[Kevin]

Hi Matt,

Thanks for helping out here!

For the first inquiry, what you've said makes sense but I just want to double check I understand correctly:

The data will be available using the service but it will have the "REMOVED" status.

As such, there will be no way to tell the difference between

    Feed Items for Extensions that had previously been "REMOVED" and are not serving and

    Feed Items for Extensions that were migrated and are "REMOVED", but still serving.

The only way to tell is to conjure a mapping between the migrated Feed Items and new, "ACTIVE" Assets.

Is that correct?

This actually leads well into the second inquiry where we were discussing the possibility of querying for

Feed Item -> Asset links from the migration.

My thoughts about the implementation are as follows:

1. We only care about the link when there are Asset-based Extensions (otherwise there is no link).

2. When we have Asset-based Extensions, we want to know which Feed-based Extensions they correspond to.

3. So we want a Service where we provide a list of Asset Ids and are returned GoogleAdsRows, each with an

Asset Id and a Feed Item Id (other details can already be queried from existing services).

As I understand it, this information should be enough to address my concerns by itself.

Let me know if there's anything else I can do to help!

Thanks,

Kevin

[Google Ads API Forum Advisor]

Hi Kevin,

Thank you for providing further details to your concern. I work with Matt and let me provide support to your concern.

For the concern that you explained, I would suggest to no longer monitor the link between feed-based extension historical data to migrated asset-based extension as these well be different entities and statistics of the feed based extension should stay with the feed based extensions, while the asset based ones will generate their own statistics moving forward. Also, historical feeds reports will eventually be deprecated and no longer available to be retrieved as discussed here.

Moving on to your follow up concern, and as discussed in this section for manual migration, you can retrieve the attributes of those feed based extensions and then apply those when creating your asset extensions, and manually include previous IDs (ex. setName("Migrated from feed item " + extensionFeedItem.getId())) as in the example, if you still wish to map your feed based to asset based extensions.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2OStYl:ref