Claude Code's GA4 connection helps developers investigate whether event instrumentation matches the data reaching Analytics. It adds reporting tools to a coding session without requiring Google credentials in the repository. Use it to check an event contract, then decide whether the next task belongs in code, Tag Manager or GA4 configuration.
What do you need before connecting?
Use Claude Code installed on the computer where you will run these commands. Its CLI supports remote HTTP MCP servers and browser OAuth. This route registers an explicit user-scoped server for use across your projects; project-scoped team configuration is a separate choice. You do not need to run a local Google API server.
- A Google login with access to the GA4 property you want to analyze.
- A LoomaScale account and a Google Analytics connection; connecting Google Ads alone does not authorize Analytics.
- The property's numeric ID, or permission to discover it from the account list. A G- measurement ID identifies a web stream and is not the reporting property ID.
How do you connect Claude Code to GA4?
1. Connect GA4 in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Analytics, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Register the remote MCP server in Claude Code
Run this command in your system terminal, outside a Claude Code conversation. User scope makes the connection available across your projects. The URL selects this Google service's tools.
claude mcp add --transport http --scope user loomascale-ga4 https://api.loomascale.com/mcp/ga4If you already use the full LoomaScale agent plugin, check its tools before adding a second connection. The plugin route is documented in the Claude Code setup guide; this article uses direct MCP setup.
3. Authenticate from Claude Code's MCP menu
Open Claude Code and enter /mcp. Select loomascale-ga4 and complete its authentication flow in the browser. Use the LoomaScale account with your Google source connected. Return to Claude Code and confirm the server is connected. You can inspect the saved server from the system terminal with claude mcp get loomascale-ga4 or claude mcp list. A successful add command saves configuration; it does not prove that the Google account lookup succeeded.
4. Verify access with an actual account lookup
Use LoomaScale to call ga4_get_account_summaries. List my accessible GA4 properties with their names and numeric property IDs. Ask me which property to use. Read its reporting time zone and currency. Do not change any settings.
The response should contain properties from your own Google login, with a resource such as properties/123456789. Select the property by name and ID, then keep that selection in subsequent requests. A description of GA4 or a sample dashboard does not prove that the connector retrieved data. An empty account list can be a valid response from a login with no accessible properties.
How do you check an event contract with Claude Code and GA4?
Start with an event you can identify in the repository, such as generate_lead. Have Claude Code record the spelling and the conditions under which the site emits it. Then compare that contract with GA4's observed event names and recent counts. An absent event is a lead for investigation, not automatic evidence that the code never executed.
Use LoomaScale with the GA4 property I selected. Read this repository's lead-form event instrumentation without editing files. Identify the intended event names and when they fire. Report eventCount by eventName for the last 7 complete days and check the expected names. If useful, query realtime events separately. Explain what the report verifies and what needs a browser test. Do not create events or change settings.
Separate an event-name mismatch from a collection failure. A recent event can be absent from a dated report while processing is still underway; a realtime result answers a different time-window question. Check the intended property and stream before editing code. If a browser test is needed, perform it in the site's appropriate test environment and check its actual emitted requests.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/ga4The service-specific endpoint exposes GA4 tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Claude Code read or change in GA4?
LoomaScale can retrieve traffic, engagement, key events, revenue, realtime activity and funnel reports. Start with reporting and specify dates, dimensions and metrics. Configuration tools can mark key events, add or change event rules, adjust enhanced measurement and data redaction, and create or rename web streams after you approve a dry run; they need an Editor role on the property and the analytics.edit permission granted at connect, and report access alone does not grant editing. Connecting an assistant does not install a website tag, create historical events or make GA4 attribution identical to an ad platform's attribution.
Why is the connection or data missing?
If the server needs authentication, open /mcp and sign in again. If tools are missing, check claude mcp list, the source endpoint, and whether an organization policy restricts the server. Restart the session after a configuration change if needed. A Claude web connector and an explicit CLI server can overlap; check the active tools before adding duplicate connections.
If the property is missing, confirm the Google email and property access, then check the Analytics connection in LoomaScale. If a report is empty, check the property, dates, filters and whether the site actually sends events. Compare equivalent periods in the property's time zone. For a metric mismatch, preserve the exact metric names and attribution definitions before drawing conclusions. Use the reporting property ID rather than the G- stream identifier.
Related connection guides and official references
Use GA4 in another assistant
- How to Connect ChatGPT to GA4
- How to Connect Claude to GA4
- How to Connect Codex to GA4
- How to Connect Grok Build to GA4
Connect another Google source to Claude Code
Official setup references
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
