CONNECT X ADS TO MUSE
Set up X 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 X Ads in Adzviser
In Adzviser, sign in to X 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 X ADS REPORT
Check campaign traffic against conversion outcomes
Build a report you can check
Compare two complete seven-day periods for one X Ads account. Request cost, impressions, URL clicks, conversions and cost per acquisition by campaign. Identify campaigns with increased cost but fewer URL clicks or conversions. Keep the selected conversion definition visible before deciding which campaigns need a closer review.
Distinguish destination clicks from broader engagement
The catalog includes clicks, URL clicks and media-engagement measures. Use URL clicks when the question concerns visits to the linked destination, rather than assuming all interactions are equivalent. A conversion count also needs its event definition and attribution context before it can be compared with another platform.
Find the ads contributing most to the change
For one campaign, request compatible ad or promoted-post detail and rank by absolute cost and outcome change. Ask Muse to produce a short manual-review list with the ad identifier, observation and evidence needed before changing it.
Metrics for this report: Cost; Impressions; URL clicks; Conversions; Cost per acquisition.
Relevant breakdowns: Campaign; 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 X 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 X Ads. List my workspaces and ask which connected ad account to use. Compare two complete seven-day periods for one X Ads account. Request cost, impressions, URL clicks, conversions and cost per acquisition by campaign. Identify campaigns with increased cost but fewer URL clicks or conversions. Keep the selected conversion definition visible before deciding which campaigns need a closer review. Use these metrics in compatible reports: Cost, Impressions, URL clicks, Conversions, Cost per acquisition. Relevant breakdowns: Campaign, 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.
