Google Analytics API

Name: Google Analytics API
Brand: Google Analytics API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb Analyticsoauth288 EndpointsREST

For Agents

Read historical Universal Analytics report data and manage UA accounts, properties, views, goals, and filters across 88 endpoints.

Install Jentic One Beta

Connect the Google Analytics API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Analytics API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Analytics API.

Run Core Reporting queries against historical Universal Analytics data with dimensions and metrics

Run Multi-Channel Funnels (MCF) reports for attribution analysis on historical sessions

Manage UA accounts, web properties, and profiles (views) including their hierarchical relationships

GET STARTED

Start building with Google Analytics API

Explore with Jentic

View OpenAPI Document

The Google Analytics API v3 (Universal Analytics) exposes both reporting and management for Universal Analytics properties — the predecessor to GA4. It covers the Core Reporting API, Multi-Channel Funnels (MCF), Real Time, and the Management API for accounts, web properties, profiles (views), goals, filters, and user permissions. Universal Analytics stopped processing new data in 2023, so this API is now used primarily to read historical data and to manage legacy property metadata. New analytics work should target the GA4 Admin and Data APIs.

Use Cases

Patterns agents use Google Analytics API for, with concrete tasks.

★ Historical Universal Analytics Reporting

Teams that ran Universal Analytics for years still need to query that history for year-over-year comparisons even after migrating to GA4. The Core Reporting endpoint /data/ga returns dimensions and metrics for a specified UA view ID and date range, and Multi-Channel Funnels at /data/mcf returns attribution paths. This is the only programmatic surface for UA historical data — GA4's Data API does not cover UA properties.

GET /data/ga with ids=ga:{viewId}, start-date and end-date, dimensions=ga:source,ga:medium and metrics=ga:sessions,ga:pageviews and write the rows to a warehouse table.

UA Property Inventory and Cleanup

Organisations migrating to GA4 need a clean inventory of every UA account, property, and view, and a way to revoke obsolete user access during sunset. /management/accountSummaries returns the full hierarchy in one call. The accounts, webproperties, profiles, and entityUserLinks paths support listing and (where allowed) updating these resources.

GET /management/accountSummaries and write the account, webPropertyId, and profileId tree to a CSV, then call entityUserLinks to list current users on each.

Goal and Filter Audit

Before retiring a Universal Analytics property, teams want to capture every goal and filter definition for institutional knowledge. The Management API exposes goals and filters per profile or account. A script can iterate accounts, properties, and views, capture the configured goals and filters, and store them as JSON for the GA4 migration team to translate.

List accounts, then iterate webProperties and profiles, calling /management/accounts/{accountId}/webproperties/{webPropertyId}/profiles/{profileId}/goals and the filters endpoint to capture every definition.

Agent Pull of Historical UA Reports

An agent integrating the Google Analytics v3 API through Jentic can run Core Reporting queries against historical UA data and answer questions about long-term trends. Jentic stores the OAuth credential and exposes the report request schema, so the agent does not have to write the OAuth dance or learn UA's metric and dimension naming by hand.

Use the Jentic search query 'run a Universal Analytics core reporting query' to discover /data/ga, then call it for a UA view ID with the requested dimensions, metrics, and date range.

Key Endpoints

88 endpoints — the google analytics api v3 (universal analytics) exposes both reporting and management for universal analytics properties — the predecessor to ga4.

METHOD

PATH

DESCRIPTION

GET

/data/ga

Run a Core Reporting query against a UA view

GET

/data/mcf

Run a Multi-Channel Funnels report

GET

/data/realtime

Run a real-time report

GET

/management/accountSummaries

List the UA account, property, and view hierarchy in one call

GET

/management/accounts

List UA accounts the caller can access

GET

/data/ga

Run a Core Reporting query against a UA view

GET

/data/mcf

Run a Multi-Channel Funnels report

GET

/data/realtime

Run a real-time report

GET

/management/accountSummaries

List the UA account, property, and view hierarchy in one call

GET

/management/accounts

List UA accounts the caller can access

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Universal Analytics uses OAuth 2.0. Jentic keeps the refresh token in the MAXsystem vault and mints short-lived access tokens for the agent, so the client secret and refresh token never appear in agent context.

Intent-based discovery

Agents search Jentic with intents like 'run a Universal Analytics core reporting query' or 'list UA goals' and receive the matching operation across the 88-endpoint surface with its input schema.

Time to first call

Direct integration takes 1-2 days for OAuth and learning UA's dimension and metric naming. Through Jentic the same query runs in under an hour.

FAQs

Specific to using Google Analytics API through Jentic.

What authentication does the Google Analytics v3 API use?

OAuth 2.0 with the analytics or analytics.readonly scopes. Jentic stores the OAuth refresh token in its encrypted vault and gives the agent only short-lived access tokens, so credentials never enter agent context.

Does this API let me query GA4 properties?

No. This is Universal Analytics (v3); GA4 properties are accessed via the Google Analytics Admin API (analyticsadmin) and the Google Analytics Data API (analyticsdata). Use this API only for historical UA data and UA property management.

What are the rate limits for the Google Analytics v3 API?

Universal Analytics enforces per-project, per-view, and per-second quotas on the Core Reporting and Management APIs. Default quotas are 50,000 requests per project per day for the Core Reporting API. Quotas are listed in IAM and Admin, Quotas under the Google Analytics API in the Cloud Console.

How do I run a Core Reporting query through Jentic?

Search Jentic for 'run a Universal Analytics core reporting query', load the schema for /data/ga, and execute it with ids=ga:{viewId}, start-date, end-date, dimensions, and metrics. Run pip install jentic and use the async search, load, execute pattern.

Is Universal Analytics still processing new data?

No. Standard Universal Analytics properties stopped processing new hits on 1 July 2023. This API now serves historical UA data and management of legacy property metadata; new analytics implementations should target GA4 via analyticsadmin and analyticsdata.