By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Perplexity to Google Analytics is the Ryze AI connector. Connect Google Analytics 4 in a Ryze AI workspace with your Google sign-in and save a Property, then in Perplexity open Plugins, choose Add custom, Add MCP connector, Remote, and enter https://connector.get-ryze.ai/mcp with OAuth, Streamable HTTP and Public network access. Select the new connector card to sign in to Ryze AI.
- In Ryze AI open Integrations, find Google Analytics 4 under Analytics and click Connect
- Sign in to Google, keep every permission checked, then pick and save the Property
- In Perplexity open Plugins, Add custom, Add MCP connector, Remote, and enter the name and URL
- Set Authentication to OAuth, tick the acknowledgement, click Add, then select the connector card to sign in to Ryze AI
Perplexity to Google Analytics at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added to Perplexity as a custom remote connector |
| Connector address | https://connector.get-ryze.ai/mcp |
| Form settings | OAuth, Streamable HTTP, Public network access |
| Sign-in | Google approves Ryze AI once; the connector card in Perplexity then opens the Ryze AI sign-in. No client ID or secret |
| Google Analytics tools | 9, all of them read tools |
| Changes from Perplexity | None. The connector has no write tool for GA4 and asks only for the analytics.readonly scope |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace use the same address |
| Perplexity plan | Pro, Max or Enterprise, per Perplexity's changelog |
| Ryze AI price | Paid Ads, $89 per month with a 7-day free trial. The connector is free |
| Google's own server | analytics-mcp 1.1.0: runs on your computer, names Claude, Cursor and Antigravity, not Perplexity |
| Last tested | November 14, 2026, from Claude Code. Nothing was run inside Perplexity |
Before you start
- A Perplexity plan that allows custom connectors. Perplexity's March 2026 changelog, its connector troubleshooting article and a blog post of October 14, 2026 name Pro, Max and Enterprise subscribers. The custom connectors help article names no plan. Inside an Enterprise organization, a member can add a connector for their own account only after an administrator switches on Allow members to add custom connectors, which starts off. Only administrators add organization-wide connectors.
- A Google login with at least the Viewer role on a GA4 property. You choose it on the Ryze AI Connect step. Universal Analytics properties are not supported. If the login carries the No Revenue Metrics or No Cost Metrics restriction in GA4, those metrics stay hidden from every connector.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and annual billing takes 30% off the first year. Connecting the connector is free; the Google Analytics tools need an active plan or trial.
- Trust in the server. Perplexity's help center tells users to add only connectors from sources they trust, because it cannot verify third-party servers. Check who runs a server first.
How to connect Perplexity to Google Analytics
Setup has two parts: GA4 is connected inside Ryze AI, then Perplexity is pointed at the Ryze AI connector. The Perplexity steps follow its help center for a personal account. Nothing was tested inside Perplexity while this page was written, so use the troubleshooting list below if a screen differs.
Connect Google Analytics 4 in Ryze AI
Sign in to Ryze AI (or create an account), open Integrations in the left sidebar, find Google Analytics 4 under Analytics and click Connect.
Approve Google access and save a Property
Sign in to the Google login that can read your GA4 property and keep every requested permission checked. Back in Ryze AI, pick the Property for the workspace (listed as account and property) and click Save. Until a Property is saved the card shows Require setup.
Open Plugins in Perplexity
Open Plugins in the sidebar. If Plugins is not there, open Customize, then Connectors. Perplexity describes Plugins on sales-assisted Enterprise plans as a beta that an administrator turns on, so members there may still see Customize.
Add a remote MCP connector
Select Add custom, then Add MCP connector, and choose Remote. Type Ryze AI as the name and https://connector.get-ryze.ai/mcp as the MCP server URL. The name takes up to 64 characters and the address must start with https://.
Set the advanced options
Under Advanced choose OAuth for Authentication, Streamable HTTP for Transport and Public for Network access. Ryze AI supports dynamic client registration, so no client ID or secret is entered. Skip API Key: the form has no field for custom headers.
Add the connector and sign in
Tick the acknowledgement checkbox and select Add. Perplexity checks the server then and tags the card with an error if the check fails. Select the connector card on the Plugins page to start the Ryze AI sign-in, choose the workspace that holds your GA4 connection and enable the connector.
The Ryze AI Google Analytics guide covers the Google sign-in and the Property step on the Ryze AI side.
Sources: Perplexity: custom remote connectors, changelog of March 12, 2026, what are plugins. Checked November 14, 2026.
Enterprise organization setup
An Enterprise administrator can add the connector once for everyone instead of each member adding it:
- Open Organization settings, then Connectors, and select Custom connector. Organization connectors are always remote, so the dialog offers no Remote choice.
- Enter the name and URL, set the advanced options as in the steps above, tick the acknowledgement checkbox and select Add.
- A new organization connector starts switched off. Turn it on under Organization settings, then Connectors.
- Decide between one shared sign-in for the organization and a sign-in for each member. A shared sign-in means every member reads GA4 through the same Ryze AI workspace, so pick per-member sign-in if people should see only their own data.
Perplexity's help center also describes a Cloudflare Access network option and AWS PrivateLink for Enterprise. The Ryze AI connector is a public address, so Public is the setting to use. Connector connections and disconnections appear in the organization's audit logs.
Sources: Perplexity: custom remote connectors, organization plugins. Checked November 14, 2026.
Local MCP and other surfaces
Local MCP servers on the desktop
Two places run a local MCP server from a command, according to Perplexity: the Mac app with its PerplexityXPC helper installed, and Portable Computer in Local mode. Perplexity on the web takes remote connectors only. The Ryze AI connector is remote, so it goes through the Plugins flow and needs neither. A remote connector that is connected anywhere is connected for the account everywhere, including inside plugins.
Other Perplexity surfaces
Perplexity says the Plugins page also exists in its desktop and mobile apps, but none of its pages says Add MCP connector works on mobile. This guide covers the web flow and the Enterprise organization flow. Add the connector on the web.
Perplexity and MCP: the facts in one table
| Topic | What Perplexity's pages say |
|---|---|
| Name | Custom remote connector, added with Add MCP connector |
| Where | Personal: Plugins, Add custom. Organization: Organization settings, Connectors, Custom connector, administrators only |
| Config file | None, it is a form. A custom plugin package can list up to 15 remote servers in mcp.json |
| Fields | A name of up to 64 characters and an https:// URL; an optional description and an icon of up to 128 KB |
| Transports | Streamable HTTP or SSE. Local commands only in the Mac app and Portable Computer |
| Sign-in | OAuth 2.0 with dynamic client registration, API Key or None. Without registration: Client ID, Client Secret and Perplexity's redirect URL |
| Headers | No custom headers, apart from two Cloudflare Access service-token headers |
| Approval | An approval card before consequential writes; Perplexity does not define consequential |
| Plan | Pro, Max and Enterprise on the changelog; the custom connectors article names none |
| Managed in | Plugins, Installed tab: status, Reconnect, Disconnect |
| Blocked by | A Web-only, Academic or Social source setting |
Sources: Perplexity: custom remote connectors, local and remote MCPs, troubleshooting connectors, installing plugins, custom plugins, Portable Computer, changelog of August 24, 2026, blog on MCP tools. Checked November 14, 2026.
Google Analytics access and scopes
Perplexity reaches GA4 through two separate sign-ins. Google decides what the Google side may read; the Ryze AI connection asks for read access only.
- Google login
- Chosen when you click Connect on the Ryze AI Google Analytics 4 card. It needs at least the Viewer role on a GA4 property. The Property you save in Ryze AI is the one the workspace uses; other properties the login can read stay reachable by naming them in the thread.
- Role in GA4
- Viewer is the lowest GA4 role that can see settings and data, and Google's own MCP server asks for the same minimum. A role can also carry No Revenue Metrics or No Cost Metrics, and Google applies those restrictions to API calls as well as the interface.
- Perplexity connector settings
- Remote connectors in Perplexity take OAuth, API Key or None. Choose OAuth for Ryze AI. In an Enterprise organization, an administrator controls who may add connectors and whether sign-in is shared or per member.
The four Google permissions
On the Google consent screen Ryze AI asks for four permissions: the read-only Google Analytics scope plus openid, email and profile. Keep every one checked. The right column shows how Google words each.
| Scope | How Google describes it |
|---|---|
| https://www.googleapis.com/auth/analytics.readonly | See and download your Google Analytics data |
| openid | Associate you with your personal info on Google |
| See your primary Google Account email address | |
| profile | See your personal info, including any personal info you've made publicly available |
What the connection can and cannot reach
The Ryze AI connection uses OAuth consent from a person. There is no API key and no service account, and you create no Google Cloud project or OAuth client. The scope and the GA4 role together set what Perplexity can read.
| Access piece | What it covers | Included for Perplexity? |
|---|---|---|
| analytics.readonly scope | Reading reports, account and property lists and Admin API settings | Yes, this is the only Google Analytics scope requested |
| Viewer role on the property | Seeing settings and data, and changing which data appears in reports | Yes, the minimum role for the login |
| analytics.edit scope | Editing Google Analytics management entities | No. Not requested, so nothing in GA4 can be created or changed |
| Marketer or Editor role | Creating audiences, events and key events, or full property settings | Not needed and not used |
| analytics.chatbot.read scope | The Ask Advisor chat method in the Data API | No. Not requested |
Out of reach: any GA4 write, such as creating or archiving key events, custom dimensions or audiences, Universal Analytics properties, and cost or revenue metrics when the Google login carries a No Cost Metrics or No Revenue Metrics restriction. The admin read tool rejects paths that would create, update or delete.
Sources: OAuth 2.0 scopes, GA4 roles and restrictions, runReport reference, accountSummaries.list, Try the Google Analytics MCP server. Checked November 14, 2026.
Removing access
To remove access, open the Google Analytics 4 card in Ryze AI and disconnect the login. In Perplexity, open Plugins, go to the Installed tab, open the Ryze AI connector and select Disconnect; Perplexity stops calling it at once. The ellipsis menu on the connector edits or removes it. Google also lists third-party access on your Google Account permissions page, where you can revoke it.
What Perplexity can do in Google Analytics
The Ryze AI connector gives Perplexity 9 Google Analytics tools, and all 9 read. Each call runs under the Google login you connected in Ryze AI.
| Tool | Type | What it does |
|---|---|---|
| google_analytics__listAccountSummaries | Read | Lists the GA4 accounts and properties the connected login can reach, so the property IDs can be found. |
| google_analytics__runRawReport | Read | Runs a GA4 Data API report with the dimensions, metrics, named date ranges, filters and ordering you ask for. |
| google_analytics__runPivotReport | Read | Runs a pivot-table report. |
| google_analytics__runRealtimeReport | Read | Runs a realtime report for the last 30 minutes. |
| google_analytics__runAdminRead | Read | Reads a GA4 Admin API resource such as key events, custom dimensions or audiences. GET only. |
| google_analytics__getAiTrafficByEngine | Read | Returns visits from AI referrers grouped by engine and compared with a prior period. |
| google_analytics__getAiTrafficDaily | Read | Returns daily visits from AI referrers such as ChatGPT and Perplexity. |
| google_analytics__getAiLandingPages | Read | Lists the top landing pages that receive AI-referred visits, up to 200 rows. |
| google_analytics__getAIReferrals | Read | Lists AI referral sources with their sessions and conversions. |
Because all 9 tools only read, no thread can alter GA4 through this connector. Perplexity says it shows an approval card before consequential writes, which these tools never reach. Since August 24, 2026 Perplexity's changelog lets a connector tool be set to Always ask; whether the panel shows for a custom connector was not confirmed. Organization administrators can set tool permissions per connector on its Base tool permissions tab.
Google Analytics limits in numbers
Google counts Data API usage in tokens per GA4 property. The figures below are for a standard property; Analytics 360 properties have higher ones. Each figure comes from the Google page named under the table.
| Limit | Figure or rule |
|---|---|
| Tokens per day | 200,000 per property on a standard property, 2,000,000 on Analytics 360. Refreshes at midnight Pacific time |
| Tokens per hour | 40,000 per property; 14,000 per Google Cloud project per property. Refreshes within an hour |
| Concurrent requests | 10 per property on standard, 50 on 360 |
| Cost of a request | Most requests cost 10 tokens or fewer. More rows, dimensions, metrics, complex filters, long ranges and high-cardinality dimensions such as pagePath cost more |
| Quota used up | Further requests to that property return 429 RESOURCE_EXHAUSTED |
| Server errors | 10 per project per property per hour on standard. Past that, requests from the project to the property are blocked |
| Rows per report | 10,000 by default and at most 250,000 per request; larger results page with an offset |
| Per report | Up to 9 dimensions. In the November 14 test the API refused 11 metrics (limit 10) and 5 date ranges (limit 4) |
| Realtime | A window of 30 minutes (60 on Analytics 360), with its own quota of the same size |
| Demographic dimensions | 120 potentially thresholded requests per property per hour |
| Data delay | Standard properties: intraday data typically 2 to 6 hours, daily data 12 hours, and processing can take 24 to 48 hours |
| Data retention | 2 or 14 months on standard properties; it affects explorations and funnel reports, not standard reports |
| Ryze AI tool inputs | AI landing pages: at most 200 rows. Raw reports default to 10,000 rows. Property ID 1 to 64 characters. AI-traffic tools take dates as YYYY-MM-DD |
| Perplexity | Connector names up to 64 characters. No printed cap on connectors or tools |
Sources: Data API quotas, runReport reference, create a report, realtime basics, Data API changelog, data freshness, data retention, Perplexity: custom remote connectors. Checked November 14, 2026.
Google Analytics calls through the connector, tested
On November 14, 2026, Claude Code sent eight Google Analytics 4 calls to the live Ryze AI connector, at the same address this guide gives Perplexity. Two were meant to return data and six to be refused. The property belongs to a real test workspace, so no name, ID or figure is shown.
| Request | Tool | Google Analytics answered |
|---|---|---|
| List accounts and properties | google_analytics__listAccountSummaries | Worked. Each property came with its display name, type, parent and a canEdit flag |
| One day, one metric (sessions), with the quota block requested | google_analytics__runRawReport | Worked. Returned a row, the currency and time zone, and a propertyQuota block; the value is withheld |
| A dimension that does not exist | google_analytics__runRawReport | HTTP 400 INVALID_ARGUMENT, with a suggested name |
| A metric that does not exist | google_analytics__runRawReport | HTTP 400 INVALID_ARGUMENT, with a suggested name |
| A property ID that does not exist | google_analytics__runRawReport | Refused with status not_allowed |
| 10 dimensions in one report | google_analytics__runRawReport | HTTP 400 INVALID_ARGUMENT |
| 5 date ranges in one report | google_analytics__runRawReport | HTTP 400 INVALID_ARGUMENT |
| 11 metrics in one report | google_analytics__runRawReport | HTTP 400 INVALID_ARGUMENT |
The report returned a propertyQuota block whose totals equal Google's standard-property limits. Google's quota page prints the same example numbers, so this test does not show the property's live usage.
First 3 prompts to run
The prompts describe what each one asks for. Answers come from your own property, so this page shows no sample numbers.
1. Find your properties and compare two months
Using the Ryze AI connector, list the GA4 properties I can read, then for the first one compare sessions, key events and revenue by default channel group for last month against the month before.
Tools used: google_analytics__listAccountSummaries, google_analytics__runRawReport
What comes back: A list of properties with their IDs, then one report with the two date ranges named, split by channel group. Revenue shows as zero if ecommerce tracking is not set up in GA4.
2. See which AI assistants send visits
Using the Ryze AI connector, show which AI assistants sent visits in the last 30 days against the 30 days before, and list the landing pages those visits arrived on.
Tools used: google_analytics__getAiTrafficByEngine, google_analytics__getAiLandingPages
What comes back: Visits from AI referrers grouped by engine with a prior-period comparison, then the top landing pages for AI-referred visits, up to 200 rows.
3. Check what is configured in the property
Using the Ryze AI connector, list the key events and custom dimensions set up in this GA4 property.
Tools used: google_analytics__runAdminRead
What comes back: Key events and custom dimensions read from the Admin API. The call is GET only, so nothing in the property changes.
Name the property in the prompt or let Perplexity look it up first. The tools take a property ID and pick none on their own. They cannot edit GA4, so these prompts are safe to try.
10 jobs to hand to Perplexity
Ten jobs for Perplexity, each with its tool. Name Ryze AI in the request or pick it with @. The account list and a core report ran in the test; the other tools were read from their definitions and not called.
| Job | Ask Perplexity | Tool | Works on the default connection |
|---|---|---|---|
| Property list | Which GA4 accounts and properties can this login read? Give me the IDs. | google_analytics__listAccountSummaries | Yes, ran in the test |
| Channel comparison | Sessions, key events and revenue by default channel group, last month against the month before. | google_analytics__runRawReport | Yes. Up to 4 date ranges, 9 dimensions and 10 metrics per report |
| Landing pages | Top landing pages by sessions with engagement rate and key event rate for the last 28 days. | google_analytics__runRawReport | Yes |
| Revenue by source | Purchase revenue and purchases by source and medium. | google_analytics__runRawReport | Yes. Zero without ecommerce tracking, and hidden by a No Revenue Metrics role |
| Pivot | A pivot of sessions by channel across device categories. | google_analytics__runPivotReport | Yes, read tool |
| Right now | Who is on the site now by country and device? | google_analytics__runRealtimeReport | Yes, last 30 minutes only |
| Property setup | List the key events, custom dimensions and audiences in this property. | google_analytics__runAdminRead | Yes, GET only |
| AI engines | Which AI assistants sent visits in the last 30 days against the 30 days before? | google_analytics__getAiTrafficByEngine | Yes, read tool |
| AI visits by day | Daily visits from ChatGPT and Perplexity over the last month. | google_analytics__getAiTrafficDaily | Yes, read tool |
| AI landing pages and sources | Landing pages that receive AI-referred visits, and each AI referral source with sessions and conversions. | google_analytics__getAiLandingPages, google_analytics__getAIReferrals | Yes, read tools |
Not possible: creating, editing or deleting properties, key events, audiences or any GA4 setting, reading Universal Analytics, and measuring whether an AI assistant mentions a brand. GA4 reports visits that arrive from AI assistants and nothing else.
3 ways to connect Perplexity to Google Analytics
Perplexity on the web takes remote connectors at an https address, and only its desktop software starts local commands. Two other GA4 routes come from vendors whose pages name Perplexity. The Ryze AI connector is the main way: one Google approval, one address and 9 read tools, including four for visits from AI assistants. Windsor.ai and Coupler.io were not tried in Perplexity. All vendor pages were read on November 14, 2026.
| Way | Runs where | Setup for Perplexity | What it reaches in GA4 | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted, one address for every user. The same address works in Claude, ChatGPT and other MCP clients | Add MCP connector, Remote, the address, OAuth. Sign in from the card | Data API reports, pivots, realtime, Admin API reads, and four AI-traffic tools. Read only | Paid Ads $89 per month, 7-day free trial. Connector free |
| Windsor.ai (Windsor MCP) | Hosted by Windsor.ai | Connect GA4 as a data source in Windsor.ai, then add its connector. Windsor lists a Perplexity guide; it was not opened for this page | Read access to GA4 data, which Windsor describes as read-only. 350+ sources in total | Forever Free after a 30-day trial, 1 data source. Basic $23 per month |
| Coupler.io Google Analytics MCP | Hosted by Coupler.io. The assistant queries a synced copy of GA4, not GA4 itself | Build a GA4 data flow with a refresh schedule, then choose Perplexity as the AI integration | Read-only. Up to 10 metrics and 9 dimensions per data flow; scheduled refresh | Free forever with manual refresh, 1 data source. Starter $32 per month |
Six Google Analytics options that do not fit Perplexity
- Google's analytics-mcp 1.1.0. An open-source server that calls the Admin API and Data API. It runs on your computer, started by the assistant, with Application Default Credentials, a Google Cloud project with both APIs enabled and the Viewer role. Google's docs page names Antigravity, Claude Desktop, Claude Code and Cursor, and the README adds Gemini CLI and Gemini Code Assist. Neither names Perplexity. It is read-only by default; opt-in write tools came with 0.8.0 and 1.1.0 behind an --allow-write flag. Since 1.0.0 it can also run as a multi-user HTTP server you host yourself. Google gives no Perplexity steps for either mode.
- Composio. Hosted, with 82 tools for reading and writing GA4 on its toolkit page. Its assistant pages name Claude Code, ChatGPT, Cursor, Codex, Antigravity, VS Code, Grok Bot and others, but not Perplexity. Free plan: 10,000 tool calls per month.
- Zapier MCP. Six GA4 actions, among them Run Report for a Property, Create Conversion Event and API Request, at 2 tasks per successful call. Zapier says any Streamable HTTP client works, yet its client lists leave Perplexity out.
- surendranb/google-analytics-mcp. A free, MIT-licensed local server with 8 read tools. Its README gives setup for Claude Code, Claude Desktop, Cursor, Antigravity and VS Code extensions, and a service account file for the Claude Desktop example. 244 GitHub stars on November 14, 2026.
- Google Analytics agent skills. Instruction files for coding agents that write Data API or Admin API code. They carry no data connection.
- Ask Advisor chat method. A Data API v1alpha method for code to put a question to the Ask Advisor assistant inside Google Analytics. It is an API route, not a connector for Perplexity.
Which one to pick
Ryze AI is the best way to connect Perplexity to Google Analytics when one thread should read reports and visits from AI assistants through a single https address with OAuth, with two caveats: the tools need an active Ryze AI plan or trial, and they only read. Windsor.ai suits GA4 next to many other sources. Coupler.io suits scheduled, read-only questions on synced data. Google's analytics-mcp suits an assistant Google names, such as Claude Code or Cursor, when you are happy to run Python tooling and Google Cloud credentials yourself. Perplexity's Discover tab also lists prebuilt connectors; this page did not check whether one covers Google Analytics.
The Ryze AI row follows the Ryze AI Google Analytics guide.
Sources: Try the Google Analytics MCP server, analytics-mcp on GitHub, agent skills, Ask Advisor, Windsor MCP, Windsor.ai for GA4, Windsor.ai pricing, Coupler.io, Coupler.io pricing, Composio, Composio pricing, Zapier MCP, Zapier MCP quickstart, surendranb/google-analytics-mcp, Perplexity: custom remote connectors, installing plugins. Checked November 14, 2026.
Perplexity, Google Analytics and MCP: dates that matter
| Date | What happened |
|---|---|
| May 6, 2024 | The GA4 Data API introduced key event metrics. conversions became a deprecated metric name and keyEvents replaced it. |
| July 30, 2025 | The Google Analytics team announced its open-source Google Analytics MCP Server. |
| March 12, 2026 | Perplexity shipped Bring Your Own Connector: custom remote connectors by URL for Pro, Max and Enterprise. |
| August 24, 2026 | Perplexity's changelog added a per-tool Always ask setting for connectors. |
| October 14, 2026 | Perplexity's blog on MCP tools restated the Pro, Max and Enterprise plan list. |
| October 22, 2026 | analytics-mcp 0.8.0 added its first write tool and the --allow-write flag. |
| November 3, 2026 | analytics-mcp 1.0.0 added a multi-user Streamable HTTP transport and OAuth 2.1, and left experimental status. |
| November 6, 2026 | analytics-mcp 1.1.0 added Cloud Run docs and opt-in Admin API write tools. The same day Perplexity's changelog announced Agent Plugins and the Plugins page. |
| November 10, 2026 | Google's page on its MCP server was last updated. It lists Antigravity, Claude Desktop, Claude Code and Cursor and says Gemini CLI is deprecated. |
| November 14, 2026 | The Ryze AI connector test for this page ran, and both fact packs were re-read. |
Sources: Data API changelog, Google Analytics API announcement, analytics-mcp releases, Try the Google Analytics MCP server, changelog of March 12, 2026, changelog of August 24, 2026, blog on MCP tools, changelog of November 6, 2026, Perplexity: custom remote connectors. Checked November 14, 2026.
How this guide was tested
The live Ryze AI connector was checked on November 14, 2026, with calls sent from Claude Code to the same address this guide gives Perplexity. Every call was read-only.
| What was run | What came back |
|---|---|
| Tool list | All 9 Google Analytics tool names loaded by exact name and each returned a definition. None contains a write verb. |
| Schema checks | Every tool takes a workspace and an optional connection_id. All but the account list and the admin read need a property ID, and no property is chosen automatically. |
| Two reads | The account and property list and a one-day, one-metric report worked. Their contents are withheld. |
| Six planned failures | A made-up dimension, a made-up metric, a property ID that does not exist, 10 dimensions, 5 date ranges and 11 metrics, each refused with the errors below. |
| Quota block | The report returned a propertyQuota block that equals the standard-property limits. It is not shown as test output. |
| Google's own endpoints | Without credentials, Google's Data API MCP address answered with 4 read-only tools and its Admin address with 12. No authenticated call was made to either. |
Not run: anything inside Perplexity. No connector was added, no sign-in completed and no tool called from a Perplexity thread, on any plan; those steps follow Perplexity's help center as read on November 14, 2026. The pivot, realtime, admin read and four AI-traffic tools were not called because they return data from a real account. No quota was exhausted and no row limit above 250,000 was tried. Windsor.ai, Coupler.io and Google's own server were not tried.
Errors and fixes
Exact Google Analytics messages from the test
Copied from the Google Analytics answers of November 14, 2026. Data API refusals reach the assistant as Error 400 with Google's JSON error inside.
| Message | What it means | What to do in Perplexity |
|---|---|---|
| Did you mean manualSource? Field trafficSauce is not a valid dimension. | The dimension name does not exist in the Data API. Google suggests the closest name. | Ask Perplexity to retry with a real dimension such as sessionSource. |
| Did you mean sessions? Field sessionz is not a valid metric. | The metric name does not exist. Note that conversions is a deprecated name; the current one is keyEvents. | Use the suggested metric name. |
| User does not have sufficient permissions for this property. | Returned with status not_allowed. The property ID does not exist, or the login has no role on it. Google answers the same way in both cases. | Have Perplexity run listAccountSummaries for the IDs the login can read, or ask a property admin for the Viewer role. |
| Requests are limited to 9 dimensions within a nested request. | One report can break data down by at most 9 dimensions. | Ask for fewer breakdowns, or split the question into two reports. |
| Requests are limited to 10 metrics within a nested request. | One report can carry at most 10 metrics. This cap is known only from the test answer; Google's pages opened for this guide do not print it. | Ask for 10 metrics or fewer, or run two reports. |
| Requests are limited to 4 dateRanges. | One report can compare at most 4 date ranges. Also known only from the test answer. | Compare up to 4 periods, or use a date dimension over one longer range. |
Two more errors appear on Google's errors page and were not triggered in the test: 429 RESOURCE_EXHAUSTED, which means a quota ran out, and 401 UNAUTHENTICATED, which means the credentials are not valid.
Other problems
- Add MCP connector is missing in Perplexity
- Check your plan. Perplexity's changelog names Pro, Max and Enterprise for custom remote connectors. In an Enterprise organization, ask an administrator to switch on Allow members to add custom connectors, or to add the connector for everyone.
- The Add button stays unavailable
- Fill in the name, the whole https address and the acknowledgement checkbox.
- The connector is added but does nothing
- Select its card on the Plugins page to start the Ryze AI sign-in and enable it. In an organization, a new connector starts switched off until an administrator turns it on.
- The sign-in window never opens
- Connector sign-in needs pop-ups and cross-site cookies for perplexity.ai. Allow both, then select the card again.
- The Google Analytics tools do not load
- First check that the Google Analytics 4 card in Ryze AI shows a saved Property rather than Require setup. If the connector was added before GA4 was connected, disconnect it under Plugins, Installed and add it again, then open a new thread. The Ryze AI help center gives this advice for Claude and ChatGPT, which cache the tool list; Perplexity's pages do not say whether it does the same.
- Perplexity never calls Ryze AI
- A Web-only, Academic or Social source setting stops connector calls. Change it and name Ryze AI in the request.
- It works in my own account but not in the company workspace
- A personal connector does not carry into an Enterprise workspace or a Project. Add Ryze AI there too.
- Sign-in fails with API Key selected
- Use OAuth. The form has no field for custom request headers, and Perplexity's documentation does not say which header the API Key option sends.
- Perplexity asks for a client ID and secret
- It asks for them only for OAuth servers without dynamic client registration. Ryze AI supports dynamic client registration, so leave them empty. If a server needs a redirect URL, Perplexity's is https://www.perplexity.ai/rest/connections/oauth_callback, or https://enterprise.perplexity.ai/rest/connections/oauth_callback for organizations on the Enterprise subdomain.
- A property is missing from the results
- Ryze AI sees only the properties the connected Google login can read. Attach another login through Add one more account on the card, or ask a property admin for the Viewer role.
- Revenue shows as zero
- GA4 reports revenue as zero until ecommerce tracking and purchase events are set up. A login with the No Revenue Metrics restriction also gets none.
- Recent numbers look low
- Standard properties can take 24 to 48 hours to process data, and Google says reports may change in that time. Ryze AI cannot shorten it.
- Perplexity says a subscription is required
- The tools sit behind an active Ryze AI plan or free trial. Start the trial, then ask again.
Sources: troubleshooting connectors, Perplexity: custom remote connectors, Data API errors. Checked November 14, 2026.
Terms on this page
- Custom remote connector
- Perplexity's name for an MCP server you add by its https address.
- Dynamic client registration
- An OAuth feature Perplexity uses when a server offers it. The Ryze AI connector supports it, so no Client ID or Client Secret is typed in.
- Property and property ID
- The unit of GA4 that reports are produced for. Every Data API request names a numeric property ID, shown under Admin, Property Settings. Universal Analytics properties do not work.
- Key event
- GA4's name for an action that matters to the business, formerly called a conversion. In the API the metric is keyEvents.
- Dimension and metric
- Metrics are measurements such as active users or event count. Dimensions break them down by criteria such as country or event name.
- Token
- The unit Google charges per report request. A standard property has 200,000 per day and 40,000 per hour.
- Viewer role
- The lowest GA4 role that can see settings and data. It is the minimum the Ryze AI connection needs.
Sources: Perplexity: custom remote connectors, property ID, key events, dimensions and metrics, Data API quotas, GA4 roles. Checked November 14, 2026.
Frequently asked questions
How do I connect Perplexity to Google Analytics?
Connect Google Analytics 4 in a Ryze AI workspace: open Integrations, click Connect on Google Analytics 4, approve every permission and save a Property. Then in Perplexity open Plugins, Add custom, Add MCP connector, Remote, enter https://connector.get-ryze.ai/mcp, set Authentication to OAuth and select Add. Select the connector card to sign in.
Does Perplexity have a Google Analytics connector?
Perplexity lets Pro, Max and Enterprise subscribers add a custom remote MCP connector by URL, and the Ryze AI connector is one you can add that way. Perplexity also lists prebuilt connectors; this page did not verify one for Google Analytics.
What is the Google Analytics MCP server URL for Perplexity?
For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, the same for every user, entered as a remote connector with OAuth. Google's own analytics-mcp runs on your computer, and Google's docs name Claude, Cursor and Antigravity for it, not Perplexity.
Does Google have an official Google Analytics MCP server?
Yes, analytics-mcp, an open-source server from the Google Analytics team. Version 1.1.0 of November 6, 2026 calls the Admin API and Data API, runs as a local command, and has an optional multi-user HTTP mode you host yourself. It is read-only by default, and its pages do not name Perplexity.
Is there a free Google Analytics MCP connector for Perplexity?
Adding the Ryze AI connector costs nothing, though its tools need an active Ryze AI plan or the 7-day free trial of Paid Ads. Coupler.io has a free plan with one data source and manual refresh, and Windsor.ai has a Forever Free plan with one data source after a 30-day trial. Both name Perplexity; neither was tried for this page.
Which Google Analytics connector should I use with Perplexity?
It depends on the job. The Ryze AI connector gives live GA4 reports and visits from AI assistants through one address, with the caveat that it needs a Ryze AI plan or trial. Coupler.io fits scheduled read-only questions on synced data, and Windsor.ai fits GA4 next to other sources. Google's own server does not name Perplexity.
Which Perplexity plan do I need?
Perplexity's March 2026 changelog says Pro, Max and Enterprise subscribers can add a custom remote connector. In an Enterprise organization, members need an administrator to switch on Allow members to add custom connectors, which starts off.
Can Perplexity change my Google Analytics settings?
No. All 9 tools read and the connection requests only the analytics.readonly scope, so Perplexity cannot create, edit or delete properties, key events, audiences or other GA4 settings. The admin read tool rejects create, update and delete paths.
Can Perplexity see which AI assistants send visits to my site?
Yes, as visits that arrive from AI referrers such as ChatGPT and Perplexity: by engine against a prior period, by day, by landing page and by referral source with sessions and conversions. GA4 does not measure whether an assistant mentions your brand.
Which authentication option should I pick?
Pick OAuth, with Streamable HTTP and Public network access. Ryze AI supports dynamic client registration, so no client ID or secret is needed. The form has no field for custom headers, so the API Key option does not fit.
Can my whole Enterprise organization use it?
Yes. An administrator opens Organization settings, Connectors, adds a Custom connector, switches it on and chooses between one organization sign-in and a sign-in for each member.
Can I use more than one GA4 property or account?
Yes. Several Google logins can be connected to one workspace with Add one more account, each with its own Property, and one is the primary. Tools accept an optional connection_id, and other properties can be reached by naming them in the thread. Keep separate clients in separate workspaces.
Why do the Google Analytics tools not show up in Perplexity?
Check that the Google Analytics 4 card in Ryze AI has a saved Property. If the connector was added before GA4 was connected, disconnect it under Plugins, Installed, add it again and open a new thread.
Why does Perplexity say the property does not exist or I lack permission?
Google returns the message User does not have sufficient permissions for this property both for an ID that does not exist and for a login with no role on the property. Ask Perplexity to run the account list for valid IDs, or get the Viewer role from a property admin.
How much does it cost to connect Perplexity to Google Analytics?
The connection costs nothing, while the Google Analytics tools run only on an active Ryze AI plan or trial. Paid Ads is $89 per month with a 7-day free trial. SEO Starter is $129 per month with a 3-day free trial. Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Google Analytics from Perplexity?
Open the Ryze AI connector under Plugins, Installed in Perplexity and select Disconnect, or remove it from its ellipsis menu. To cut GA4 off at the source, disconnect the login on the Google Analytics 4 card in Ryze AI or revoke access on your Google Account permissions page.