Extensions migration: Preserving performance data

[Ellen Skipper]

Hi there,

I'm investigating the extensions migration, which affects our service as we have previously been using Feed-based Sitelinks. I have two questions about this.

Firstly, we received an email telling us to update the implementation by January 10th. Does this mean that we are scheduled for automatic migration of our sitelinks to the Asset system on that date, please?

Secondly, our client is concerned about preserving the performance data (ie: clicks, impressions, cpc, cost, conversions, conversion rate, ctr, etc) of the existing sitelinks. Would this data be preserved if:

a) We allowed the sitelinks to be migrated automatically 

b) We manually migrated the sitelinks before this date (as described here)

Many thanks in advance for your help.

[Ellen Skipper]

(NB when I say "preserving" the data, I mean that the client wants the performance data up until the point of the migration to be attached to the new Asset based object; and for new performance data from then on to be added to the existing data)

[Google Ads API Forum Advisor]

Hi Ellen,

Thank you for reaching out. You may refer below for my responses to the items you sent over :

Firstly, we received an email telling us to update the implementation by January 10th. Does this mean that we are scheduled for automatic migration of our sitelinks to the Asset system on that date, please?

Our team is currently not aware of a January 10th schedule as the dates mentioned in this blog post are the only ones currently visible to our API support team. That being said, could you share details of the said email to our team and send it over via the Reply privately to author option?

Secondly, our client is concerned about preserving the performance data (ie: clicks, impressions, cpc, cost, conversions, conversion rate, ctr, etc) of the existing sitelinks. Would this data be preserved if:
a) We allowed the sitelinks to be migrated automatically 
b) We manually migrated the sitelinks before this date (as described here)

(NB when I say "preserving" the data, I mean that the client wants the performance data up until the point of the migration to be attached to the new Asset based object; and for new performance data from then on to be added to the existing data)

Whether it is the a or b option, your feed based extensions historical data should still be available until August 2022 as mentioned here. You can then use the asset_field_type_view report mentioned in the same section of the guide, for tracking performances of asset extensions moving forward.

Best regards,

Peter Laurence Napa Oliquino Google Ads API Team

ref:_00D1U1174p._5004Q2SacTZ:ref

[Ellen Skipper]

Thanks for your help. So to confirm, there is no way to have the historical data from the feed based extensions appear on the new asset extensions?

[Google Ads API Forum Advisor]

Hi Ellen,

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

If what you want to clarify is if the historical data from the feed based extensions will no longer be available in August 2022 onwards, then the answer would be yes. Also its feed based historical data would no longer be available in the new asset based extensions report.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2SacTZ:ref

[Ellen Skipper]

Great, thank you very much. I think that answers everything we needed to know.