CONNECT MNTN TO MUSE
Set up MNTN 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 MNTN in Adzviser
Connect MNTN using an API key. 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 reporting scope. 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 MNTN REPORT
Compare CTV delivery with verified visits
Build a report you can check
Use two complete seven-day periods for the MNTN account accessible to your API key. Request total spend, CTV impressions, households reached, verified visits and cost per visit in compatible campaign reports. Identify the campaigns responsible for the largest spending changes and show whether verified visits moved in the same direction.
Keep visits distinct from customers and sales
A verified visit is a platform reporting measure, not a confirmed new customer. Household reach also differs from an individual-user count and may overlap across campaigns. Label MNTN-attributed revenue separately if you request it, rather than substituting it for your store’s sales total.
Choose a campaign for closer creative review
Ask Muse for the available ad-level detail of a campaign with rising spend and weaker visit performance. Request a short observation, supporting figures and the next measurement question. Use the result to prepare a review in MNTN, not an automatic spending change.
Metrics for this report: Total spend; CTV impressions; Households reached; Total verified visits; Cost per visit.
Relevant breakdowns: Campaign name; Ad name.
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 MNTN 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 MNTN. List my workspaces and ask which connected reporting scope to use. Use two complete seven-day periods for the MNTN account accessible to your API key. Request total spend, CTV impressions, households reached, verified visits and cost per visit in compatible campaign reports. Identify the campaigns responsible for the largest spending changes and show whether verified visits moved in the same direction. Use these metrics in compatible reports: Total spend, CTV impressions, Households reached, Total verified visits, Cost per visit. Relevant breakdowns: Campaign name, Ad name. 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.
