How to connect Google Analytics to OpenClaw

The ClawHub skill teaches OpenClaw about Google Analytics, but the calls run through the ClawLink plugin and your connected account. Make sure Google Analytics is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Reconnect Google Analytics from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Analytics tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Analytics call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

This is the single most common Google Analytics failure in ClawLink, 21 of the 48 real tool errors we logged. GA4 stores some dimension and metric combinations separately and refuses to query them together, so the pairing is rejected rather than returned empty. The useful part is that Google names the exact field to drop: the message reads "Please remove eventCount to make the request compatible for example", or occasionally "Please add sessionCampaignName". Tell your agent to remove the single field the error names and retry, rather than rebuilding the request. If it needs to check before spending a call, google_analytics_check_compatibility takes the same dimensions and metrics and returns COMPATIBLE or INCOMPATIBLE per field. Note that it fails outright on an incompatible pair rather than always answering politely, so treat the failure itself as the verdict.

The agent used a GA4 interface label instead of an API name. They differ, and the reporting UI never shows the API name. We have logged this with averageEngagementTime, averageUserEngagementDuration, sessionCampaign, sessionGoogleAdsKeywordText and exits, all of which look correct in the GA4 interface and none of which exist in the Data API. Google's suggestion in the error is usually right, so retry with the field it names. To stop it recurring, have the agent call google_analytics_get_metadata with properties/0/metadata first and pick apiName values from that response.

Despite the wording, this is almost never a permissions problem. It is a property id the connected Google account cannot see, usually one the agent invented or carried over from an example. Ask it to call google_analytics_list_account_summaries and reuse a property value from that response verbatim. Reconnecting will not help and is the wrong first move here.

Two distinct causes, and they need opposite responses. First, the tool may need Google's analytics.edit scope, which ClawLink does not request. Seven of the 67 tools are in that group, all of them account and property administration rather than reporting, and no amount of reconnecting will change it. Second, if a report or list tool fails this way, the grant itself is incomplete: ClawLink requests three Google scopes, which is the condition under which Google shows the consent screen with a separate checkbox per permission, and unchecking the Analytics box produces exactly this error. Reconnect from the dashboard and leave every box on Google's consent screen ticked.

A hard Data API limit, not a ClawLink one, and batch reports count each nested request separately. Split the request into several calls of at most 9 dimensions and 10 metrics each and join the results on a dimension both share, usually date. Asking for everything in one report is the usual cause.

The report went out with no date range. Standard reports require at least one, for example dateRanges=[\{"startDate": "30daysAgo", "endDate": "today"\}]. The exception runs the other way: a cohort report supplies its own window through cohortSpec and fails if you also pass dateRanges.

Google's refresh token for this connection is no longer valid, usually because the grant was revoked in the Google account, the password changed, or the account sat unused long enough for Google to expire it. This is the one case where reconnecting is the right answer: open the ClawLink dashboard, reconnect Google Analytics, and leave every box ticked on Google's consent screen. It is rare, 2 of the 48 real Google Analytics failures we have logged.

Try reconnecting Google Analytics and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect OpenClaw to Google Analytics: link your Google Analytics account once in the browser and OpenClaw can call the Google Analytics API through 67 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Analytics skill from ClawHub, then you click Connect in the dashboard to authorize Google Analytics. OpenClaw calls the tools from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Google Analytics in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Analytics working from chat.

No. That is the requirement every other route imposes, including Google's own MCP server, which asks you to enable the Analytics Data and Admin APIs in a Cloud project, create an OAuth client or an impersonable service account, run a gcloud login, and point a config file at the credentials JSON on disk. ClawLink owns the verified OAuth app instead. You click Connect, approve on Google's consent screen, and ClawLink holds and refreshes the token. There is no Cloud project, no OAuth client, no JSON key on your machine, and no Property Access Management step to grant a robot account access.

Three scopes: https://www.googleapis.com/auth/analytics.readonly, https://www.googleapis.com/auth/analytics and https://www.googleapis.com/auth/userinfo.profile. Because that is more than one non-sign-in scope, Google shows its granular consent screen with a checkbox per permission, and the connection only works if you leave them ticked. ClawLink does not request analytics.edit, so it cannot create, rename or archive properties, custom dimensions or custom metrics. You can review or revoke the grant at any time under Third-party apps and services in your Google account.

Not through ClawLink today. The 67 tools include GA4 Admin API endpoints that would edit a property, but they need the analytics.edit scope ClawLink does not request, so they return 403. In practice the integration is reporting and inspection: run standard, pivot, funnel and realtime reports, read property, audience, data stream, key event and link configuration, and check field compatibility. If you need GA4 configuration writes, that is a genuine limit of this integration rather than something a reconnect will fix.

Google's server is open source, still labelled experimental, read-only by Google's own description, and runs locally over stdio, which means it cannot be used from a hosted or phone-based agent at all. Getting to a first query needs pipx, Python 3.10 or newer, the gcloud CLI, a Google Cloud project, two manually enabled APIs and an OAuth client you create. It registers nine tools, seven of which its README documents. ClawLink exposes 67 through a hosted connection with no local runtime and nothing to keep running, at the cost of routing calls through our infrastructure rather than your machine. If you want a local, self-owned setup and are comfortable with Google Cloud, the official server is a reasonable choice.

The ClawHub skill teaches OpenClaw about Google Analytics, but the calls run through the ClawLink plugin and your connected account. Make sure Google Analytics is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.