CONNECT ADOBE ANALYTICS TO MUSE
Set up Adobe Analytics 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 Adobe Analytics in Adzviser
Connect Adobe Analytics using OAuth Server-to-Server credentials: a Client ID and Client Secret. 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 report suite. 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 ADOBE ANALYTICS REPORT
Locate the pages behind a traffic change
Build a report you can check
Choose one report suite and compare two complete 28-day periods. Request page views, entries and exits by page or site section. Rank pages by the largest absolute entry change, then inspect the exit pattern. Request revenue and orders separately when their compatible dimensions or attribution rules differ from the page-flow report.
Respect the report suite’s implementation
Adobe measurement depends on the configured suite and reporting definitions. A page view, entry and exit describe different behaviors; they are not interchangeable visit totals. Do not treat page-attributed revenue as a causal statement about the page or assume that two suites implement the same business events.
Prepare an analytics investigation
Ask Muse to identify a site section with changing entries or exits and state the evidence behind the selection. Use that shortlist to inspect acquisition, navigation or tagging changes. Confirm the implementation before recommending a page redesign based solely on the trend.
Metrics for this report: Total page views; Entries; Exits; Revenue; Total orders.
Relevant breakdowns: Page; Site section.
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 Adobe Analytics 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 Adobe Analytics. List my workspaces and ask which connected report suite to use. Choose one report suite and compare two complete 28-day periods. Request page views, entries and exits by page or site section. Rank pages by the largest absolute entry change, then inspect the exit pattern. Request revenue and orders separately when their compatible dimensions or attribution rules differ from the page-flow report. Use these metrics in compatible reports: Total page views, Entries, Exits, Revenue, Total orders. Relevant breakdowns: Page, Site section. 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.
