CONNECT META ADS TO MUSE
Set up Meta Ads 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 Meta Ads in Adzviser
In Adzviser, sign in to Meta Ads 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 ad 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 META ADS REPORT
Separate rising delivery costs from changing results
Build a report you can check
For one ad account, compare the last seven complete days with the preceding week. Show spend, impressions, reach, frequency and reported ROAS by campaign. Flag campaigns where spend increased while ROAS declined. For the largest changes, request ad-set detail separately and state which attribution settings apply to the returned results.
Keep reach and attributed sales in context
Campaign audiences can overlap, so summing campaign reach does not establish account-wide unique reach. Likewise, Meta-attributed purchases and store orders are two views of sales, not independent revenue streams. Rising frequency is a reason to inspect delivery and creative performance; by itself it does not prove creative fatigue.
Build a shortlist of creative tests
For a flagged ad set, compare the available ad-level results and name the ads driving the change. Ask for two test hypotheses grounded in those observations, plus the metric and reporting period you would use to evaluate each test.
Metrics for this report: Spend; Impressions; Reach; Frequency; Return On Ad Spend (ROAS).
Relevant breakdowns: Campaign Name; Ad Set 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 Meta Ads 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 Meta Ads. List my workspaces and ask which connected ad account to use. For one ad account, compare the last seven complete days with the preceding week. Show spend, impressions, reach, frequency and reported ROAS by campaign. Flag campaigns where spend increased while ROAS declined. For the largest changes, request ad-set detail separately and state which attribution settings apply to the returned results. Use these metrics in compatible reports: Spend, Impressions, Reach, Frequency, Return On Ad Spend (ROAS). Relevant breakdowns: Campaign Name, Ad Set 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.
