You Migrated Your Feed to the Merchant API. But Did You Check the Google Ads Side?

On 18 August 2026, Google is fully shutting down the Content API for Shopping — the system that has powered Shopping's plumbing for over a decade. No delay, no grace period; the date didn't move even when Google refreshed its developer release notes in early July. As of today, you have about 5 weeks.

There are dozens of guides about this migration online, and almost all of them cover the same thing: how to migrate your feed. That's fine — and it's already a solved problem. Your feed tool is probably handling the migration for you, and for Shopify and WooCommerce users the work is fully automatic.

This post is about the other half. The half nobody covers, because it isn't in the feed tools' interest to:

Even after the migration completes "successfully," your campaigns can die silently — and the problem isn't in the feed; it's on the Google Ads side.

Why the job isn't done when the feed migration is

The Merchant API migration is a feed-infrastructure task. But your Google Ads campaigns are tied to that feed through feed labels. And here's the critical part:

Feed labels don't migrate automatically.

If your campaigns are built around feed labels — which is very common in Shopping campaigns and especially in Performance Max asset groups — campaigns can drop out of serving if the feeds aren't re-linked correctly after the migration.

So the scenario is this: your developer or your feed tool tells you "migration done." Products show up in Merchant Center, everything looks fine. But on the Google Ads side, your asset group now points to a feed label that no longer exists, and your PMax campaign has no products to show.

Merchant Center is green. Google Ads is silent. Revenue drops.

Anatomy of the silent death

The most dangerous thing about this kind of failure is that it makes no noise. You don't get an error message, your account isn't suspended, no red warning appears. Just:

1. Impressions start to fall. Not slowly — but if you didn't look Monday morning, you won't notice.
2. PMax shifts the budget elsewhere. Because it can't show products, it leans into Search and Display inventory. Spend continues, ROAS collapses. Whoever reads the report concludes "PMax is underperforming."
3. Shopping campaigns are left without products. If the feed label doesn't match, the campaign technically looks "active" but has nothing to show.
4. The feed gets the blame. Everyone looks at Merchant Center, sees no problem there, and gets confused.

For an average team this loop can last 1–2 weeks. At the end of August — right in the middle of Q4 prep.

The single most important thing to do before the migration: take a baseline

The only way to answer "did something break after 18 August?" is to have a record of the un-broken state. Most teams skip this and then get lost in the "is this drop normal, seasonal, or from the migration?" debate.

If Opus Growth is connected, you can ask Claude or ChatGPT for it in one sentence:

"Pull the last 30 days of impressions, clicks, spend and conversions for my Shopping and Performance Max campaigns, broken down by campaign."

Do this before the migration and save it. It's not a 20-minute job, it's a 20-second one — and at the end of August it will be the only evidence you have.

Post-migration checklist

Once the feed side says "done," here's what to check on the Google Ads side:

1. Are your asset groups still seeing products?

"List the asset groups in my Performance Max campaigns and show the status of each."

PMax campaigns that use feed labels in their asset-group configuration are the most fragile against a post-migration mismatch. Look here first.

2. Who changed what in the account?

"List the account changes over the last 7 days — who, when, and what did they change?"

If your developer or agency touched something on the Google Ads side during the migration, this is the first place to look. The change history tells you whether "we didn't touch anything" is actually true.

3. What changed versus the baseline?

"Compare the last 7 days of my Shopping and PMax campaigns with the week before the migration. Are there any campaigns whose impressions or conversions dropped significantly?"

The only way to catch a silent drop is comparison. Looking at absolute numbers is misleading — seasonality, budget and competition all mix in. Comparing against the prior week cuts through that.

4. Check daily for the first week.

The 7 days after 18 August could be the most important 7 days of your year. Asking the same question every morning takes 30 seconds. The difference between catching the break and seeing it in the month-end report is a few days of revenue.

So what don't we do?

Let's be clear: Opus Growth does not do your feed migration. That's an infrastructure job on the Merchant Center side, and there are already good tools for it — go to your feed tool, your e-commerce platform, or your developer.

What we do is see what that migration broke on the Google Ads side. These are two different jobs, and for the second one your option today is to click through the Google Ads UI campaign by campaign and compare by eye.

Still not sure whether you're affected?

You can find out whether you're affected on the feed side in 2 minutes: Merchant Center Next → Settings → Data sources → the "Source" column. If it says "Content API," you need to act.

Not affected (nothing to do):

• XML feed, scheduled fetch, or manual file upload
• Those who send product data via Google Sheets
• Those using Shopify's official Google & YouTube channel or the WooCommerce Google Listings & Ads plugin (the platform handles it — just confirm your plugin is up to date)

Action needed:

• Those with custom code talking directly to Merchant Center
• Those using a third-party feed tool that hasn't migrated yet
• Those with an ERP/PIM integration

But beware: showing up as "not affected" on this list does not mean you're safe on the Google Ads side. Even if your feed tool did the migration for you, that migration may have changed your feed labels. So even if you're in the "platform handles it" group, run the checklist above.

In fact, this is exactly the riskiest group: advertisers who, because they didn't do the migration themselves, assume "nothing will happen to me" and therefore never check.

Frequently Asked Questions

If my feed tool did the migration, could my feed labels have changed?

Yes, they could. "The platform handles it" guarantees the feed reaches Merchant Center; it does not guarantee your Google Ads campaign configuration is intact. These are two separate systems.

Will the deadline be pushed back?

Google has given no signal of an extension or grace period so far. Don't plan around a delay.

Which is riskier, Shopping or Performance Max?

Both depend on Merchant Center product data. But PMax campaigns that use feed labels in their asset-group configuration are especially fragile against a post-migration mismatch — and because PMax shifts budget to other inventory when it can't show products, the failure stays hidden longer.

If my campaign stops after 18 August, where should I start?

In order: (1) are products showing in Merchant Center, (2) if so, is the feed-label match correct on the Google Ads side, (3) are the asset groups seeing products, (4) what happened in the change history on migration day. In most cases the problem shows up at step 2.

I forgot to take a baseline — is it too late?

No — take it today. There are 5 weeks until 18 August, so you're still in the "before." If your migration date is earlier, at least you'll have the data from the last clean week before it.