The Shopify Merchant API Migration Is About to Wipe Your Google Ads History. Your Agency Should Have Warned You.

What is actually happening

Google is shutting down the old Content API for Shopping. The replacement, the Merchant API, becomes the only option. The hard cutoff is 18 August 2026. After that date, anything still connected through the old system stops syncing.

Shopify is moving stores across to the new connection on its own schedule. That migration changes the format of your product IDs in Google Merchant Center.

Small change. Large consequence. Google identifies products by their ID. Change the ID and Google does not see an updated product. It sees a brand new one. Every click, every conversion, every signal your campaigns spent months and budget accumulating is tied to the old ID. When the ID flips, that history detaches.

Your feed label changes too. A clean label like "GB" becomes something like "GBP_123456". If your campaigns are structured by feed label rather than country, they stop matching their feed and can serve zero products.

Why this costs you money, not just data

"Losing historical data" sounds like an analytics problem. It is not. It is a margin problem.

Smart Bidding and Performance Max run on accumulated learning. Conversion history per product is what lets the algorithm bid confidently. Strip that history and the system re-enters learning mode across your catalogue. During learning, it bids less efficiently, spends to gather fresh data, and tolerates worse returns while it recalibrates.

So the real cost is not a gap in a report. It is weeks of inflated CPAs, wasted spend on re-exploration, and contribution margin bleeding out of your best SKUs precisely when they were finally profitable.

For a well-structured account the recovery is days. For a poorly structured one it can run for weeks. The difference is whether someone built the account to survive a reset in the first place. Most were not.

The bit nobody mentions: your feed rules and supplemental feeds break too

Here is the part that catches even careful operators.

Feed rules in Merchant Center are attached to a specific feed, not to your account. Your title rewrites, brand mappings, attribute fixes, custom labels, all of it lives on the Content API feed. When that feed goes inactive and a new Merchant API feed takes over as primary, the rules do not move with it. They simply stop applying.

Same story for supplemental feeds. The AI-optimised titles, the margin labels, the custom-label logic you bid against. They were linked to the old primary source. They do not auto-link to the new one. They go quiet.

So a brand can wake up to reverted product titles, missing custom labels, and listing groups in PMax pointing at subdivisions that no longer exist. No warning shot. Just performance softening for reasons that are not obvious from the dashboard.

Why this is an agency failure, not a Google one

Google published the deadline. The trade press has covered it. Warning notices started landing in Merchant Center accounts back in January. None of this was a secret to anyone whose job is to watch this platform.

The whole point of paying an agency is that someone is monitoring the plumbing so you do not have to. A migration that can reset your ad history and break your feed logic going into peak season is the textbook example of what a retainer is supposed to catch. Early, quietly, before it hits the account.

If the first time you hear about the Merchant API migration is from a blog post rather than from the people managing your spend, ask a fair question. What else is moving underneath the account that nobody has flagged? This is not a gotcha. It is a reasonable test of whether your account is being managed or merely maintained.

The brands that come through this cleanly will not be the ones who reacted fastest in August. They will be the ones whose accounts were already structured so the reset barely registered, and whose agency had a preservation plan in the diary in spring.

How to check whether you are affected

Do this today. It takes five minutes.

1. Open Google Merchant Center and go to Settings > Data sources.
2. Look at the source column for your primary product feed.
3. If it says Content API, you have not been migrated yet. You have a window to act.
4. If it says Merchant API and a new data source has appeared (often labelled something like "Shopify App API"), you have already been moved. Check whether your product IDs now carry the "ZZ" format and whether your feed rules and supplemental feeds are still applying.

Then check your product IDs directly. If they still show your country code, the old history is intact and worth protecting. If they have already flipped to "ZZ", the history for those IDs cannot be restored.

How to protect your data before the cutoff

You cannot solve this inside Merchant Center alone. The product ID field cannot be edited with feed rules on a native primary feed. Tweaking the Shopify app feed will not save you either. The fix is structural: take control of the feed with a feed management tool so you own the IDs, rather than letting Shopify hand you whatever the new app decides.

The architecture that works:

Get the sequence right and the ID stays stable, the rules keep applying, and the algorithm never notices a thing. That is the entire game.