CONNECT GOOGLE MERCHANT CENTER TO MUSE
Set up Google Merchant Center reporting in Muse
Adzviser retrieves the source data through its MCP reporting tools. Muse uses those results to answer your questions. Connect the source in Adzviser, then authorize Muse to use that connection.
Connect Google Merchant Center in Adzviser
In Adzviser, sign in to Google Merchant Center and allow Adzviser to read its reporting data. Add the source to the workspace you want to use in Muse.
Open Adzviser setup →Authorize Adzviser in Muse
Open Muse.ai and send: “Can you connect to custom Adzviser MCP at https://mcp.adzviser.com/http?” Select Connect on the Adzviser card, sign in to Adzviser, and select Complete Authorization via MCP. Return to Muse.
https://mcp.adzviser.com/httpVerify the first result
Ask Muse to list your Adzviser workspaces and their sources. Choose the workspace and confirm the merchant account. Request a small report for a known period before expanding the analysis.
The Adzviser reporting connection is read-only. It can retrieve data for analysis; it cannot edit source records or campaigns.
A USEFUL FIRST GOOGLE MERCHANT CENTER REPORT
Review product availability beside performance
Build a report you can check
Start with a current product list containing IDs, titles and availability. Separately request compatible performance measures for a defined period, keeping the marketing method visible. Ask Muse to identify products worth reviewing because of their current status or their reported traffic, without assuming the two reports have the same time basis.
Do not backdate a current product status
A product marked out of stock now was not necessarily unavailable throughout last month. Likewise, product identifiers and performance aggregations need to match before records can be compared. If a direct product-level pairing is unsupported, return separate tables and state the limitation.
Prepare a feed and performance review
Ask Muse for a concise list of products to inspect in Merchant Center, including the identifier, current availability and the supporting performance observation when available. Verify the feed and destination in Merchant Center before editing product information.
Metrics for this report: Impressions; Clicks; CTR; Conversions.
Relevant breakdowns: Product ID; Title; Availability; Marketing method.
These are starting fields, not a promise that every combination belongs in one report. Use separate requests for different reporting levels and check the full field catalog for additional coverage.
COPY INTO MUSE
Run your first Google Merchant Center analysis
Paste this after connecting. Change the period or research subject to match your question, and let Muse confirm the selection before retrieving results.
Use Adzviser to analyze Google Merchant Center. List my workspaces and ask which connected merchant account to use. Start with a current product list containing IDs, titles and availability. Separately request compatible performance measures for a defined period, keeping the marketing method visible. Ask Muse to identify products worth reviewing because of their current status or their reported traffic, without assuming the two reports have the same time basis. Use these metrics in compatible reports: Impressions, Clicks, CTR, Conversions. Relevant breakdowns: Product ID, Title, Availability, Marketing method. Check field compatibility and use separate tables for different reporting levels. State the actual reporting dates or observation window. Show the supporting rows, then give a short conclusion and one next investigation. Label missing data and separate observed changes from possible explanations.
