CrushPress.AI

Urgent: Switch to Google’s New Merchant API or Risk Ad Interruptions

```json { "alt": "Smartphone displaying the Google Ads logo held in a hand.", "caption": "Navigating the digital advertising world with Google Ads at your fingertips.", "description": "A close-up image shows a smartphone held in a hand, displaying the Google Ads logo prominently on the screen. The logo consists of a multicolored 'A' shape, representing Google's advertising platform. The background is blurred, focusing attention on the phone. This image is ideal for discussions related to digital marketing, online advertising strategies, and Google Ads tutorials. Keywords include Google Ads, smartphone, digital marketing, and advertising." } ```

Written by

shivamcrushpressai

in

, ,

As someone deeply invested in digital advertising, I recently learned about Google’s impending changes to their Shopping API. If you rely on Shopping and Performance Max campaigns like I do, switching to Google’s Merchant API isn’t just recommended—it’s essential to keep things running smoothly.

What’s happening. Google plans to phase out older API versions, making the Merchant API the go-to for all things Shopping Ads. I checked my own campaigns in Merchant Center Next under Settings > Data sources to see which API I’m using. Any listing marked as “Content API” needed my immediate attention.

```json { "alt": "API users must switch to Merchant API by specific dates, options for different user types.", "caption": "Attention API users! Transition to Merchant API for enhanced management. Check deadlines for your user group.", "description": "This informative image outlines the transition to Merchant API, detailing deadlines for Merchant API beta users (by February 28, 2026) and Content API users (by August 18, 2026). Non-API users are encouraged to start integration for automated product uploads and inventory management. The design features bold text and action buttons for easy navigation, ensuring users stay informed and take necessary steps on time." } ```

Why this matters to us. Google has been actively notifying us advertisers to make the move to the new Merchant API. For those in beta, the deadline is February 28th, and for others using Content API, it’s August 18th. If I miss this, my campaigns that depend heavily on product feeds might just stop working. That’s not a risk I’m willing to take.

```json { "alt": "Google Merchant Center Data Sources page displaying product source information.", "caption": "Explore how Google Merchant Center automates product discovery and management with streamlined data sources.", "description": "The screenshot shows the Data Sources section in Google Merchant Center, highlighting both Google-found and user-provided product sources. The interface displays a primary source named 'Content API' with 18 products listed. On the left, various navigation options include Store Quality, Marketing, and Analytics. The page invites users to manage products that Google found on their online store. This overview helps businesses understand how to integrate product data efficiently. Keywords: Google Merchant Center, data sources, Content API, product management." } ```

The risk. I realized that feed labels don’t seamlessly transfer during the migration. Overlooking this can cause significant issues in Shopping and Performance Max campaigns, which rely on these labels for structure or bidding strategies. Without proper updating, my campaigns could quietly fail.

```json { "alt": "Notice about Merchant API replacing Content API, with key dates for transition in 2026.", "caption": "Attention sellers: Switch to Merchant API by 2026 for seamless access to Google services, as Content API will soon be retired.", "description": "The image is a notice confirming the Merchant API as the replacement for Content API for Shopping. Key transition dates include February 28, 2026, when Merchant API v1beta will be discontinued, and August 18, 2026, when Content API for Shopping will cease. Users must switch to Merchant API v1 by these dates to maintain access to Merchant Center. This change is essential for sellers to continue their organic and ad experiences on Google platforms efficiently. Keywords: Merchant API, Content API, deprecation, Google Shopping, transition dates, API switch." } ```

What to do now. Google’s suggesting that we complete this migration sooner rather than later. On my end, that means reviewing my feed labels, reconnecting my data feeds, and making sure everything’s back on track. This transition process started in mid-2024 and is becoming urgent as legacy APIs are on their way out.

Bottom line. Ignoring this isn’t an option for me. This change is more than just a backend tweak—it’s a potential revenue disruptor if not addressed promptly.

First seen. I first caught wind of this update through Google Shopping Specialist Emmanuel Flossie. He flagged the issue on LinkedIn.

Inspired by this post on Search Engine Land.

crushpress.ai community screenshot

FAQs

What are the migration deadlines for the Merchant API?

Beta users must migrate by February 28. Content API users must switch by August 18, 2026.

Why is switching to Merchant API necessary?

Google plans to phase out older API versions, so the Merchant API is essential to keep Shopping ads running. Campaigns that rely on product feeds may stop working if you don’t switch.

What are the risks if migration isn’t completed?

Feed labels may not transfer during migration, which can cause issues in Shopping and Performance Max campaigns. Keeping labels updated helps avoid disruption.

What should I do now to prepare?

Review feed labels, reconnect data feeds, and ensure everything is back on track. Start the migration sooner rather than later.

Who flagged the update publicly?

Emmanuel Flossie flagged the issue on LinkedIn. The post notes that he brought the update to attention.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

More posts