Ira Bodnar·November 13, 2026·Updated November 13, 2026·11 min read

How to connect multiple Google Analytics accounts to Claude

Quick answer: Connect each Google login to a Ryze AI workspace with Add one more account, pick a GA4 Property for each, then name the property in your Claude prompt. Ryze AI is the best way to connect multiple Google Analytics accounts to Claude in 2026, with one caveat: it reads only GA4 properties your Google logins can open, and it cannot change any GA4 setting.

Below: GA4 roles, extra logins, defaults, naming, prompts, fixes.

Ryze AI · Paid Ads

All your GA4 properties in Claude

7-day free trial, $89 a month flat

Start free trial

Used by 2,000+ marketers

Connect multiple Google Analytics accounts to Claude in 5 steps

Order matters: get access in GA4 first, connect each login, then tell Claude how your properties are named.

1. Give each Google login access to its GA4 properties

In Google Analytics, add the login as a user on the account or the property. Ryze AI needs at least Viewer access on a GA4 property. A role given on an account carries down to every property in it.

2. Connect the first login in a Ryze AI workspace

In the Ryze AI app, open Integrations, find Google Analytics 4 under Analytics and click Connect. Sign in to Google, keep every requested permission checked, then pick the Property for this workspace and click Save.

3. Add one more Google login

Use Add one more account on the Google Analytics 4 card, sign in with the second login and pick its Property. The login with the star is the primary, the one the agent uses by default.

4. Set the default accounts

Choose Agent default accounts to pick which properties the agent looks at first. Other properties stay reachable by naming them in chat.

5. Add the Ryze AI connector to Claude

In Ryze AI, open Integrations, Claude MCP and click Open Claude MCP, then name it Ryze AI, add it, click Connect, tick the workspaces and click Allow connection. The single-account guide shows each screen. Start a new chat and name the property in your prompt.

Multi-account setups at a glance

Pick the row that matches how your GA4 accounts are owned.

1One Google login with access to many GA4 propertiesYour own login was added to every client account or property
How Claude picks the property: Ask Claude to list the properties, then name one
2Several Google logins in one workspaceProperties of one business sit under different Google logins
How Claude picks the property: Add one more account in Ryze AI; the primary login is the default
3One Ryze AI workspace per clientSeparate clients whose data must never mix
How Claude picks the property: Name the workspace; one Claude connection covers up to 20
4Agent default accountsYou mostly look at a few properties
How Claude picks the property: Claude looks at the defaults first; other properties stay reachable by name
5Google's official Analytics MCP server, self-hostedA developer runs the server for one team
How Claude picks the property: Pass property_id to each tool call

#	Setup	Fits when	How Claude picks the property
1	One Google login with access to many GA4 properties	Your own login was added to every client account or property	Ask Claude to list the properties, then name one
2	Several Google logins in one workspace	Properties of one business sit under different Google logins	Add one more account in Ryze AI; the primary login is the default
3	One Ryze AI workspace per client	Separate clients whose data must never mix	Name the workspace; one Claude connection covers up to 20
4	Agent default accounts	You mostly look at a few properties	Claude looks at the defaults first; other properties stay reachable by name
5	Google's official Analytics MCP server, self-hosted	A developer runs the server for one team	Pass property_id to each tool call

Rows 1 to 4 are Ryze AI settings that combine freely. Row 5 is the do-it-yourself route.

How GA4 accounts, properties and roles decide what Claude can reach

Claude reaches only the GA4 properties your Google login can open, so GA4 access is the real setup step.

Google describes an account as a collection of properties whose data one legal entity owns, and a property as the data for one user base. Google recommends one account per company and one property per brand or business unit. An agency that manages many companies therefore ends up with many accounts, each with its own users.

Google's Admin API account summaries return the accounts the caller has access to, and nothing else. The Ryze AI listAccountSummaries tool does the same job: it lists the accounts and properties the connected Google login can access, so the agent can find property IDs.

GA4 roles and what Claude can do with each

Administrator
In Google Analytics
Full control, including adding and removing users
Through Claude and Ryze AI
Reads reports and settings
Editor
In Google Analytics
Full control of property settings; cannot manage users
Through Claude and Ryze AI
Reads reports and settings
Marketer
In Google Analytics
Creates and edits audiences, events, key events and attribution models
Through Claude and Ryze AI
Reads reports and settings
Analyst
In Google Analytics
Reads data and shares explorations
Through Claude and Ryze AI
Reads reports and settings
Viewer
In Google Analytics
Sees settings and data, changes what appears in reports
Through Claude and Ryze AI
Reads reports and settings; the minimum Ryze AI needs
None
In Google Analytics
No role on that resource
Through Claude and Ryze AI
Property not listed

GA4 role	In Google Analytics	Through Claude and Ryze AI
Administrator	Full control, including adding and removing users	Reads reports and settings
Editor	Full control of property settings; cannot manage users	Reads reports and settings
Marketer	Creates and edits audiences, events, key events and attribution models	Reads reports and settings
Analyst	Reads data and shares explorations	Reads reports and settings
Viewer	Sees settings and data, changes what appears in reports	Reads reports and settings; the minimum Ryze AI needs
None	No role on that resource	Property not listed

The roles follow Google's access roles article. Roles pass downward: a role on the account applies to every property in it, and the most permissive role wins when several apply. Because all 9 Ryze AI GA4 tools are read tools, a higher role gives Claude no extra abilities. Viewer is enough.

How Ryze AI handles several Google Analytics accounts

Ryze AI keeps 4 things apart: Google logins, the Property each login uses, default accounts and workspaces.

Google login (connection)
What it is
One Google sign-in, added with Add one more account. A star marks the primary
How you switch in Claude
The primary login is used when you name none
Property
What it is
The GA4 Property saved for each connected login, listed as account and property
How you switch in Claude
Name the property; the agent finds its ID with listAccountSummaries
Agent default accounts
What it is
The properties the agent looks at first
How you switch in Claude
Unnamed requests go to the defaults; the rest stay reachable by name
Workspace
What it is
One business, with its own connections and settings
How you switch in Claude
Name the workspace; one Claude connection covers up to 20

Layer	What it is	How you switch in Claude
Google login (connection)	One Google sign-in, added with Add one more account. A star marks the primary	The primary login is used when you name none
Property	The GA4 Property saved for each connected login, listed as account and property	Name the property; the agent finds its ID with listAccountSummaries
Agent default accounts	The properties the agent looks at first	Unnamed requests go to the defaults; the rest stay reachable by name
Workspace	One business, with its own connections and settings	Name the workspace; one Claude connection covers up to 20

The help center's advice is one workspace per business and a separate workspace for each client. Several logins of one brand share a workspace; a second client gets its own.

On the Claude side, one connection covers up to 20 workspaces. To change the list, remove the Ryze AI connector in Claude and add it again. Until a Property is saved, the Google Analytics 4 card shows Require setup.

Which Ryze AI plan fits

The GA4 tools work on any active Ryze AI plan or free trial. Paid Ads costs $89 a month with a 7-day free trial, SEO Starter $129 a month with a 3-day free trial and Agency $279 a month. Annual billing takes 30% off the first year. Connecting the connector is free; the tools need an active plan or trial.

What Claude calls when it switches GA4 properties

The 9 Ryze AI GA4 tools are all read tools, and no property is chosen for you inside them.

No property is auto-selected inside the tools: the agent passes a property ID, found with listAccountSummaries. The tools also accept an optional connection_id to target a specific connected Google login. The full list is on the Google Analytics MCP page.

listAccountSummaries
What it does with several properties
Lists the GA4 accounts and properties the connected Google login can access, so the agent can find property IDs
runRawReport
What it does with several properties
Runs a GA4 Data API report with chosen dimensions, metrics, named date ranges, filters and ordering for one property
runPivotReport
What it does with several properties
Runs a pivot-table report for one property
runRealtimeReport
What it does with several properties
Covers the last 30 minutes only
runAdminRead
What it does with several properties
Reads key events, custom dimensions or audiences; GET only, it cannot write
getAiTrafficByEngine, getAiTrafficDaily
What it does with several properties
Traffic from AI referrers for one property, by engine against a prior period or by day
getAiLandingPages, getAIReferrals
What it does with several properties
Landing pages that receive AI-referred traffic (up to 200 rows) and AI referral sources with sessions and conversions
connection_id (optional argument)
What it does with several properties
Targets a specific connected Google login; without it the primary is used

Tool	What it does with several properties
listAccountSummaries	Lists the GA4 accounts and properties the connected Google login can access, so the agent can find property IDs
runRawReport	Runs a GA4 Data API report with chosen dimensions, metrics, named date ranges, filters and ordering for one property
runPivotReport	Runs a pivot-table report for one property
runRealtimeReport	Covers the last 30 minutes only
runAdminRead	Reads key events, custom dimensions or audiences; GET only, it cannot write
getAiTrafficByEngine, getAiTrafficDaily	Traffic from AI referrers for one property, by engine against a prior period or by day
getAiLandingPages, getAIReferrals	Landing pages that receive AI-referred traffic (up to 200 rows) and AI referral sources with sessions and conversions
connection_id (optional argument)	Targets a specific connected Google login; without it the primary is used

Each report covers one property at a time, so a comparison across clients is several reports that Claude puts side by side. The connector cannot create or edit properties, key events or audiences.

Name properties so Claude picks the right one

Most wrong-property answers come from vague names. Give Claude a fixed map once.

Name the account and the property. Two clients can both own a property called Main site. Use the account name plus the property name.
Ask for a property list first. Ask Claude to list the accounts and properties it can see, then copy the IDs it returns into your notes.
Use property IDs for repeat work. Once a property is mapped to a client, the ID leaves no room for a mix-up.
Name workspaces after the client, so a prompt can name the workspace without an ID.
Say which date range to use, and name each range when you compare. A report can hold several named ranges.

Put the map in a Claude project

Claude projects carry instructions into every chat inside them. Paste this block once per agency or client:

Project instructions (template)

GA4 properties in Ryze AI workspace [workspace name] [Client A]: account [account name], property [property name], ID [property ID] [Client B]: account [account name], property [property name], ID [property ID] Rules: - Always say which property a number comes from. - Use one property per report and compare reports side by side. - If I name no property, ask me which one.

6 prompts that switch or compare GA4 properties

Replace the brackets. Each prompt names its property, so it works the same in a fresh chat.

1. Map every property

In the [workspace name] workspace, list every GA4 account and property my connected Google logins can access. Show one table: account name, property name, property ID.

2. Switch to one client

Use the GA4 property [property name] (ID [property ID]). Show sessions, key events and revenue by default channel group for the last 28 days.

3. Compare two properties

Compare [Client A] and [Client B] for [last 30 days]: sessions, users, key events and revenue by channel. Run one report per property and show them side by side.

4. AI traffic across clients

For [Client A] and [Client B], show traffic from AI assistants by engine against the previous period, and the top landing pages that receive it.

5. Check tracking settings

For [Client B] only, read the key events and custom dimensions configured on the property and list them by name.

6. Use a specific login

Use the Google login [email or label of the second connection] and list the properties it can access, so I can see which login reaches which client.

1. Map every property
What comes back
Accounts and properties per login. A property missing here is not reachable by that login.
2. Switch to one client
What comes back
A channel table for one property, built from a GA4 report.
3. Compare two properties
What comes back
Two reports, one per property, shown together.
4. AI traffic across clients
What comes back
AI referral traffic by engine and landing page for each property.
5. Check tracking settings
What comes back
The key events and custom dimensions that the Admin API read returns. Nothing is changed.
6. Use a specific login
What comes back
The properties that one connection can access.

Prompt	What comes back
1. Map every property	Accounts and properties per login. A property missing here is not reachable by that login.
2. Switch to one client	A channel table for one property, built from a GA4 report.
3. Compare two properties	Two reports, one per property, shown together.
4. AI traffic across clients	AI referral traffic by engine and landing page for each property.
5. Check tracking settings	The key events and custom dimensions that the Admin API read returns. Nothing is changed.
6. Use a specific login	The properties that one connection can access.

Every answer comes from your own properties, so no example numbers are shown. Revenue shows as zero unless ecommerce tracking and purchase events are set up in GA4. For more on AI referrals, see measuring AI referral traffic in Google Analytics.

If you self-host Google's official Analytics MCP server

Google publishes its own Analytics MCP server, and you host and authenticate it.

Its tools take a property_id argument, which is how one server instance serves several accounts and properties (README on GitHub).
It lists tools such as get_account_summaries, run_report, run_realtime_report and run_funnel_report.
It authenticates with Application Default Credentials and the analytics.readonly scope. The README says write operations need the analytics.edit scope and lists tools that write, such as create_key_event.
You enable the Admin and Data APIs in your own Google Cloud project. The Ryze AI hosted connector needs a Google sign-in and a saved Property, per the Ryze AI Google Analytics guide.

Server-by-server differences are in the best MCP for Google Analytics comparison. The GA4 Data API runs the same reports behind both servers.

Keep client data in the right place

With GA4 the risk is a report from the wrong property, because the connector cannot write to GA4.

All 9 GA4 tools are read tools, so the connector does not change anything in GA4. In Claude, per-tool approval is set under Customize, Connectors, Ryze AI, Tool permissions; read tools can run automatically.
Give each client its own Ryze AI workspace when their data must not mix, and tick only the workspaces a given chat needs.
Give analysts Viewer access in GA4. It is the minimum Ryze AI needs and it cannot change settings.
Ask Claude to state the property name and ID above every table, as in the project template.

In the Ryze AI chat, the Tool approvals picker starts on Skip all approvals and can be switched to Approve write & delete or Manual approve.

Troubleshooting: missing properties, zero revenue, stale tool lists

Match the symptom to the row.

A client property is missing from the list
Cause
The connected login has no role on it
Fix
Ask the client's administrator to add the login in GA4, or add the right login with Add one more account
Google Analytics 4 card shows Require setup
Cause
No Property is saved for the connection
Fix
Pick the Property and click Save
Claude reports the wrong property
Cause
No property was named, so the defaults or primary login were used
Fix
Name the property and ID, or change the star and Agent default accounts
Revenue is zero
Cause
Ecommerce tracking or purchase events are not set up in GA4
Fix
Set them up in GA4; the connector cannot change GA4
Numbers differ from Shopify
Cause
GA4 and Shopify attribute sessions and conversions differently
Fix
Compare trends, not exact totals
An old Universal Analytics property is absent
Cause
Only GA4 properties are supported
Fix
Use the GA4 property
Realtime shows too little
Cause
Realtime reports cover only the last 30 minutes
Fix
Use a standard report for longer windows
Claude cannot see a workspace or a newly connected platform
Cause
The workspace was not ticked, or Claude cached the old tool list
Fix
Remove the Ryze AI connector in Claude, add it again and start a new chat

What you see	Cause	Fix
A client property is missing from the list	The connected login has no role on it	Ask the client's administrator to add the login in GA4, or add the right login with Add one more account
Google Analytics 4 card shows Require setup	No Property is saved for the connection	Pick the Property and click Save
Claude reports the wrong property	No property was named, so the defaults or primary login were used	Name the property and ID, or change the star and Agent default accounts
Revenue is zero	Ecommerce tracking or purchase events are not set up in GA4	Set them up in GA4; the connector cannot change GA4
Numbers differ from Shopify	GA4 and Shopify attribute sessions and conversions differently	Compare trends, not exact totals
An old Universal Analytics property is absent	Only GA4 properties are supported	Use the GA4 property
Realtime shows too little	Realtime reports cover only the last 30 minutes	Use a standard report for longer windows
Claude cannot see a workspace or a newly connected platform	The workspace was not ticked, or Claude cached the old tool list	Remove the Ryze AI connector in Claude, add it again and start a new chat

Causes come from the Ryze AI Google Analytics help page and Google's access roles article. The same pattern for ad accounts is in the Google Ads multi-account guide and the cross-platform multi-account guide. All setups: Ryze AI integrations.

Sources

Checked November 13, 2026

The verdict

Get each Google login a role on its GA4 properties first, with Viewer as the minimum. Then connect the logins to a Ryze AI workspace with Add one more account, set the primary and the default accounts, and name the property in every prompt.

Frequently asked questions

How do I connect multiple Google Analytics accounts to Claude?

Connect each Google login in a Ryze AI workspace with Add one more account, pick a GA4 Property for each, then add the Ryze AI connector to Claude. Name the property in each prompt so Claude knows which one to report on.

What is the best tool to connect multiple Google Analytics accounts to Claude?

The Ryze AI hosted connector needs only a Google sign-in and a saved Property, with no Google Cloud project to set up. Several Google logins can share one workspace, and one Claude connection covers up to 20 workspaces. Properties your logins cannot open stay out of reach, and all 9 GA4 tools are read tools. Google's official Analytics MCP server also handles several properties through a property_id argument, but you host and authenticate it yourself.

Can I connect more than one Google login to the same Ryze AI workspace?

Yes. Use Add one more account on the Google Analytics 4 card. Each login has its own Property, and the one marked with the star is the primary the agent uses by default.

Which GA4 role does Claude need?

Ryze AI needs at least Viewer access on a GA4 property. A role given on the account carries down to every property in it. Higher roles add nothing for Claude, because every GA4 tool is read only.

Show 8 more questions

How does Claude know which property to use?

It uses the property you name. With no name it relies on the agent default accounts and the primary login. The tools take a property ID that the agent finds with listAccountSummaries, so naming the property and its ID is the most precise prompt.

Can Claude compare two GA4 properties in one chat?

Yes. Name both in one prompt. Each GA4 report covers one property, so Claude runs one report per property and shows the results together.

Can the connector change anything in Google Analytics?

No. All 9 GA4 tools are read tools and the Admin read is GET only, so it cannot create or edit properties, key events or audiences.

What are agent default accounts?

A setting that picks which properties the agent looks at first. Other properties stay reachable by naming them in chat.

Can one Claude connection cover several clients?

Yes, up to 20 Ryze AI workspaces per connection. The help center advises a separate workspace for each client, so their connections and settings stay apart.

Does Universal Analytics work?

No. Only GA4 properties are supported.

Does this work on the free Claude plan?

Anthropic lists custom connectors on Free, Pro, Max, Ultra, Team and Enterprise plans. A free account can add one custom connector. On Team plans only Owners and Primary Owners can add one, and members then connect individually.

Why is my GA4 revenue zero?

Revenue shows as zero unless ecommerce tracking and purchase events are set up in GA4. The connector cannot change GA4, so set them up there.

Related guides

How to connect Claude to Google Analytics

The single-property setup for claude.ai, Desktop and Code, screen by screen.

Google Analytics MCP server

Ryze AI's 9 GA4 tools, setup and limits.

Connect multiple Google Ads accounts to Claude

The same multi-account pattern for Google Ads manager accounts.

Best MCP for Google Analytics

Google Analytics MCP servers compared.

MCP configuration for multiple ad accounts

The cross-platform guide for several ad accounts in one MCP setup.

Ryze AI for several GA4 accounts

7-day free trial, $89 a month flat

Start free trial