How to monitor multiple Merchant Center accounts

Google provides agency and advanced-account options for eligible operating models, but not every business with more than one Merchant account needs the same structure. Use current Google guidance and preserve each merchant's ownership and verification responsibilities.

Avoid moving or duplicating accounts simply to create a dashboard. Monitoring should sit on top of authorized access rather than alter Merchant ownership.

Every client workspace should keep Merchant credentials, products, issues, alerts, billing context, and team access isolated. A workspace switcher must change authorized server context, not merely filter a combined client-side dataset.

Raw issue totals are difficult to compare across stores of different sizes. A useful portfolio view combines Google severity, affected products, lifecycle change, connection health, and safely matched traffic.

• Which client has a new account-critical issue?
• Which issue expanded since the prior complete sync?
• Which affected products recently received clicks?
• Which client requires OAuth reconnection or has repeated sync failure?
• Which issue has now resolved and can be closed?

Group alerts by client and issue lifecycle rather than emitting one notification per product. Route access to the right team members, keep a shared history, and ensure switching accounts does not expose another client's data.

CommerceVigil Agency supports separated client workspaces and portfolio monitoring. It does not merge Merchant accounts, transfer ownership, share OAuth tokens between clients, or make feed changes. Google's account model and each client authorization remain authoritative.