Help Center
Go back to application
Help Center
Go back to application
Getting started
IntroductionProduct Flow OverviewAudienceFlow OverviewUser - Right Management Settings - Client ManagementSMA IntegrationsCheck usage
Data Management
Data ManagementData Import SFTP & FTP ConnectionData Export Channel DuplicationData deletion Join Deduplication MappingFilter Product Flow alert Price assets Alert Merchant Center
Optimize flow
Formula EditorText Processing FormulasMathematical FormulasDate Handling FormulasPartition byRegex Variables
Use cases
Product Segmentation Feed AIAudience SegmentationProduct Feeds for AI Search
Reports and Insights
Reports and InsightsDetailed Import HistoryCAI - Catalog Activation InsightsPSI - Product Segmentation Insight
Updates & Assistance
Software updatesFAQContact usAdminTransition to Google Merchant API

Transition to Google Merchant API

Published on May 27, 2026 — This article will be updated regularly as progress is made.

This document centralizes all answers regarding the transition from the old Google API (Content API) to the new Google Merchant API, with the final deprecation set by Google for August 18, 2026.

What action is required on my end for this transition?

Our technical teams are currently deploying the new Google modules to anticipate the deprecation of the old API, guaranteeing a seamless transition with no service interruption and no impact on your feeds.

The only recommended action on your part will be to delete the deprecated data sources directly in your Google Merchant Center once the migration is complete. This will clean up your workspace of obsolete information. We will provide you with a guide as soon as the update is live.

What is the timeline for the transition?

The SmartFeeds transition to the Merchant API will take place gradually and transparently well before the August 18, 2026 deadline. There will be no negative impact on the delivery of your campaigns or the approval of your products in Google Merchant Center.

Here is the update schedule for our channels:

  • MCT Push: June 15, 2026
  • Vehicle Ads API: June 15, 2026
  • Local Inventory Ads (LIA) API: June 30, 2026

Do I need to create a new channel in SmartFeeds?

No, there is no need to create a new channel on your end. The technical switch is fully managed in the background by the SmartFeeds teams. Your current configurations, mappings, and optimizations will remain strictly unchanged.

I export my feeds via URLs. Am I affected by this migration?

No, you are not directly affected by this technical migration. The deprecation announced by Google concerns the evolution of its direct connection APIs. If your feeds are retrieved by Google via URL files, your setup remains identical.

Is it necessary or relevant to switch to an API feed if I am currently using a URL feed?

Not necessarily. For standard update frequencies, the classic URL feed remains perfectly sufficient and highly stable. However, the new Merchant API will indeed be available and integrated into SmartFeeds at no extra cost. A transition will therefore be possible if it aligns with a strategic or operational interest for your business.

Would switching to the API help resolve internal URL feed errors?

Using the API allows for more direct and granular communication with Google Merchant Center. Unlike file-based feeds (URLs) which import the entire catalog at once, the API enables targeted and faster updates, which can indeed eliminate certain file processing errors or timeouts on the GMC side.

Have you planned to make the Merchant API compatible with Vehicle Ads and LIA (Local Inventory Ads) feeds?

Yes, specific formats such as Vehicle Ads as well as local stock LIA feeds are an integral part of our technical roadmap.



Was this article helpful?

Powered by Product Fruits