Google Ads after the Merchant API migration: why feed labels silently stop campaigns

Moving from the Content API to the Merchant API changes how product data reaches Merchant Center. That belongs to your developer or feed tool. But Google Ads campaigns are tied to the feed through feed labels, and the label mapping does not migrate by itself.

The scenario goes like this: the feed side says “done”, products appear in Merchant Center, everything is green. Meanwhile the Performance Max asset group points at a label that no longer exists and has nothing to show.

The most dangerous thing about this failure is that it makes no noise. No error, no suspension, no red banner. Impressions fall, Performance Max shifts budget to Search and Display because it cannot show products, spend continues and ROAS collapses.

Whoever reads the report concludes that Performance Max is underperforming. Everyone looks at Merchant Center, finds nothing wrong and the confusion grows. For an average team the loop can last one or two weeks.

The only way to answer “did something break after the migration?” is a record of the unbroken state. With Tecrube connected that record is one sentence: “Pull the last 30 days of impressions, clicks, spend and conversions for my Shopping and Performance Max campaigns, by campaign.”

Run it before the migration and save it in the /app panel. It is a twenty-second job, not a twenty-minute one, and afterwards it will be the only evidence you have.

Check one: do the asset groups still see products? “List the asset groups in my Performance Max campaigns with the status of each.” Asset groups that rely on feed labels are the most fragile to a mismatch.

Check two: who changed what in the account? “Show the last seven days of change history with who, when and what.” This is where “we did not touch anything” gets verified.

Check three: compare with the baseline. “Compare the last seven days with the week before the migration; did any campaign lose a significant share of impressions or conversions?” Absolute numbers mislead, comparison is decisive. Ask it every morning for the first week.

When a mismatch is found the fix is usually simple: align the campaign’s or asset group’s feed label setting with the new value in Merchant Center. Tecrube shows the change as a preview: which campaign, old label, new label. It applies on your approval.

Tecrube does not perform the feed migration; that is Merchant Center work and platform plugins or feed tools exist for it. Tecrube’s job is to see what the migration broke on the Google Ads side and fix it with your consent.

In Merchant Center open the data sources screen and read the Source column. If it says “Content API”, you need to act. XML feeds, scheduled fetches, file uploads and Google Sheets are unaffected. If you use Shopify’s official channel or WooCommerce’s Google plugin, the platform handles the move; just confirm the plugin is current.

Tecrube’s ecommerce module watches the Merchant Center connection in the same panel, so when a product disapproval or label change appears you can ask about the campaign impact in the same chat. The first check fits within the 75 free credits.

The developer or feed owner runs the migration; checking the Google Ads side belongs to whoever runs the ads. Getting those two roles talking before the migration date is the most effective guard against the silent drop.

In Tecrube you can keep the baseline table and the daily comparison question in a chat the team shares, so everyone looks at the same data and responsibility is clear.

What is a feed label and why does it matter so much? A feed label decides which campaigns use which Merchant Center products. Shopping and Performance Max campaigns select products through it; when the label changes, a campaign can fall into a “no products” state.

Why can I not see the problem in Merchant Center? Because everything is correct there: products are approved and live. The break is on the Google Ads side, where the campaign points at a label that no longer exists. That is why the check needs a tool that sees both sides.

How far back should the baseline go? The 30 days right before the migration are ideal; if you changed campaigns or budgets recently, use the period after that change. Tecrube stores the table with a date in the panel and uses it automatically in later comparisons.

How long should I monitor after migrating? Every morning for the first seven days, then weekly for three more weeks. Performance Max shifting budget to other inventory shows up within days; spotting it early is worth several days of revenue.