In short: As of April 22, 2026, the Merchant API is reachable from inside Google Ads Scripts — feed and campaigns finally live in one runtime. One script can now read Merchant Center data and act on it: a disapproved product gets pulled from a PMax listing group, an out-of-stock SKU pauses its asset group — automatically, with no external glue between two systems.
Feed and campaigns have always lived in separate worlds: campaigns scriptable in Google Ads Scripts, the feed managed somewhere else entirely. As of April 22, 2026, that wall is gone — the Merchant API is now reachable from inside Google Ads Scripts.
What changed
One script can now read Merchant Center data and act on it within the same Google Ads runtime. Combined with product_filters (conditional feed sharing with Google Ads, shipped November 2025), the loop between feed health and ad spend finally closes in a single environment.
Why it matters
The split used to force awkward workarounds: a feed problem detected in one system, a campaign reaction triggered in another, glued together with external plumbing. Now the reaction lives where the campaign control already is.
The obvious win is a closed-loop guardrail: a product gets disapproved in Merchant Center → the same script pulls it from the PMax listing group or trims its budget — automatically, without a human in the loop.
How to automate it
Start with the highest-pain feed event you handle manually today and wire it to a campaign action:
- Disapproval → exclusion. A SKU loses approval → remove it from the relevant listing group so spend stops chasing an unbuyable product.
- Out of stock → pause. Stock hits zero in the feed → pause or down-bid the asset group surfacing it.
- Price change → bid review. A margin-eroding price update → flag the product for a bid revisit.
This is the kind of cross-domain logic that previously needed two systems and a cron job between them. Now it’s one script, running on Google’s own schedule, with no external glue to maintain or secrets to pass between environments. Start small — one event, one action — and confirm the reaction fires before you wire up the next.
For the wider context of Google’s converging Ads and Merchant APIs, see our Google API year in review.
