CrushPress.AI

Google Ads Unveils Robust Merchant API Before Content API Exit

```json { "alt": "Smartphone displaying Google Ads logo with analytics graph in the background.", "caption": "Explore the dynamic world of Google Ads as data analytics provides insights into your marketing impact.", "description": "This image features a smartphone screen prominently displaying the Google Ads logo with the welcome message. In the background, a computer screen shows an analytics graph, highlighting metrics like clicks and impressions. The image conveys the integration of digital advertising and data analysis, emphasizing marketing strategy and SEO insights. Useful for illustrating articles about online advertising and data-driven marketing." } ```

Written by

shivamcrushpressai

in

,

I recently discovered some exciting news that Google Ads has introduced a more robust Merchant API. This new API is crafted to offer advertisers scalable and feature-rich tools for handling product data, especially as we prepare for the shutdown of the Content API for Shopping.

Google is steering us toward a more modern, scalable infrastructure for Shopping integrations. This shift brings cutting-edge capabilities, including AI tools, directly into our scripting workflows.

What’s happening: Starting April 22nd, Google Ads scripts will support the Merchant API. This change comes as we approach the August 18th retirement of the Content API for Shopping. This new API will be available as an Advanced API within the scripts editor while we can still use the Content API until its official sunset.

What’s new: The Merchant API introduces a modular architecture, breaking down functionality into sub-APIs for quicker updates, easier maintenance, and fewer disruptions. This setup enhances capabilities with features like the Google Product Studio API for generative AI, APIs dedicated to product and store reviews, and a Notifications API for real-time updates.

Additionally, we now have more control over data management. This includes handling supplemental product data, managing local and regional inventories, and running promotions—all within an omnichannel system while still supporting our legacy setups.

Why it matters: The Merchant API provides a more flexible approach to managing product data at scale. It’s especially beneficial for complex or omnichannel setups and introduces new capabilities like AI-driven content tools that can boost feed quality and performance. With the imminent retirement of the Content API, transitioning to this new system is crucial to avoid disruptions and maintain competitiveness.

Yes, but: Switching to the new API requires adjustments, particularly for those of us with custom scripts or complex feed setups tied to the legacy API.

Bottom line: For those of us using scripts, this is our chance to upgrade to a more powerful and scalable integration, enabling new features while future-proofing our Shopping workflows before the cutoff date.

Dig deeper: Merchant API is coming to Google Ads scripts starting April 22, 2026

Inspired by this post on Search Engine Land.

crushpress.ai community screenshot

FAQs

What is changing with Google Ads scripts and the Merchant API?

Google Ads scripts will support the Merchant API as an Advanced API in the scripts editor. The post describes it as a more scalable and feature-rich way to handle product data before the Content API for Shopping is retired.

When does Google Ads scripts support for the Merchant API begin?

The post says Google Ads scripts will support the Merchant API starting April 22. It also notes that the Content API for Shopping can still be used until its official sunset.

When is the Content API for Shopping scheduled to retire?

The article says the Content API for Shopping is approaching retirement on August 18. Advertisers using custom scripts or complex feed setups should plan adjustments before that cutoff date.

What new capabilities does the Merchant API introduce?

The Merchant API introduces a modular architecture with sub-APIs for quicker updates and easier maintenance. The article highlights Google Product Studio API for generative AI, product and store review APIs, and a Notifications API for real-time updates.

Why does the Merchant API matter for product data management?

The post says the Merchant API gives advertisers a more flexible way to manage product data at scale. It is especially useful for complex or omnichannel setups, including supplemental product data, local and regional inventories, and promotions.

Who may need to make adjustments before moving to the Merchant API?

Advertisers with custom scripts or complex feed setups tied to the legacy Content API may need to adjust their workflows. The article frames the transition as a chance to upgrade Shopping integrations before the cutoff date.

Comments

Leave a Reply

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

More posts