CONNECT GOOGLE ANALYTICS 4 TO MUSE
Set up Google Analytics 4 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 Google Analytics 4 in Adzviser
In Adzviser, sign in to Google Analytics 4 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 GA4 property. 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 GOOGLE ANALYTICS 4 REPORT
Find landing pages that need a closer look
Build a report you can check
Compare the last 28 complete days with the previous 28 days for one GA4 property. Rank landing pages by the absolute change in sessions and show engaged sessions and engagement rate for both periods. Review traffic volume and engagement together: a page attracting more visitors can still have a weaker share of engaged sessions.
Use the traffic-source scope that matches the question
GA4 distinguishes first-user acquisition, session acquisition and event attribution. For a visit-focused landing-page review, use session-scoped source and medium in a compatible report. Do not interpret an acquisition dimension as proof that the same channel caused every subsequent purchase. Keep revenue analysis in a separate request when metric compatibility requires it.
Compare the affected audience
Ask Muse to narrow the largest landing-page change by session source and medium. If only one traffic source changed, investigate that acquisition source before proposing a site-wide redesign. Request the figures behind the explanation and identify what tracking or page review is still needed.
Metrics for this report: Sessions; Engaged sessions; Engagement rate; Total revenue.
Relevant breakdowns: First session landing page; Session source and medium.
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 Google Analytics 4 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 Google Analytics 4. List my workspaces and ask which connected GA4 property to use. Compare the last 28 complete days with the previous 28 days for one GA4 property. Rank landing pages by the absolute change in sessions and show engaged sessions and engagement rate for both periods. Review traffic volume and engagement together: a page attracting more visitors can still have a weaker share of engaged sessions. Use these metrics in compatible reports: Sessions, Engaged sessions, Engagement rate, Total revenue. Relevant breakdowns: First session landing page, Session source and medium. 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.
