Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Analytics through Google’s OAuth flow. Agents can query reports, read metrics and dimensions, and pull traffic data from your GA4 properties. The gateway injects OAuth credentials into requests to the Google Analytics Data API automatically. This is useful for reporting agents that generate traffic summaries, marketing agents that monitor campaign performance, or any agent that needs web analytics data.

​
What you will set up

  • A Google OAuth client shared by every Google app in OneCLI
  • A Google Analytics connection for your GA4 properties
  • Per-agent, per-tool access to reporting data

​
Connect Google Analytics

This applies on OneCLI Cloud and self-hosted alike. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
Open Connections > Google Analytics, select Connect Google Analytics, pick your Google account, and click Allow.
OneCLI connect window for Google Analytics showing Configuration required, the setup guide link, and the Configure credentials button.

The Google Analytics connect window before a Google client is set up.

​
What agents can do

  • Run reports with custom date ranges, metrics, and dimensions
  • Query core metrics (sessions, users, page views, bounce rate, conversions)
  • Break down data by dimensions (source, medium, country, page path, device)
  • Read real-time active user data
  • List GA4 properties and data streams on your account
  • Query audience and demographic data
  • Read event-level data and custom event parameters
  • Compare date ranges for trend analysis
  • Query e-commerce metrics (revenue, transactions, items purchased)

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Analytics.

​
FAQ

Yes. Follow the Google setup guide once. One client serves every Google app in OneCLI.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Open Connections > Google Analytics and connect again. Agents with access use the new connection automatically.