Skip to main content
Disapproved products don’t serve, and a Shopping or Performance Max campaign starved by its feed looks like a bidding or budget problem from the Ads side. AdLoop reads Google Merchant Center’s product status so your AI can rule the feed in or out first: how many products are approved, pending or disapproved, which issues affect the most products, and which account-level issues block serving altogether. Google’s Merchant API has no read-only permission: the only one available (content) also allows managing products. AdLoop only reads with it and has no tool that changes products or settings.

Connect

When you connect Google, leave Merchant Center ticked under Access for your AI (“Read product feed status, for Shopping and PMax”). Then pick the account, during onboarding or later under Settings → Google → Change. Agencies pick an account per client under Settings → Clients.Google requires a one-time registration before the Merchant API works with an account, and until then it doesn’t even list your accounts. If that is the case, the dashboard asks for your Merchant Center ID instead (shown top right in Merchant Center). When you save the account, AdLoop registers itself with it, so Google’s few minutes of processing happen before your first question.If the page says Permission missing — reconnect Google to enable Merchant Center, click Reconnect and approve the permission; your other selections stay as they are.
The registration needs a Google user with Admin access on the Merchant Center account (Merchant Center → Settings → People and access). If it fails, the tool returns that hint and a link to Google’s manual registration steps.

Behaviour worth knowing

  • Which account is checked. On AdLoop Cloud, the Merchant Center tools use the Merchant Center account selected for the workspace or the client, so your AI doesn’t need the ID. Self-hosted, set merchant.account_id in the configuration to get the same default. An account_id passed in the call always wins; your AI finds the IDs with list_merchant_accounts.
  • What comes back: approved, pending and disapproved counts per reporting context (Shopping ads, free listings, …) and country; the top product issues ranked by affected products, each with Google’s documentation link; account-level issues with their severity. CRITICAL means offers stop serving entirely.
  • Product by product: get_merchant_product_issues names the products behind those counts: disapproved (the default), limited or pending ones, each with its offer id, title and click potential, and every issue with the attribute it concerns, the countries affected and whether you have to act or Google is still reviewing. Products with high click potential come first, because fixing them brings back the most traffic. Filter by an issue code to get, say, every product that lacks a GTIN.
  • Product status lags about 30 minutes. A feed fix you just made won’t show yet.

Tools

  • list_merchant_accounts: the Merchant Center accounts your Google account can access
  • get_merchant_feed_health: product status totals, top issues and account issues for one account
  • get_merchant_product_issues: the individual products with issues, and their issues
For spend and conversions per product, see get_shopping_product_performance under Google Ads. Parameters are in the tool reference; the toolset slug is merchant (toolsets).

Limits

  • Read-only: AdLoop can’t edit products, the feed or account settings. Product issues list up to 1,000 matching products per call; narrow by issue code for larger feeds.
  • On AdLoop Cloud, Merchant Center calls are unmetered on every plan; see plans and limits.
  • On a solo plan or a client-scoped key, calls for an account other than the selected one are refused.

What AdLoop stores

On AdLoop Cloud: the selected Merchant Center ID and account name, next to your encrypted Google token. Feed data passes through and is never stored.