Google Analytics Admin API

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

✓ Official Vendor SpecAnalyticsWeb Analyticsoauth228 EndpointsREST

For Agents

Configure GA4 — accounts, properties, data streams, conversion events, custom dimensions, and user access — across 28 management endpoints.

Install Jentic One Beta

Connect the Google Analytics Admin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Analytics Admin 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 Admin API.

List GA4 accounts and properties accessible to the calling user or service account

Create a new GA4 property under an existing account or via an account ticket flow

Configure web, iOS, and Android data streams attached to a GA4 property

GET STARTED

Start building with Google Analytics Admin API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Programmatic GA4 Property Bootstrapping

Agencies and platform teams that launch GA4 for many brands or environments need to spin up properties and data streams from a script rather than clicking through the GA4 admin UI. The Admin API creates the property, attaches web/iOS/Android data streams, registers custom dimensions and metrics, and marks conversions in one repeatable run, so every new tenant gets the same baseline configuration.

POST /v1beta/properties with the new property body, then POST /v1beta/{+parent}/dataStreams for each platform, then POST /v1beta/{+parent}/customDimensions and /v1beta/{+parent}/conversionEvents to lock in the standard config.

Configuration Drift Audit

Analytics governance teams want to detect when someone changes a GA4 property's measurement protocol secret, a custom dimension definition, or who has Editor access. searchChangeHistoryEvents returns a stream of mutations on an account with actor, change type, and resource. A scheduled job stores diffs to a warehouse for review.

POST /v1beta/{+account}:searchChangeHistoryEvents with a 30-day window and write each ChangeHistoryEvent into a warehouse table for compliance review.

Access Review and Compliance Reporting

Compliance teams need to demonstrate who has access to which GA4 properties and who has actually used them. runAccessReport returns who accessed a property, when, and what they did, so compliance can produce quarterly attestations without combing the audit logs manually.

POST /v1beta/{+entity}:runAccessReport with the property as entity and the desired dateRanges to return users, times, and actions, then write the rows to a compliance dashboard.

Agent-Built GA4 Setup

An agent integrating the Admin API through Jentic can take a description of a desired GA4 setup and execute the create-property, create-stream, define-dimension, mark-conversion sequence as discrete tool calls. Jentic isolates the OAuth credential and exposes each operation's input schema, so the agent constructs valid request bodies without learning the GA4 admin reference end to end.

Use the Jentic search query 'create a GA4 property' to discover /v1beta/properties, then chain dataStreams, customDimensions, and conversionEvents creates to bootstrap the new property.

Key Endpoints

28 endpoints — the google analytics admin api is the configuration surface for ga4 properties.

METHOD

PATH

DESCRIPTION

GET

/v1beta/accountSummaries

List the GA4 account, property, and data stream tree

GET

/v1beta/accounts

List GA4 accounts the caller can access

POST

/v1beta/accounts:provisionAccountTicket

Provision an account ticket for a new GA4 account

POST

/v1beta/properties

Create a new GA4 property

POST

/v1beta/{+account}:searchChangeHistoryEvents

Search the change history of a GA4 account

POST

/v1beta/{+entity}:runAccessReport

Run an access report on a GA4 property

POST

/v1beta/{+name}:archive

Archive a GA4 property

GET

/v1beta/accountSummaries

List the GA4 account, property, and data stream tree

GET

/v1beta/accounts

List GA4 accounts the caller can access

POST

/v1beta/accounts:provisionAccountTicket

Provision an account ticket for a new GA4 account

POST

/v1beta/properties

Create a new GA4 property

POST

/v1beta/{+account}:searchChangeHistoryEvents

Search the change history of a GA4 account

Why Jentic?

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

Credential isolation

OAuth 2.0 with analytics.edit / analytics.readonly scopes. Jentic keeps the refresh token in MAXsystem and mints short-lived tokens for the agent, so the GA OAuth client secret and refresh token never appear in agent context.

Intent-based discovery

Agents search Jentic with intents like 'create a GA4 property' or 'mark an event as a conversion' and receive the matching admin operation with its input schema.

Time to first call

Direct integration takes 1-2 days for OAuth, account ticket provisioning, and learning the property/dataStream/customDimension hierarchy. Through Jentic, scripted property setup runs in under an hour.

FAQs

Specific to using Google Analytics Admin API through Jentic.

What authentication does the Google Analytics Admin API use?

OAuth 2.0 with analytics.edit, analytics.manage.users, or analytics.readonly scopes depending on the operation. Jentic stores the OAuth refresh token in the MAXsystem vault and minted access tokens never enter agent context.

Can I create a GA4 property entirely through the API?

Yes. POST /v1beta/properties with parent set to the account and the new property body, then POST /v1beta/{+parent}/dataStreams to attach a web, iOS, or Android data stream. New top-level GA4 accounts go through provisionAccountTicket because they require terms acceptance in the UI.

What are the rate limits for the Admin API?

Admin enforces per-project quotas under the Google Analytics Admin API in IAM and Admin, Quotas. Reads are generous; writes (create, update, archive) are limited per property per day. Configuration write quotas are visible per property in the Admin UI.

How do I bootstrap a new GA4 property through Jentic?

Search Jentic for 'create a GA4 property', load the schema for /v1beta/properties, and execute it with the parent account and the property body. Run pip install jentic and use the async search, load, execute pattern, then chain dataStreams and customDimensions creates.

Does the Admin API return GA4 reporting data?

No. Admin is configuration only. To run reports on a GA4 property, use the Google Analytics Data API (analyticsdata) — runReport, batchRunReports, runRealtimeReport, and runPivotReport.

Google Analytics Admin API

Connect the Google Analytics Admin API to your agent

Capabilities

Start building with Google Analytics Admin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs