CONNECTOR SETUP
Start using Google Analytics 4 in Claude
Connect Google Analytics 4 to Adzviser, add Adzviser to Claude, and start asking questions about your data.
Connect Google Analytics 4 to Adzviser
In Adzviser, sign in to Google Analytics 4 and allow Adzviser to read its reporting data.
Add Adzviser to Claude
Open Adzviser in Claude's connector directory, select Connect, and sign in to your Adzviser account when asked.
Open Adzviser in Claude ↗Ask your first Google Analytics 4 question
Ask Claude to list your Adzviser workspaces and show the GA4 property connected to each. Choose a workspace, pick a date range, and ask what you want to know.
CHOOSE THE RIGHT CLAUDE CONNECTOR
Google Analytics 4 in Claude: Google's official Google Analytics MCP server vs. Adzviser's read-only reporting connector
This side-by-side comparison covers Google's official Google Analytics MCP server and Adzviser's read-only Google Analytics 4 reporting connector in Claude. Both choices let Claude read Google Analytics reports. Google's option requires your team to run and maintain the server; Adzviser is ready to connect and can compare Google Analytics with your other marketing data.
Google's official Google Analytics MCP server
Install and maintain Google's Analytics server
Set up Python, a Google Cloud project, Analytics APIs and credentials, then run the server. This is a manual Claude connection: run the server, make its MCP address reachable, add it as a custom connector, and authorize it. Team and Enterprise workspaces require an owner to add the connector first.
Run core, funnel, and realtime Google Analytics reports.
Read-only: retrieve core, funnel and realtime reports without changing Analytics settings.
Google Analytics only: analyze properties available to the credentials you configure.
Best for: developers and technical analysts who want to own the server and its setup.
Read Google's setup guideAdzviser's read-only Google Analytics 4 reporting connector
Connect Google Analytics 4 without running your own server
Sign in to Google Analytics through Adzviser, then add Adzviser in Claude—no Python, Google Cloud project or server to maintain.
Ask Claude to review acquisition, engagement, landing pages or conversions and organize the findings into a clear marketing brief.
Read-only reporting; Claude can analyze Google Analytics through Adzviser but cannot change the property or its settings.
Compare Google Analytics with connected advertising, commerce, email and CRM results in the same Claude conversation.
Best for: marketing teams that want Google Analytics 4 and cross-channel reporting in Claude without server setup.
Open Adzviser in ClaudeCOPY-AND-PASTE PROMPT
Try a complete Google Analytics 4 analysis in Claude
Choose the right connected account, run a useful analysis, and get the supporting numbers and next steps in one response.
Compare behavior patterns between new and returning visitors.
First, show the GA4 property connected for Google Analytics 4 in each Adzviser workspace. Ask me which one I want to analyze. Then run this analysis: From the workspace I choose for the last 30 complete days, compare Google Analytics 4 new users vs returning users. Show: User Type, Sessions, Pageviews per Session, Average Engagement Time, Bounce Rate, Conversions, and Conversion Rate. How much more likely are returning users to convert? What's the ideal ratio of new vs returning users? Suggest strategies to increase both acquisition and retention. Start with the main takeaway, show the supporting numbers in a table, and suggest three next steps. If part of the answer is uncertain, say what information is missing.
ANALYSIS PLAN
Shape a Google Analytics 4 decision brief for Claude
Give Claude a clear scope, ask it to show its evidence, and finish with practical next steps for your team to review.
Start with the numbers
Get a concise weekly snapshot of sessions, users, and engagement metrics. Ask for the underlying figures and a clearly named comparison period.
See the “Weekly Traffic Overview” promptSeparate facts from explanations
Compare behavior patterns between new and returning visitors. Ask Claude to label possible causes as explanations to investigate, not facts.
See the “New vs Returning Users Comparison” promptTurn the findings into next steps
Identify landing pages with high traffic but poor engagement. Request a short list of actions to consider, the evidence for each, and what to measure next.
See the “Landing Page Optimization” prompt
