CONNECT MATOMO TO MUSE
Set up Matomo 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 Matomo in Adzviser
Connect Matomo using your Matomo base URL and authentication token. 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 site. 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 MATOMO REPORT
Compare site outcomes before inspecting individual pages
Build a report you can check
For one Matomo site, compare two complete 28-day periods. Request the supported goal and ecommerce outcomes in separate reports, then ask for compatible page-traffic detail for the area you want to investigate. State the selected goal and include the website identity so results from different sites are not accidentally combined.
Keep goal value and store revenue distinct
A configured goal may have a value that represents a business assumption rather than an actual order. Ecommerce revenue describes a different report. Adding goal revenue to ecommerce revenue can double-count or mix incompatible values, so label both and explain the question each one answers.
Narrow the review to a concrete site question
Ask Muse to identify whether the observed change is primarily in traffic, measured goal completions or ecommerce results. Request the relevant page or acquisition breakdown only where supported, and describe the site checks needed to distinguish a business change from a tracking change.
Metrics for this report: Goal conversions; Goal revenue; Ecommerce orders; Ecommerce total revenue.
Relevant breakdowns: Website name; Page URL.
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 Matomo 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 Matomo. List my workspaces and ask which connected site to use. For one Matomo site, compare two complete 28-day periods. Request the supported goal and ecommerce outcomes in separate reports, then ask for compatible page-traffic detail for the area you want to investigate. State the selected goal and include the website identity so results from different sites are not accidentally combined. Use these metrics in compatible reports: Goal conversions, Goal revenue, Ecommerce orders, Ecommerce total revenue. Relevant breakdowns: Website name, Page URL. 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.
