Google Merchant Center · Status at source date: Newsletter archive
Google Merchant Centre sets 18 August deadline for Merchant API migration
VIVEK GUPTA has flagged that Google has announced 18 August 2026 as the final date for migrating Google Merchant Centre integrations to the Merchant API. The Merchant API is becoming the future direction for product data management and integrations within Google's ecosystem, replacing the legacy Content API workflow.

Why it matters for advertisers
For you, this means that engineering and feed management teams should plan the Merchant API migration well before the August deadline to avoid disruption to product data flows. Particularly relevant for agencies and retailers running custom feed integrations that still rely on the legacy API.
Perspective from the original PMC newsletter.Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterLinkedIn
Linked from the original newsletter. The source publication date has not been independently confirmed.
Original creator unverified
The names below are source credits. The original creator and first-reporting priority have not yet been independently verified.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
Original newsletter text and archive evidence
Google Merchant Centre sets 18 August deadline for Merchant API migration
VIVEK GUPTA has flagged that Google has announced 18 August 2026 as the final date for migrating Google Merchant Centre integrations to the Merchant API. The Merchant API is becoming the future direction for product data management and integrations within Google's ecosystem, replacing the legacy Content API workflow.
For you, this means that engineering and feed management teams should plan the Merchant API migration well before the August deadline to avoid disruption to product data flows. Particularly relevant for agencies and retailers running custom feed integrations that still rely on the legacy API.
Source captured . No explicit first-contributor label was provided for this update.




