Any MCP-compatible appRead live data
- Sessions, users, engagement and conversions
- Channels, sources, mediums and campaigns
- Landing pages, page paths and events
- Ecommerce revenue, purchases and ROAS
Connect once, use it two ways
Connect Google Analytics 4 to Jepto once. What you build in Jepto and what you ask in Claude or ChatGPT read the same data, so the numbers match wherever you look.
Add the Jepto MCP server and ask about Google Analytics 4 in plain English, across all your brands. Included on every plan.
and any MCP-compatible appJepto runs a hosted GA4 MCP server at mcp.jepto.com. Connect it once and Claude, ChatGPT, Cursor or any MCP-compatible app can query 60 Google Analytics 4 fields across every property you manage, next to your ad platforms. There's nothing to install and no Google Cloud project to set up. It reads your GA4 data and never changes it.
Paste the URL into your AI assistant, or find Jepto in Claude's connector directory or ChatGPT's Plugins page. Sign in to Jepto once and every conversation can use your live Google Analytics 4 data.
Works with
OAuth sign-in. Each person sees only the brands their Jepto login can.
Your assistant shows a preview. Nothing saves until you confirm.
Nothing. The Jepto MCP reads your Google Analytics 4 data and never changes it.
Paste one into Claude or ChatGPT once Jepto is connected. Swap [brand] for one of yours.
“Which landing pages lost the most organic sessions this month compared with last?”
“What's [brand]'s engagement rate and conversion rate by default channel group for the last 30 days?”
“Compare Google Ads clicks with GA4 sessions from google / cpc by day for the last two weeks.”
“Which session campaigns drove the most purchase revenue last month?”
“Compare mobile and desktop conversion rate over the last 90 days.”
“Set a monthly KPI of 500 conversions in GA4 for [brand] and tell me if we're on track.”
Google's own server is a good fit for one analyst exploring one property. Jepto suits teams that need every property, plus the ad spend that drove the traffic, in the same answer.
| Compared on | Jepto MCP | Google's official Google Analytics MCP | Community servers |
|---|---|---|---|
| Setup | Hosted. Paste one URL, or pick Jepto in the Claude or ChatGPT directory, then sign in. | Install it locally and set up Google Cloud credentials. | You install, host and update it, and supply your own API credentials. |
| Accounts | Every Google Analytics 4 account you've connected, across all your brands, in one connection. | Properties your Google login can reach. | Usually one login or token at a time. |
| Other channels | Ask across Google Analytics 4 and every other connected source in the same question. | Google Analytics only. | One platform per server. You combine servers yourself. |
| Brand context | Reads each brand's details and knowledgebase, so answers reflect what the business sells and what it's aiming for. | None. | None. |
| Field guidance | Ships a Google Analytics 4 guide the AI reads first: which numbers add up, which don't, and what isn't available. | Raw Data API reports. The AI builds them. | Raw API fields. The AI works out what they mean. |
| Changes | Read-only in GA4. KPI targets in Jepto can be set from chat, with a confirm step. | Reads reports and property settings. | Varies. Some write to your account with no confirm step. |
| Cost | Included on every Jepto plan, with no usage limits. | Free. You run it. | Free code. Your time to run and maintain it. |
Every Google Analytics 4 metric and dimension in the Jepto data model, with its definition. Each one works the same way in Reports, Data Chat and the Jepto MCP.
| How you connect | Sign in with Google. You need access to the GA4 property. |
| Levels | Property, traffic source, page, event, location, device and browser, date and time |
| Use it in | Reports, Data Chat, KPI forecasting, anomaly alerts and the Jepto MCP |
| AI assistants | Claude, ChatGPT, Cursor and any MCP client, at https://mcp.jepto.com |
| Changes from chat | None. The MCP reads your data and never changes it |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Active usersgoogleAnalytics4.activeUsers | Active users. Users who had an engaged session, or when Analytics collected first_visit or engagement_time from a page. | Metric | number | Maximum | — |
Total usersgoogleAnalytics4.totalUsers | Users who logged at least one event, new or returning. | Metric | number | Maximum | — |
New usersgoogleAnalytics4.newUsers | Users who interacted with your site or app for the first time. | Metric | number | Maximum | — |
SessionsgoogleAnalytics4.sessions | Periods when users are actively engaged with your site or app. | Metric | number | Sum | — |
Sessions per usergoogleAnalytics4.sessionsPerUser | Average number of sessions per user. | Metric | number | Sum | — |
Engaged sessionsgoogleAnalytics4.engagedSessions | Sessions that lasted longer than 10 seconds, had a conversion event, or had at least 2 page views. | Metric | number | Sum | — |
Page viewsgoogleAnalytics4.screenPageViews | Total count of screen or page views recorded. | Metric | number | Sum | — |
EventsgoogleAnalytics4.eventCount | Count of event instances recorded. | Metric | number | Sum | — |
Item viewsgoogleAnalytics4.itemViews | Total count of item views recorded. | Metric | number | Sum | — |
Ad clicksgoogleAnalytics4.advertiserAdClicks | Number of clicks on your ads. | Metric | number | Sum | — |
Ad impressionsgoogleAnalytics4.advertiserAdImpressions | Number of times your ads were displayed to users. | Metric | number | Sum | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Event valuegoogleAnalytics4.eventValue | Total monetary value attributed to user interactions with your site or app. | Metric | number | Sum | Currency |
Total ad costgoogleAnalytics4.totalAdCost | Total amount spent on linked ads (e.g. Google Ads), in your account currency. | Metric | number | Sum | Currency |
Ad CPCgoogleAnalytics4.advertiserAdCostPerClick | Average cost per click on your ads, calculated as total ad cost divided by clicks. | Metric | number | Average | Currency |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Avg. session durationgoogleAnalytics4.averageSessionDuration | Average duration of each session in seconds. | Metric | number | Average | Decimal (×) |
Bounce rategoogleAnalytics4.bounceRate | Percentage of sessions that were not engaged sessions: non-engaged sessions ÷ total sessions. | Metric | number | Average | Percentage |
ROASgoogleAnalytics4.returnOnAdSpend | Return on ad spend: attributed revenue divided by ad cost. | Metric | number | Average | Decimal (×) |
Ad CTRgoogleAnalytics4.advertiserAdCtr | Click-through rate for linked ads: ad clicks ÷ ad impressions. | Metric | number | Calculated: Ad clicks ÷ Ad impressions | Percentage |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Add-to-cartsgoogleAnalytics4.addToCarts | Number of times users added items to their shopping cart. | Metric | number | Sum | — |
Items purchasedgoogleAnalytics4.itemsPurchased | Number of items purchased by users. | Metric | number | Sum | — |
Purchase revenuegoogleAnalytics4.purchaseRevenue | Total revenue generated from purchases, in your account currency. | Metric | number | Sum | Currency |
Total revenuegoogleAnalytics4.totalRevenue | Total revenue across all transaction types recorded, in your account currency. | Metric | number | Sum | Currency |
Transactions per purchasergoogleAnalytics4.transactionsPerPurchaser | Average number of transactions per user who made a purchase. | Metric | number | Sum | — |
Avg. purchase revenuegoogleAnalytics4.averagePurchaseRevenue | Average revenue generated per purchase transaction. | Metric | number | Sum | Currency |
Purchaser rategoogleAnalytics4.purchaserRate | Percentage of active users who made a purchase: purchasers ÷ active users. | Metric | number | Average | Percentage |
ConversionsgoogleAnalytics4.conversions | Number of completed conversion actions you are measuring (e.g. purchases, sign-ups, leads). | Metric | number | Sum | — |
Conversion rategoogleAnalytics4.conversionRate | Percentage of sessions that resulted in a conversion: conversions ÷ sessions. | Metric | number | Calculated: Conversions ÷ Sessions | Percentage |
Cost per conversiongoogleAnalytics4.adCostPerConversion | Average ad spend per conversion: total ad cost ÷ conversions. | Metric | number | Calculated: Total ad cost ÷ Conversions | Currency |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Engagement rategoogleAnalytics4.engagementRate | Percentage of sessions that were engaged (lasted 10+ seconds, had a conversion, or had 2+ page views): engaged sessions ÷ total sessions. | Metric | number | Average | Percentage |
User engagement durationgoogleAnalytics4.userEngagementDuration | Total time users spent engaged with your site or app, in seconds. | Metric | number | Average | Decimal (×) |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
DategoogleAnalytics4.date | Calendar date for the report row. | Dimension | string | — | — |
ISO year + weekgoogleAnalytics4.isoYearIsoWeek | ISO year and week number for the report row (e.g. 202305 = week 5 of 2023). | Dimension | string | — | — |
YeargoogleAnalytics4.year | Year of the report row. Used when reporting is grouped by calendar year. | Dimension | string | — | — |
Year + monthgoogleAnalytics4.yearMonth | Year and month of the report row (YYYYMM). | Dimension | string | — | — |
MonthgoogleAnalytics4.month | Month of the report row (01–12). | Dimension | string | — | — |
WeekgoogleAnalytics4.week | Week of the year (01–53). | Dimension | string | — | — |
Date + hourgoogleAnalytics4.dateHour | Date and hour. Combined date and hour (YYYYMMDDHH). | Dimension | string | — | — |
Date + hour + minutegoogleAnalytics4.dateHourMinute | Date, hour, and minute of the report row (YYYYMMDDHHmm). | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Session sourcegoogleAnalytics4.sessionSource | Traffic source that brought the session (e.g. google, direct, newsletter). | Dimension | string | — | — |
Session mediumgoogleAnalytics4.sessionMedium | Traffic medium for the session (e.g. cpc, organic, email). | Dimension | string | — | — |
Session campaigngoogleAnalytics4.sessionCampaignName | Campaign name that brought the session. | Dimension | string | — | — |
Default channel groupgoogleAnalytics4.sessionDefaultChannelGroup | Marketing channel group for the session (e.g. Paid Search, Organic). | Dimension | string | — | — |
First user sourcegoogleAnalytics4.firstUserSource | Traffic source that first acquired the user (e.g. google, direct). | Dimension | string | — | — |
First user mediumgoogleAnalytics4.firstUserMedium | Traffic medium through which the user was first acquired (e.g. cpc, organic). | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Page pathgoogleAnalytics4.pagePath | Path portion of the page URL. | Dimension | string | — | — |
Page titlegoogleAnalytics4.pageTitle | HTML document title of the page as collected by Google Analytics. | Dimension | string | — | — |
Landing pagegoogleAnalytics4.landingPage | Page path where the session began. | Dimension | string | — | — |
Page path / screen namegoogleAnalytics4.unifiedPagePathScreen | Unified path for both web pages and app screens. | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
CountrygoogleAnalytics4.country | Country associated with user activity. | Dimension | string | — | — |
RegiongoogleAnalytics4.region | Geographic region for user activity. | Dimension | string | — | — |
CitygoogleAnalytics4.city | City associated with user activity. | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Device categorygoogleAnalytics4.deviceCategory | Desktop, mobile, or tablet. | Dimension | string | — | — |
PlatformgoogleAnalytics4.platform | Platform used for the session (Web, iOS, Android). | Dimension | string | — | — |
Platform + devicegoogleAnalytics4.platformDeviceCategory | Platform and device category combined (e.g. web / mobile, iOS / tablet). | Dimension | string | — | — |
BrowsergoogleAnalytics4.browser | Web browser used for the session. | Dimension | string | — | — |
Operating systemgoogleAnalytics4.operatingSystem | Operating system of the device used in the session (e.g. Windows, iOS, Android). | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
Currency codegoogleAnalytics4.currencyCode | Currency code for the transaction data. | Dimension | string | — | — |
Event namegoogleAnalytics4.eventName | Name of the collected event. | Dimension | string | — | — |
Reports, Data Chat, forecasts and alerts all use the same Google Analytics 4 fields listed above.
Describe the report you want and Jepto builds it from your Google Analytics 4 data, then writes an analysis of what changed and why.
Explore reportingAsk questions about your Google Analytics 4 data in plain English and get answers, tables and charts back in seconds.
Explore Data ChatSet a target on any Google Analytics 4 metric and see where the month is likely to finish, while there's still time to act.
Explore KPI forecastingAdd an anomaly alert to the Google Analytics 4 metrics you care about, and Jepto tells you when one moves outside its normal range.
Explore anomaly detectionSign in with a Google account that has access to the GA4 property.
In Jepto, add a Google Analytics 4 connection and sign in with a Google account that has access to the property.
Select the GA4 property you want to report on. Add another connection for each additional property.
Your data is ready in Reports and Data Chat. Connect https://mcp.jepto.com to your AI assistant to ask about it from there too.
About Google Analytics 4 in Jepto and the Jepto MCP.
Yes. Jepto hosts an MCP server at https://mcp.jepto.com that gives Claude, ChatGPT, Cursor and other MCP-compatible apps access to your Google Analytics 4 data. There's nothing to install: you sign in to Jepto with OAuth, and the assistant can query every GA4 field in the Jepto data model.
Yes. Google publishes an open-source Google Analytics MCP server that runs on your own computer with Google Cloud credentials. Jepto's server is hosted, covers every GA4 property you've connected in one connection, and lets one question span GA4 and your ad platforms.
Jepto includes GA4 metrics such as Active users, Total users, New users, Sessions, Sessions per user, Engaged sessions, Page views and Events. You can break them down by dimensions for Date & time, Traffic source, Page & content, Location, Device & placement and Segments. Every field, with its definition, is listed on this page.
No. Through the Jepto MCP, GA4 data is read-only: the assistant can query it but can't change anything in GA4.
Yes. When both are connected to the same brand, any report or chart can use fields from either source, and Data Chat and the Jepto MCP can answer questions that span the two. GA4 also includes linked ad metrics such as Total ad cost, Ad clicks and ROAS.
Yes. Page path, page title, landing page and page path / screen name are all dimensions, so you can break sessions, engagement and conversions down by page.
No. You connect Google Analytics 4 to Jepto by signing in, and Jepto handles the API access. Your AI assistant then connects to Jepto at https://mcp.jepto.com.
Yes. Every Google Analytics 4 account connected to Jepto, across all your brands, is available through the one connection. What each person can see follows their Jepto login.
No. The Jepto MCP is included on every plan with no usage limits. Check that your AI assistant's plan lets you add connectors.
Related Articles
Start asking your data smarter questions today. Connect your first data source in minutes.
