Shopify Google & YouTube app Merchant API migration checklist

Verified as of July 10, 2026

Google says the Merchant API replaces the Content API for Shopping as the main programmatic Merchant Center interface, and Google says Content API access continues only until August 18, 2026. Google also says Merchant API v1 is generally available.

Google and Shopify help docs say the Google & YouTube app syncs eligible Shopify products into Merchant Center. Google also says product IDs should stay stable because changing an ID overwrites the product and its history.

Third-party reports say some Shopify Google & YouTube app migrations or reinstalls have changed product IDs from market-coded formats like Shopify_US_12345_67890 to shopify_ZZ_12345_67890. Google and Shopify docs checked for this page do not currently confirm that every merchant must reinstall the app or that every product ID will be rewritten.

What changes on August 18

The deadline is about the API path that sends or manages Merchant Center data. After August 18, 2026, integrations still depending on the legacy Content API for Shopping need to be on Merchant API instead.

That does not automatically mean every Shopify merchant should change IDs, reinstall the Google & YouTube app, or rebuild feeds. The safer job is to confirm which data source owns your products, whether that source has already moved to Merchant API, and whether product IDs, feed labels, and campaign filters stayed stable.

Who should check this now

• Shopify stores using the Google & YouTube app to sync products into Merchant Center.
• Stores where Merchant Center Data sources still shows Content API, Shopify App API, Merchant API, or another API source and the ownership is unclear.
• Stores using Shopping or Performance Max filters tied to item ID, product ID, item group ID, custom label, country, market, or feed label.
• Stores using supplemental feeds, feed rules, promotion rules, or attribute rules that join by product ID or feed label.
• Stores where conversion tracking, remarketing, GA4 ecommerce, or server-side tags send item_id values that must match Merchant Center product IDs.

Document before you migrate or reconnect

1. Open Merchant Center Data sources and record each primary and supplemental source name, owner, source type, last update time, and whether it says Content API, Merchant API, Shopify app, file upload, scheduled fetch, or another provider.
2. Export a representative product set with ID [id], item group ID [item_group_id], title, link, feed label, language, country or market, custom labels, and review status.
3. Save examples of current Shopify-generated IDs, including any Shopify_US, Shopify_CA, Shopify_GB, shopify_zz, or shopify_ZZ formats.
4. List every campaign, asset group, listing group, product group, feed-label filter, country filter, and custom-label filter that depends on the current IDs or labels.
5. List supplemental feeds, feed rules, attribute rules, promotion mappings, and product-data transformations that join to the primary source by ID.
6. Check the conversion tag item_id or GA4 items.item_id value for a test purchase or debug event and confirm it matches the Merchant Center ID you want campaigns to learn from.

What not to do

• Do not uninstall and reinstall the Google & YouTube app just to test the migration. Treat reinstalling as a change with product-ID risk until Google or Shopify says otherwise for your account.
• Do not bulk edit product IDs blindly. A changed ID can look like a new product to Google and can break filters, rules, joins, reporting, and history.
• Do not assume a Content API warning means your Shopify feed will break on the same day. First confirm whether the data source that owns products has already migrated or has a vendor-managed migration path.
• Do not change conversion tag item_id values until you know which Merchant Center IDs will survive the migration.

Wait, escalate, or change state

1. Wait and monitor when Data sources already shows Merchant API or a current Shopify app source, IDs are stable, products are approved, and campaign filters still match.
2. Escalate to Google or Shopify support before reconnecting when the app asks for a reinstall, the Merchant Center source owner changes, or products enter review unexpectedly.
3. Escalate to your feed provider or ads operator when supplemental feeds, product groups, custom labels, feed labels, or conversion tags are keyed to the old IDs.
4. Change state only after you have a rollback packet: old IDs, new IDs, data-source screenshots, affected campaign filters, tag item_id examples, and Merchant Center review status.

Where StoreSteady fits

Use the Google Shopping hub at /google-shopping to audit the public storefront side of the issue: price, availability, identifiers, policy signals, crawler access, and structured data. Connect Google and Shopify only when you need source-by-source comparison beyond public page evidence.