We previously announced that we’re migrating Feeds to Assets. We’ve started auto-migrating accounts. If you’re still using legacy Feeds, your API calls will start to fail. Please migrate to Assets as soon as possible.
The following table shows the current status and key dates for the automatic migration.
Feed Type | Subtype | Status | Auto Migration Date |
---|---|---|---|
Extensions | Promotion | AUTO MIGRATION IN PROGRESS | October 20, 2021* |
Extensions | Callout Sitelink Structured Snippet | AUTO MIGRATION IN PROGRESS | October 20, 2021* |
Extensions | App Call Hotel Callout Price | DEPRECATED | February 15, 2022 |
Extensions | Image | Not ready to migrate until mid 2022 | September 2022 |
Dynamic Search Ads | Page feed | DEPRECATED | 27 April 2022 |
Dynamic Remarketing | Education | DEPRECATED | 27 April 2022 |
Dynamic Remarketing | Custom Flight Hotel Real estate Travel Location Job | Deprecation planned for April 2022 | 5 October 2022 |
I thought Image extensions were migrating in February 2022?
That was the original plan, however we have delayed the Image extensions migration until September 2022.
What do I need to do?
You need to support the new Asset types as soon as possible.
To trace migration between Feed IDs and Asset IDs you need to migrate these manually. There is no way to get this relationship through the auto-migration.
See the following migration guides for more detail: What happens after the automated migration?
Accounts that have been migrated will reject mutate calls for Feed-based entities. Reporting stats will be removed for the legacy Feed-based entities in the near future. Equivalent reporting data will be available for assets, as described in the preceding migration guides.
Can I opt-out of the auto-migration?
No. We offered an opt-out for the first batch of auto-migration, but this isn’t available for future migrations.
If you have any questions, please reach out to us on the forum.